# Nebius lets engineers use AI but keeps accountability human

Markdown copy of https://realalpha.app/s/nebius-lets-engineers-use-ai-but-keeps-accountability-human/ on Real Alpha, the best minutes from long interviews with the people building AI. Cite and link the page, not this copy.

- Speaker: [Danila Shtan](https://realalpha.app/people/danila-shtan/) · Danila Shtan is CTO of Nebius.
- Host: [Jacob Effron](https://realalpha.app/people/jacob-effron/) · AI Investor, Redpoint Ventures · Growth investor in Abridge, Ramp and Physical Intelligence; ex-Flatiron Health.
- Show: Unsupervised Learning
- Episode: [The Window Before AWS Wakes Up: Nebius CTO on Racing the Hyperscalers](https://realalpha.app/v/qJkcjURcAe8/), Nov 2, 2026
- Moment: 53:19 to 55:49 of the episode (3 min), playing on https://realalpha.app/s/nebius-lets-engineers-use-ai-but-keeps-accountability-human/; the episode from there: https://realalpha.app/v/qJkcjURcAe8/?t=3199

## Quote

> “whatever you've done with the agent, it's still your result. **It's your responsibility**. It's your pull request. It's your code.”
> — [Danila Shtan](https://realalpha.app/people/danila-shtan/) at [54:52](https://realalpha.app/v/qJkcjURcAe8/?t=3292) · Unsupervised Learning

## Takeaways

1. Nebius sets no per-person or per-department AI usage limits.
2. Employees remain responsible for code produced with agents.
3. Fully autonomous agents cannot yet touch core services.

## About this segment

Danila Shtan says Nebius does not cap AI usage, but monitors how teams use it and expects employees to own agent-generated work. Fully autonomous agents are kept away from core services for now.

From “The Window Before AWS Wakes Up: Nebius CTO on Racing the Hyperscalers”, Nov 2, 2026. [Watch the full episode](https://realalpha.app/v/qJkcjURcAe8/)

## Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

[53:22](https://realalpha.app/v/qJkcjURcAe8/?t=3202) trying to figure out, you know, I mean, obviously, the models only recently got really good on the coding side. And so everyone's trying to figure out what it means to build teams given the new model capabilities and run an organization. I'm curious where you've settled and how you thought about that. Cautiously, conservatively. I'm very concerned that modern models and the attractive user experience that they provide, like model agents, modern models, etc etc etc is something that will lead us to two issues you like you see slop like being revealed in like in chats in merge requests all over and i like i try to paste that and i try to like be very observant and vigilant about that so for example like we don't restrict talking usage like people can use whatever they want our budget is quite significant we don't impose like

[54:32](https://realalpha.app/v/qJkcjURcAe8/?t=3272) per person limitations or per department limitations but the at the same point we try to like look at the usage uh figure out what it is used for look at the most ineffective ways people use it. We constructed a set of policies that doubles down on the idea that whatever you've done with the agent, it's still your result. It's your responsibility. It's your pull request. It's your code. It's you who is on call. It's you who's going to wake up in the middle of the night if something goes awry, et cetera, et cetera, et cetera. And if something was created by a completely autonomous agent it is marked like that uh completely autonomous agents will not touch like the core services for a while because like this is like this is like out of bounds like sometimes people are surprised that like i work in a company that's kind of participates in this

[55:36](https://realalpha.app/v/qJkcjURcAe8/?t=3336) whole ai revolution and i'm very conservative but at the same time like i've seen how this sources we've made, and I'll be cautious.