At the highest level, every Salesforce org is one of two things:
- Production org — the live, paid environment where real users do real work.
- Sandbox org — a non-production copy used for development, testing, training, or staging.
That’s the textbook answer. The reality is a little more nuanced; sandboxes come in flavours, and there are a few special-case orgs that don’t fit cleanly in either bucket.
Production orgs
The single source of truth for the business. Characteristics:
- Houses live data — customers, opportunities, cases, invoices.
- Used by real users every day.
- Login URL: login.salesforce.com (or a My Domain like
acme.my.salesforce.com). - Paid licences required for every user.
- Deployments to production enforce 75% test coverage and “all tests must pass” rules.
- One per customer contract (typically).
You don’t develop in production. You deploy to it.
Sandbox orgs
Non-production copies linked to a production org. Sandboxes inherit metadata (and optionally data) from production at creation/refresh, then diverge as developers and admins customise them.
Four flavours of sandbox (covered in detail in What are different types of sandboxes?):
| Sandbox type | Metadata | Data | Refresh interval | Typical use |
|---|---|---|---|---|
| Developer | Yes | None | 1 day | Solo dev work |
| Developer Pro | Yes | None | 1 day | Bigger storage for solo dev |
| Partial Copy | Yes | Sample (template-defined) | 5 days | UAT with realistic data |
| Full | Yes | All data | 29 days | Staging, perf, training |
Login URL: test.salesforce.com (or acme--sandboxname.sandbox.my.salesforce.com).
Orgs that sit outside this dichotomy
- Developer Edition — free, standalone production-like org for learning. Has all developer features but small storage. Not connected to a real production org.
- Trailhead Playgrounds — special Developer Edition orgs pre-seeded with Trailhead-ready data.
- Scratch orgs — short-lived (up to 30 days), source-driven, spun up via Salesforce CLI. Used for individual developer work and CI. Linked to a Dev Hub, which is itself usually a production org.
- Trial / Demo orgs — Salesforce-provisioned for sales prospects; convert to production after purchase.
- Patch orgs — special org type ISVs use for managed-package patch releases.
In an interview
The expected answer is production and sandbox. If you want extra credit, mention:
- Production has live data and paid licences; sandbox is a non-production copy.
- Sandboxes come in four types (Developer, Developer Pro, Partial Copy, Full).
- Scratch orgs are a third category for modern, source-driven dev.
That covers the textbook answer and signals you’ve done real-world dev work.
Why the distinction matters
Every deployment, every release pipeline, every code review process in Salesforce is built around the production-vs-sandbox separation. Understanding which org type you’re in is the first thing every admin and developer learns — and the first thing that goes wrong when someone deploys to the wrong target.
Verified against: Salesforce Help — Sandbox Types and Templates, Salesforce DX Developer Guide, Metadata API Developer Guide. Last reviewed 2026-05-17 for Spring ‘26 release.