Runtimes
Each exocorp runs in its own isolated environment — dedicated compute, its own database, and a private network namespace. No shared state between organizations.
Isolation
Every exocorp gets its own compute instance, database volume, and network namespace. There is no shared state at the runtime level. One exocorp cannot see or affect another.
Health monitoring
The platform continuously checks runtime health. Healthy, unreachable, and inactive states are tracked and surfaced in the admin dashboard. Unhealthy runtimes are flagged immediately so you can intervene before they affect work.
Lifecycle
Runtimes move through states: pending, provisioning, running, stopped, and failed. You can pause, resume, reprovision, restart, roll back, or destroy a runtime at any time from the dashboard.