Who manages what
The boundary between what you control in Runtime and what id0n operates for you.
Runtime is a managed service. You decide what runs and how much capacity it gets. id0n runs the infrastructure that builds and executes it.
You control
| Area | What you decide |
|---|---|
| Source | The repository you connect, or the container image you authorize. |
| Build and start | Supported build settings and how your application starts. |
| Environment | Your application's environment variables and secrets. |
| Credentials | Source and image credentials, scoped to one application. |
| Capacity | CPU, memory and disk for the application. |
| Lifecycle | Requests to deploy, restart, stop, roll back or delete the application. |
id0n controls
| Area | What id0n does |
|---|---|
| Build workers | Runs and maintains the workers that build your application. You cannot choose or point to a worker. |
| Execution | Runs the infrastructure your application executes on. |
| Build cache | Chooses where caches are stored, how long they are kept and when they are cleaned up. |
| Capacity enforcement | Applies the capacity you set. |
| Retention and cleanup | Removes old build data and unused content. |
Why this matters
- You never handle build-worker credentials, cache storage credentials or host paths.
- Settings that would change id0n-managed infrastructure are refused with an error. They are never silently ignored. See Unsupported features.
- Runtime does not require any other id0n product.