Applications
The unit you deploy, configure and scale on Runtime.
An application is one service on Runtime. Everything else, including source, builds, releases, configuration, domains, storage and capacity, belongs to exactly one application.
Lifecycle
| Action | Effect |
|---|---|
| Create | Reserves the name and creates empty configuration. |
| List and inspect | Shows your applications and their state. |
| Rename | Changes the application's name. |
| Lock and unlock | A locked application refuses new deploys until it is unlocked. Use it to freeze a service during an incident. |
| Delete | Removes the application, its releases, configuration and routing. |
Isolation
- Credentials, caches, configuration and storage are scoped to one application.
- An application cannot read another application's source, cache or credentials, including through cached build data.
- Requests made on your behalf by id0n operators still act only on the application they target.
Workloads Runtime is built for
- Web apps, APIs and HTTP services that run continuously.
- Services that need a stable URL and custom domains.
For scheduled or one-off jobs, use Ongoings.