Environments and promotion
One contract, many environments — how Möbius tags, gates, and promotes data across dev, staging, and prod.
Möbius governs every environment your organization runs — dev, staging, prod, or whatever ladder you define — from a single instance and a single set of contracts.
One contract, many environments
The semantic contract for a table (what "orders" means, what columns a "policy" table must carry) is environment-invariant: you define it once, and it applies wherever the table exists. What varies by environment is:
- The environment tag — every table (or, for an in-place table, every warehouse connector) carries an
environmentLabeland apromotionRank, an explicit ordering from least to most privileged (for example: dev → staging → prod). - Gate mode — how strictly row-level writes are enforced (Enforcing / Advisory / Off), set per environment. Dev can run loose; prod can run strict. See Certification and gates for what each mode does.
- Governance posture — several other settings can also vary per environment, including who can certify without a second approver, whether a third-party AI tool may see that environment's data, and table-level access-control strictness. Configure these on Workspace → Environments.
Running two entirely separate Möbius instances (one for dev, one for prod) is never required — one instance governs your whole ladder. Running separate instances is supported for regulatory separation on a fully air-gapped Enclave deployment, but it isn't the default posture.
Promotion
Promotion moves a table's governance artifact — its contract and column definitions — up the rank ladder, from a lower environment to a higher one. Promotion is always explicit, and it is not a certification shortcut:
- The promoted table lands in the target environment uncertified (
PENDING_REVIEW). Its dev certification does not travel with it — a promoted artifact's claims aren't load-bearing on their own. - You then re-certify it as a separate step, against the target environment's own data and under the target environment's own gate mode, before it's readable through the certified doors.
- Moving into a stricter environment can require steward sign-off at that re-certification step, depending on the target environment's certify policy.
- Promotion never sets the table's steward. In the target environment, the steward is whoever a workspace admin assigns there, and the table can't be certified until one is assigned.
You start a promotion from the table, in the environment it is in now. The right to promote into an environment is the right to work in it: you need the Steward role and access to the target environment. When the target runs on a separate Möbius instance, your browser opens that instance, you sign in, and it shows a consent screen naming the table and the target environment. Choose Approve or Deny yourself. The in-app assistant can start a promotion for you, but it can't answer the consent screen.
From the CLI:
mb env promote <tableId> --to <env>See the CLI reference for the full command, and
mb versions restore for putting an earlier certified contract version back on the live
contract as a new forward-minted version.
Deployment models and environment separation
How environments are physically separated depends on your deployment model (see Security for the three models):
- Cloud — environments are logical: one Möbius instance, one database, environments distinguished by their tag.
- Connect / Enclave — environments are typically physical: separate boxes or stacks, each running its own instance with its own environment identity. This is the stronger separation regulated or air-gapped deployments choose.
Both arrangements use the same contract-and-tag model described above — physical separation changes where the data and enforcement live, not the governance model applied to it.