# ProdBreak

> Stateful, controllable sandbox environments for any API your app depends on.

## Docs

- [Deck](https://docs.prodbreak.com/apis/deck.md): Reference for the Deck pack — objects, events, errors, and formats, faithful to Deck API v2.0.0 — plus the thin prod-break control layer.
- [Supported APIs](https://docs.prodbreak.com/apis/overview.md): Point your app at any of these. Search the 500 most-used APIs and grab a sandbox for the one you depend on.
- [Stripe](https://docs.prodbreak.com/apis/stripe.md): Reference for the Stripe pack — objects, events, errors, and formats, faithful to the live Stripe API — plus the thin prod-break control layer.
- [Force a branch](https://docs.prodbreak.com/concepts/branching.md): Drive a workflow down its success or failure arm on demand — without inventing a path that can't happen.
- [Causes, not effects](https://docs.prodbreak.com/concepts/causes-not-effects.md): You trigger domain events; webhooks fall out of real state transitions, exactly like prod.
- [The virtual clock](https://docs.prodbreak.com/concepts/clock.md): Each world has one timeline you control. Make time pass on demand; keep CI deterministic.
- [Values you control](https://docs.prodbreak.com/concepts/exogenous.md): What's faithful and unfakeable vs what you set yourself — the line that decides what you can control.
- [Setting values & the trace](https://docs.prodbreak.com/concepts/pins-and-trace.md): Set out-of-control values by result, not by channel — and let the sandbox teach you its own surface.
- [How ProdBreak works](https://docs.prodbreak.com/concepts/sandbox.md): A faithful model of each API you can point your app at — and what you interact with.
- [One instance = one world](https://docs.prodbreak.com/concepts/worlds.md): The isolation model: each running sandbox is exactly one world, reset between tests.
- [How faithful is it?](https://docs.prodbreak.com/fidelity.md): Exactly what ProdBreak guarantees, what it doesn't, and how we guard the line.
- [Make CI deterministic](https://docs.prodbreak.com/guides/deterministic-ci.md): Collapse durations so cascades fire inline, in order, with no flake.
- [Force an error](https://docs.prodbreak.com/guides/force-an-error.md): Arm the failure your code must survive — the case that's painful to trigger for real.
- [Run parallel workers](https://docs.prodbreak.com/guides/parallel-workers.md): One instance per worker, provisioned by the CLI, assigned automatically by the plugin.
- [Seed history](https://docs.prodbreak.com/guides/seed-history.md): Start a test from exactly the state you need.
- [Point a staging app at a sandbox](https://docs.prodbreak.com/guides/staging.md): Use a long-lived instance as a staging-like environment, not just a test fixture.
- [Test a webhook](https://docs.prodbreak.com/guides/test-a-webhook.md): Receive a real signed webhook, verify it, and confirm it agrees with the GET.
- [Connect your app](https://docs.prodbreak.com/interception.md): How your app reaches the sandbox: change the address, not the request.
- [What is ProdBreak](https://docs.prodbreak.com/introduction.md): Stateful, controllable sandbox environments for any API your app depends on — faithful to the real thing, pointed at by changing one base URL.
- [Quickstart](https://docs.prodbreak.com/quickstart.md): From zero to a green integration test in under 10 minutes.
- [Command line](https://docs.prodbreak.com/reference/cli.md): Spin up and run sandboxes from your shell.
- [SDK](https://docs.prodbreak.com/reference/sdk.md): The control client: connect to a world and drive it. JavaScript/TypeScript first; Python mirrors it.
- [Test framework plugins](https://docs.prodbreak.com/reference/test-plugins.md): Framework-idiomatic sugar over the SDK — fixtures and lifecycle for Jest, Vitest, and pytest.
- [HTTP API](https://docs.prodbreak.com/reference/wire.md): The raw HTTP control contract every client wraps. curl works; the SDKs are thin shells over this.