Skip to main content
Environments are isolated copies of your backend that let you develop, test, and ship changes safely without affecting production. Every project starts with a single master environment. From there, you branch new environments — staging, feature-auth, qa-sprint-12 — that inherit the schema (and optionally the data and configuration) of their parent and run in complete isolation. Changes in one environment don’t propagate to another until you explicitly merge them.
Archie also has code branches for the Frontend and for Logic services. They are a different thing. See Environments and code branches.

Environments and code branches

Archie uses the word “branch” for two different things. An environment holds data and configuration, and it runs deployed code. A code branch holds a version of code for the Frontend or for one Logic service.

Which one do I need?

  • You want to test a schema change safely. Create a new environment, make the change there, and merge it when you are ready.
  • You want to try a code change or have it reviewed. Create a code branch and open a pull request.
  • You want a realistic copy of your data for QA. Create an environment with branch mode Full.
  • You want your deployed service to behave differently in staging and in master. Deploy a branch and commit of the service to each environment.
To learn more, see Branching, Branches in a Logic service, and Creating environments.

How you reach Environments

Environments don’t have a dedicated entry in the Backend sidebar. You access them through the environment switcher at the top of the project chrome — the dropdown that shows the active environment’s name. From there you can:
  • Switch to a different environment (the entire Backend Console reloads in that environment’s context).
  • Open the create-environment modal.
  • Open the environment tree, diff, merge, history, and backups views.

The branching model

In this section, “branch” means creating an environment from a parent. It does not mean a code branch. Environments form a parent-child tree rooted at master. Each branch carries metadata — name, status, branch mode, parent, branched-at timestamp, and the list of children — that drives the rest of the surface (diff target selection, merge direction, restore scope).

Branch modes

Branch modes apply when you create an environment from a parent. They are not options of a code branch. When you create a new environment, you pick how the source database is cloned: For full coverage of branch modes and the configuration-copy flags, see Creating environments.

Status lifecycle

Environments transition through five states. The platform uses these to prevent conflicting operations — you can’t delete an environment that’s merging, can’t merge into one that’s branching.

Isolation guarantees

Environments are designed for hard isolation between development stages:
  1. Storage isolation — each environment has its own dedicated PostgreSQL database. A bug or destructive operation in dev cannot reach production.
  2. Configuration scoping — every backend setting is per-environment. Auth providers, API keys, RBAC roles, custom APIs, file storage, environment variables, and integration credentials are all independent.
  3. Context propagation — when you switch environments, the entire Backend Console reloads in that environment’s context. The same applies to API requests via the environment header. There’s no path by which dev traffic accidentally touches production data.
For the full list of what’s scoped per-environment, see Configuration.

Where to go next

Creating

Branch a new environment with the right mode and copy flags.

Colors

Tell environments apart at a glance with a color for each one.

Tree

Visualize the parent-child hierarchy and plan merge strategies.

Diff

Compare two environments’ schemas with forward-only semantics.

Merge

Cherry-pick changes from one environment to another, transactionally.

History

Audit trail of every merge and migration.

Backups

Automatic pre-merge backups, manual snapshots, and restore.

Frontend data source

Choose which backend environment your generated frontend connects to.

Deleting

Permanently remove an environment.

Configuration

What’s scoped per-environment, with cross-links to each setting.

FAQ

Yes — branch as many as you want. Each one is independent, so it’s reasonable to have a long-lived master and staging plus a handful of short-lived feature-* environments for in-progress work.
No. Environments are isolated. Schema changes propagate only when you explicitly merge — the cherry-pick UI lets you pick which changes to apply.
It’s the root of the tree and can’t be deleted or renamed. Other environments can be deleted; master always exists so the project always has a baseline.
Nothing. Switching only changes which environment your console session is pointed at. The previous environment continues running, holds open connections, and serves traffic from any clients still using it.
Not as a dedicated menu entry — environments are surfaced through the switcher at the top of the project chrome. The docs cover the full surface; the product UI threads the actions through the switcher dropdown.