Skip to main content
A stateful environment is the provider your software talks to inside an Archal sandbox. It keeps data across calls, applies provider-specific behavior, and can return to a known starting state. Each sandbox can contain one environment or several. For example, one sandbox can hold GitHub, Slack, and Datadog so an agent can run a cross-service workflow without touching real accounts.

​
Environment catalog

Every row is included in Archal’s environment catalog. That does not prove the hosted lifecycle is available. Public is the intended GA channel. Preview means upstream coverage is incomplete. Local catalog validation: 110 passed. Archal checks current hosted certification before admitting new sandboxes.

​
Five starting states per environment

The catalog includes exactly 110 versioned samples, five for each environment. The set spans small baselines, team-shaped state, larger corpora, edge cases, and multi-step workflows. Every environment page shows what each sample is for, the first read, a representative mutation, the expected changed paths, reset expectations, limits, and the verified state artifact.

​
What provider-shaped means

Archal does not turn every provider into one generic API. GitHub requests remain GitHub-shaped. Linear keeps its GraphQL surface. Supabase accepts database-shaped operations. Your existing provider client should need a different base URL and scoped test credentials, not a rewrite around an Archal data model.
After launch, the authenticated catalog is authoritative. Run archal environment list or call GET /api/environments before relying on an environment in automation.