Environments
Sandbox and Live are fully isolated execution environments. Build and test in sandbox before touching real money.
Two environments, fully isolated
Every procedure run in Rapidfolio happens in one of two environments: Sandbox or Live. They are completely separate — different API keys, different connections, different run histories. Nothing in sandbox affects live, and vice versa.
Sandbox
Sandbox is where you build and test. It's a full execution environment — when you run a procedure in sandbox, it makes real API requests to your sandbox integrations:
- Stripe test mode
- Plaid sandbox
- Onfido's test environment
- Your own staging systems
You get real integration behavior — real error codes, real response shapes — without touching production data or real customer accounts. When something breaks in sandbox, nothing actually breaks.
Use sandbox for:
- Building new procedures from scratch
- Testing edge cases and error paths
- Running scenarios before publishing
- Showing stakeholders how a workflow behaves
Live
Live uses your real integrations. Tool calls in live runs affect real accounts, real customers, and real money.
Only use live for procedures that have been thoroughly tested in sandbox and are ready for production. There's no undo for a live Stripe charge or a real bank transfer.
What's scoped per environment
| Resource | Scoped separately per environment |
|---|---|
| API keys | Yes — sandbox and live keys are different |
| Connections | Yes — your sandbox Stripe and live Stripe are separate connections |
| Triggers | Yes — a trigger set up in sandbox won't fire live runs |
| Run history | Yes — sandbox runs don't appear in the live run list |
The procedure graph itself is shared. You don't maintain two separate procedure definitions. What changes is which connections each Tool Call node resolves to when it executes.
Going from sandbox to live
When you're ready to take a procedure into production:
- Make sure every sandbox connection has a corresponding live connection in Settings → Connections
- Run your scenarios in sandbox and confirm they all pass
- Publish the procedure version
- Set up your live trigger or configure your live API key in your application
The first live run will use your live connections. All prior sandbox runs stay in the sandbox history.
API keys and environments
Your API key determines which environment a run goes into:
| Key prefix | Environment |
|---|---|
rsk_sandbox_ | Sandbox |
rsk_live_ | Live |
Use sandbox keys in development and CI. Live keys belong in production only — store them in a secrets manager, not in environment files or source code.