> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment strategy

> Two independent cycles: platform environments with CI/CD, and per-use-case dev and prod workspaces versioned by Git.

Deployment on Prisme.ai runs on **two independent cycles**. Keep them separate in your head and the rest is simple: the **platform** moves through its own environments, and each **use case** has its own dev and prod workspaces on the production environment, versioned by its own Git.

<Frame>
  <img src="https://mintcdn.com/prismeai/JfYVoQBb78ItOmsW/images/deployment-strategy.svg?fit=max&auto=format&n=JfYVoQBb78ItOmsW&q=85&s=43d9b911783994cc487544ec6f575f52" alt="Platform versions flow Dev to Preprod to Prod with go/no-go, run by the Platform Squad with CI/CD. A use case runs on the Production platform environment as a Dev workspace (Git read/write) that pushes to a use-case Git repo, from which a Prod workspace reads (read-only). The use-case lifecycle is decoupled from platform upgrades." width="1200" height="500" data-path="images/deployment-strategy.svg" />
</Frame>

## Platform environments (self-hosted)

The platform itself moves through isolated environments on your own landing zone (AWS, Azure, GCP) or on-premises. A minimum of two is recommended, three when critical use cases justify it. This cycle is run by the **Platform Squad** with **CI/CD**.

| Environment        | Role                                                                                           |
| ------------------ | ---------------------------------------------------------------------------------------------- |
| **Development**    | Receives new platform versions first. Connected to Git to version workspaces.                  |
| **Pre-production** | Validation close to production: non-regression tests of critical use cases before any upgrade. |
| **Production**     | Updated only after pre-production sign-off. Stable, supervised service.                        |

Each version is promoted **Development, then Pre-production, then Production, with a formal go / no-go** at each step. Critical use cases must be testable on every environment before a version reaches production. See [self-hosting updates](/self-hosting/operations/updates).

## Deploying a use case

A use case does **not** get its own platform environments. It runs on the **production** environment, as **two workspaces** synchronized by a **dedicated Git repository**. Its lifecycle is **decoupled** from platform upgrades, and Git guarantees reproducibility.

<Steps>
  <Step title="Dev workspace (Git read / write)">
    Where the team builds and iterates, on the production platform environment. Connected to the use case's dedicated [Git repo](/products/ai-builder/versioning) in read / write.
  </Step>

  <Step title="Controlled promotion">
    Versions are promoted through the **CD pipeline** and / or the **Builder UI**. There is no manual change in production. See [deployment](/products/ai-builder/deployment).
  </Step>

  <Step title="Prod workspace (Git read-only)">
    Connected to the **same** Git repo in read-only, so production always runs a validated, versioned release.
  </Step>
</Steps>

<Note>
  **Critical use cases during a platform upgrade.** When the platform moves to a new version, critical use cases are also validated across the Dev, Pre-production, and Production environments. This validation is carried by the **Platform Squad**, not by the use-case teams.
</Note>

## Workspace or self-care?

Not every use case needs the two-workspace, Git-versioned pipeline. Choose per use case.

<CardGroup cols={2}>
  <Card title="Workspaces (Git-versioned)" icon="code-branch">
    Dev and prod [workspaces](/products/ai-builder/workspaces) synchronized by Git. Required when every change must be traced and versioned.
  </Card>

  <Card title="Self-care (no-code)" icon="wand-magic-sparkles">
    Agents created and updated directly in the product interfaces by business teams, with no workspace, repo, or pipeline. Enough for lighter, self-service use cases. See [Agent Creator](/products/agent-factory/overview).
  </Card>
</CardGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="From a use case to production" icon="diagram-project" href="./use-case-lifecycle">
    The full delivery lifecycle in phases
  </Card>

  <Card title="Builder deployment" icon="rocket" href="/products/ai-builder/deployment">
    How promotion and Git sync work in practice
  </Card>
</CardGroup>