ReferenceAsk
Remy Reference/Architecture/Architecture/Environment Matrix
Appendix

Environment Matrix

Live, preview and dev side by side

The three environments a request can run in, and what each one resolves to.

LivePreviewDev
What it isThe promoted releaseA branch buildA person's working copy
Release rowThe one the app's live pointer namesThe branch's release with status previewA dev release per workspace, resumed rather than recreated
Host{slug}.{app apex} and custom domains{label}--{slug}.{app apex}The dev box's preview host {sessionId}.{sandbox apex}, through the sandbox proxy
Host resolutionThe app's own origin serves liveA double-hyphen label names a preview releaseNone; dev is reached by refinement from a session or a hook token
Data plane keyThe live release idThe preview release idThe dev release id
DatabasesThe live filesA clone of live, taken on the preview's first visitA clone taken at session start; reset, truncate, and lift available
CodeThe compiled bundles for the releaseThe compiled bundles for the preview releaseTranspiled per request on the dev box
Runs onA release sandboxA release sandboxThe dev box's tunnel
SecretsProd valuesDev valuesDev values
Who reaches itAnyone the app admitsWorkspace members with a session, and share-link holdersThe person, through their own preview and control channel
GateThe app's own authRequired before any of the /_/ surface answersThe person's platform session
Realtime channel scopelivepreviewdev
Request log and metrics labellivepreviewdev
Precedence when a credential is presentThe host wins outright over any session token; off its host a preview session reaches nothing (the voice worker's excepted)A dev session beats a dev-session header, which beats the host; a session or header that names no dev release of the app reaches nothing, not live

The environment is decided once, at a single boundary with three resolution paths: from a host, from a request carrying an interface session, or from a callback carrying a hook token. Each yields a resolved environment that the handlers which run code, read config or touch data receive and ask, rather than re-deriving the decision downstream.