Skip to main content
Archal creates testing sandboxes for software that talks to external services. Each sandbox contains one or more stateful environments, such as GitHub, Slack, Datadog, Jira, or Supabase. The environment keeps data across calls, responds through a provider-shaped interface, and can return to a known starting state. Your test can create an issue, send a message, update a monitor, inspect what changed, then reset and run again without maintaining provider test accounts.

​
The product in one picture

The sandbox is the customer-visible isolation boundary. The lifecycle API and CLI call it a session, and its stable identifier is sessionId. Those names refer to the same running sandbox.

​
What Archal handles

  • isolated state for every sandbox
  • 22 provider-shaped environments
  • five versioned starting states for each environment
  • one create, inspect, renew, reset, and destroy lifecycle
  • state reads and explicit diffs
  • scoped credentials that expire with the sandbox
  • usage metering per ready environment

​
What stays yours

Archal does not replace your agent harness, model, evaluator, observability tool, or CI system. Your coding agent connects Archal to the code and tools you already use. Braintrust, LangSmith, custom evals, and ordinary test runners can keep doing their current jobs.

​
A normal workflow

  1. Choose the environments and starting states your test needs.
  2. Create one sandbox containing those environments.
  3. Point existing provider clients at the returned URLs and scoped credentials.
  4. Run the agent, integration test, or QA workflow.
  5. Read state or compare it with an explicit before snapshot.
  6. Reset for another attempt or destroy the sandbox.

Set up with a coding agent

Pair Claude Code, Codex, Cursor, or Devin and let it configure Archal.

Understand a sandbox

See how isolation, environments, state, and lifecycle fit together.

Browse environments

Review all 22 environments and their 110 curated starting states.

Integrate manually

Use the CLI, TypeScript client, MCP, or raw REST without a coding agent.
Archal documents the supported provider surface for each environment. Inclusion in the catalog is not a claim that every upstream provider operation has been reproduced.