Sandbox vs Trial vs Production vs Default vs Developer environment
Verdict: Develop and test with copy and reset in a Sandbox. Trial is short-lived and self-cleaning after about 30 days. Production is for permanent work the organisation depends on.
| Criterion | Sandbox | Trial | Production | Developer |
|---|---|---|---|---|
| Purpose | Non-production development and testing | Short-term evaluation | Permanent work the organisation depends on | Personal build space from the Developer Plan |
| Key feature | Copy and reset to a clean baseline | Automatically cleaned up, expires ~30 days | Lasting, fully featured | Created with a Developer Plan licence |
| Choose when | Iterate and reset between test cycles | Try an app briefly and let it expire | Run apps and flows you depend on | Individual makers build and learn |
Rules
- Choose a Sandbox: a non-production environment offering copy and reset, used for development and testing separate from production.
- Choose a Trial for a brief evaluation: it is intended for short-term testing, is automatically cleaned up, and expires after 30 days, one per user.
- Choose Production for permanent work the organisation depends on, not for non-production development and testing.
Traps
- Copy and reset ties specifically to Sandbox; Trial supports short-term testing but expires and is auto-cleaned rather than reset.
- Sandbox persists for ongoing development; it is not auto-cleaned after a short period the way a Trial is.