Deployments
A deployment activates a published boundary version in a specific environment. Once deployed, all evaluations in that environment run against the deployed boundary version.
Deploy Tab
Section titled “Deploy Tab”The project Deploy tab shows all environments and their current deployment state. Each environment card shows whether a boundary version is currently active, which version it is, and its status.
Deploying a Boundary Version
Section titled “Deploying a Boundary Version”- Click Deploy (or use the keyboard shortcut
Dfrom the Deploy tab) - Select the boundary version you want to deploy (only Published versions can be deployed)
- Select the target environment
- Click Confirm Deploy
Only one boundary version can be active per environment at a time. Deploying a new version automatically supersedes the previous deployment.
Approval Workflow
Section titled “Approval Workflow”Production deployments may require approval depending on your organization’s configuration. When approval is required, the deployment enters a Pending Approval state. An authorized team member must approve it before it becomes active.
Environments
Section titled “Environments”Each project can have multiple environments. Environment types determine which boundary version statuses are deployable:
| Type | Description |
|---|---|
| Development | For testing and iteration. Draft and Published versions are deployable. |
| Staging | Pre-production validation. Only Published versions are deployable. |
| Production | Live governance. Only Published versions are deployable. Approval may be required. |
| Custom | User-defined environment with configurable policies. |
Environments are managed in the project Settings tab under the Environments section.
Promoting and Rolling Back
Section titled “Promoting and Rolling Back”- Promote: take a deployment from one environment and deploy it to a higher environment (e.g., Staging to Production)
- Rollback: revert an environment to the previously active deployment
Both actions create new deployment records. The deployment history is append-only and fully auditable.
What’s Next
Section titled “What’s Next”- Boundaries : create and publish boundary versions
- Evaluations : submit evidence against deployed boundaries
- Certifications : run compliance checks across deployed boundaries