Platform
Platform Overview
User-level model for how projects, environments, and releases work.
Enclavely is organized around a simple model:
- Organization: your team and permissions
- Project: one deployable service
- Environment: isolated target within a project
- Release: immutable deploy record
Request flow
For each environment, Enclavely gives you a route URL. Traffic is served by the currently healthy release for that environment.
Deploy flow
- Build artifacts in your pipeline
- Run
enclavely deploy --project <name> --env <env> ... - Track status with:
enclavely statusenclavely release listenclavely logs --follow
- Verify route with
enclavely routing --project <name> --env <env>
What is guaranteed
- Releases are immutable once created
- Routing only points to healthy releases
- Access control is enforced by org role + API key scope
- Audit history is available for operational events
You do not need to manage platform internals to deploy with Enclavely. Focus on your service, digests, and release flow.