Deployment

Specification - implementation in progress. The CI integration flags and the hosted control plane endpoints are specified but not yet fully available in the sandbox environment. Contact your PLEXI technical contact for current availability.

Environment model

Flexor uses three environments:

Environment	Purpose	Vault tier scope	Agent runs
sandbox	Development and testing	L3 + L4	Manual triggers only by default
staging	Integration testing	L2 + L3 + L4	All triggers; isolated data sources
production	Live operations	L2 + L4	All triggers; live PlexiFact catalog

Agents must explicitly declare their target environment in the YAML (environment: production). Flexor will not deploy an agent to production unless the declaration matches.

The deployment workflow

Standard deployment

# 1. Validate all changed files
flexor validate

# 2. Sync the vault
flexor sync --vault company

# 3. Deploy to staging
flexor deploy --env staging

# 4. Run a smoke test
flexor run feed-monitor --now --env staging

# 5. If staging is clean, deploy to production
flexor deploy --env production

Targeting a specific agent

flexor deploy --agent feed-monitor --env production

Dry run

flexor deploy --dry-run --env production

Prints what would be deployed without making changes. Use this to verify the deployment plan before executing it.

Rollback

To revert an agent to the previous deployed version:

flexor rollback --agent feed-monitor --env production

Flexor maintains the last three deployed versions of each agent. To roll back to a specific version:

flexor rollback --agent feed-monitor --version 1.2 --env production

CI integration

Add Flexor deployment to your CI pipeline with the FLEXOR_API_KEY environment variable:

# Example: GitHub Actions step
- name: Deploy Flexor agents
  env:
    FLEXOR_API_KEY: ${{ secrets.FLEXOR_API_KEY }}
  run: |
    flexor validate
    flexor sync --vault company
    flexor deploy --env production

The FLEXOR_API_KEY must have deploy:production scope. Generate keys in the Flexor dashboard under Settings > API Keys.

Deployment to a PLEXI-managed environment

For PLEXI client firms where PLEXI manages the Flexor runtime, the deployment process differs:

1. Submit a deployment request via the PLEXI client portal or email your engagement lead
2. PLEXI validates the vault configuration and runs pre-deployment checks
3. Changes are deployed to staging for your review (48-hour review window)
4. After your approval, changes deploy to production during the next maintenance window (Tuesdays and Thursdays, 22:00–23:00 ET)

Self-service production deployment is available for firms on the Full Stack CTO engagement tier.

Health checks

After deployment, verify agent health:

flexor status --env production

Expected output:

Environment: production
Agents: 8 active, 0 paused, 0 erroring
Last deployment: 2026-04-30 14:32 UTC
Vault sync: 2026-04-30 14:30 UTC (current)
PlexiFact connection: healthy

An agent in erroring state has failed its most recent run and exceeded its retry policy. Inspect with:

flexor logs --agent <name> --env production --status error