Environments

Workspace-level runtime environments with per-app release binding for Production, Staging, and Development.

Environments provide isolated runtime configurations for your AI apps. MechaMental comes with pre-configured environments at the workspace level, and each app deploys releases to these environments independently.

Pre-Configured Environments

Environments are defined at the workspace level. Every workspace comes with three pre-configured environments:

Environment	Purpose
Production	Serves live traffic. Only deploy releases that have been validated.
Staging	Mirrors production for pre-release validation and testing.
Development	For active development and experimentation.

These environments are shared across all apps in the workspace, but each app has its own independent release binding per environment.

Release Binding

Each environment displays an Active Release — the specific release version currently deployed and serving traffic for that app. The Environments tab on an app shows all available environments with their active release status at a glance.

When you deploy a new release to an environment:

The new release atomically replaces the previous one
The switch is instant — no downtime
The previous release remains available for rollback

Production  → v2.1.0 (Active)
Staging     → v2.2.0 (Active)
Development → v2.3.0-beta (Active)

Deploying to an Environment

Deployment happens from the Releases tab of your app:

Find the release you want to deploy (it must be in the Ready or Active state)
Click Deploy to Environment
Select the target environment (Production, Staging, or Development)
The release is bound to that environment and begins serving traffic immediately

Deploy to Staging First

Always deploy to Staging and validate before promoting to Production. This catches issues before they affect live users.

Per-App Independence

While environments are defined at the workspace level, release binding is per-app. This means:

App A can have v3.0.0 deployed to Production
App B can have v1.5.0 deployed to Production
Each app manages its own deployment lifecycle independently
Deploying one app does not affect other apps in the same workspace

Environment-Scoped Requests

When calling an endpoint, the environment determines which release (and therefore which pipeline configuration) handles the request. The active release for the target environment defines:

Which augmentation pipeline version runs
Which endpoint configuration is used
Which step configurations, prompts, and tool bindings are applied

Rollback

Since releases are immutable snapshots, rolling back to a previous version is instant:

Go to the Releases tab in your app
Find the previous release you want to restore
Click Deploy to Environment and select the environment
The previous release replaces the current one immediately

Instant Rollback

No configuration is lost or overwritten during rollback. Every release is a complete, self-contained snapshot. The old active release simply moves back to the Ready state and can be redeployed at any time.