A Salesforce development environment is an isolated instance of the Salesforce platform where developers, admins, and architects can build, test, and validate changes — without risking the integrity of the live production org. Think of it as your private coding workspace, away from real users and real data.
Every Salesforce professional — from a beginner learning Apex to an experienced architect building LWC components — works within some type of development environment. Getting this choice right accelerates your whole development lifecycle. Poor choices, on the other hand, lead to data corruption, deployment failures, and team conflicts.
Why This Matters for Certification The Salesforce Platform Developer I exam tests your knowledge of org types, the application lifecycle, and deployment strategies. Understanding development environments isn’t just practical — it’s essential exam content.
Types of Salesforce Development Environments
Salesforce provides several distinct environment types, each designed for a specific stage of the development lifecycle. Here’s a quick overview before we dive deep:
| Environment | Best For | Lifespan |
|---|---|---|
| Scratch Org | Modern DX, CI/CD, isolated dev | Max 30 days |
| Developer Sandbox | Team development, org-based dev | Permanent |
| Partial Copy Sandbox | UAT, integration testing | Permanent |
| Full Sandbox | Final staging, performance testing | Permanent |
| Developer Edition Org | Learning, certification prep | Permanent (Free) |
| DevOps Center Pipeline | Governed release management | Managed pipeline |
Scratch Orgs: The Modern Developer's Choice
A scratch org is a temporary, source-driven, fully configurable Salesforce environment. Unlike sandboxes, scratch orgs start completely empty — no metadata, no data, no users — and are populated entirely from your version control system.
Key Characteristics
- Lifespan: Default 7 days, maximum 30 days — they expire automatically
- Creation: Via Salesforce CLI, VS Code extensions, or Code Builder
- Starting state: Empty — metadata is deployed from source control
- Edition: You choose the edition (Developer, Enterprise, etc.) per project
- Source tracking: Enabled by default — every change is tracked automatically
Scratch Org Limits by Edition
| Dev Hub Edition | Active Scratch Orgs | Daily Creates |
|---|---|---|
| Developer Edition | 3 | 6 |
| Enterprise Edition | 40 | 80 |
| Unlimited Edition | 100 | 200 |
Creating a Scratch Org via CLI
# Step 1 — Authorize your Dev Hub
sf org login web --set-default-dev-hub --alias MyDevHub
# Step 2 — Create a scratch org (7-day default)
sf org create scratch --definition-file config/project-scratch-def.json --alias MyScratchOrg
# Step 3 — Open the scratch org in browser
sf org open --target-org MyScratchOrg
When to Use Scratch Orgs
Scratch orgs are the best choice when you want:
- Isolated environments per developer
- CI/CD pipeline integration
- Parallel feature development
- Experimentation with features not yet in your production org
They are especially powerful in team settings where multiple developers need their own environment — no stepping on each other’s changes.
Scratch Org Shapes & Snapshots
Two powerful features extend scratch org utility:
- Org Shapes capture configuration settings from an existing production org so your scratch orgs mirror production’s feature set — without complex manual setup.
- Scratch Org Snapshots let you back up a scratch org’s metadata state and restore it rapidly, eliminating repetitive setup steps across the team.
Sandboxes: Tried, Tested, and Reliable
A Salesforce sandbox is a copy of your production org — it replicates your metadata (configuration, code, customizations) and optionally your data. Sandboxes are linked to production and follow the same edition, licenses, and features.
Salesforce offers four distinct sandbox types, each calibrated for different team sizes, use cases, and data requirements:
Developer Sandbox
- Copies all metadata from production but no data
- Designed for individual development and unit testing
- Storage: 200 MB data / 200 MB file
- Refresh interval: Every 1 day
Developer Pro Sandbox
- Same as Developer but with significantly more storage
- Handles larger datasets for integration testing and QA
- Storage: 1 GB data / 1 GB file
- Refresh interval: Every 1 day
Partial Copy Sandbox
- Copies all metadata plus a sample of production data (defined by a sandbox template)
- Ideal for UAT and integration testing
- Storage: 5 GB data / 5 GB file
- Refresh interval: Every 5 days
Full Sandbox
- An exact replica of your production org — all metadata AND all data
- Used for final staging and performance testing
- Storage: Full production data
- Refresh interval: Every 29 days
Important: Only Developer and Developer Pro sandboxes can be added as development environments in a DevOps Center pipeline. Partial Copy and Full sandboxes are used for later pipeline stages such as UAT and staging.
Developer Edition Orgs: Perfect for Learning
A Developer Edition (DE) org is a free, standalone Salesforce environment that anyone can sign up for at developer.salesforce.com/free-trials. It’s permanent (no expiry) and doesn’t require an existing production org.
Developer Edition orgs are ideal for:
- Learning Salesforce from scratch
- Studying for certifications like Platform Developer I
- Building proof-of-concept applications
- Experimenting with new platform features
They have limited storage and user licenses, but are fully functional Salesforce environments — with access to Apex, LWC, Aura, Flow, and most platform APIs.
Certification Tip: All the hands-on exercises in the Salesforce Certified Platform Developer I course at MyTutorialRack use Developer Edition orgs — free, instant to create, and no credit card required. Start coding within minutes.
Side-by-Side Comparison Table
Use this reference table to decide which Salesforce development environment suits your use case:
| Feature | Scratch Org | Developer Sandbox | Full Sandbox | Developer Edition |
|---|---|---|---|---|
| Cost | Included (with Dev Hub) | Included w/ licence | Paid add-on | Free |
| Lifespan | Max 30 days | Permanent | Permanent | Permanent |
| Production Copy | Starts empty | Metadata only | Full copy | Standalone |
| Source Tracking | Default on | Optional | Optional | No |
| CI/CD Ready | Best fit | Possible | Staging | No |
| DevOps Center | Dev stage | Dev stage | Staging/UAT | No |
| Best For | Modern DX / CI/CD | Team development | Final staging | Learning / Certs |
Using Development Environments in DevOps Center
Salesforce DevOps Center is the modern, click-based replacement for Change Sets. It brings source control (GitHub), work item tracking, and a visual deployment pipeline into the Salesforce UI — making DevOps accessible to admins and developers alike.
At the heart of DevOps Center is the pipeline — a series of stages, each connected to a Salesforce environment. Development environments live at the beginning of the pipeline. Changes are “promoted” stage by stage until they reach production.
A Typical DevOps Center Pipeline
Dev Env → Integration → UAT → Staging → Production
(Scratch / Dev Sandbox) (Merge & test) (Business testing) (Final validation) (Live release)
DevOps Center automatically:
- Tracks changes made in development environments
- Integrates with GitHub for version control
- Enables click-based deployments — no CLI required
- Bridges the gap between admins and pro-code developers
Hybrid Teams Welcome: A developer can commit code via VS Code and CLI, while an admin manages the same work item through the DevOps Center UI — both contributing to the same GitHub branch.
How to Add Development Environments to a DevOps Project
Once you have a DevOps Center project set up and connected to GitHub, adding development environments is straightforward. Here is the complete step-by-step process:
Step 1 — Open Your DevOps Center Project From the Salesforce App Launcher, search for “DevOps Center” and launch the app. Click on the project you want to configure.
Step 2 — Navigate to the Pipeline View Inside the project, you’ll see the pipeline with its stages. The “Development Environments” section is where individual developer orgs connect.
Step 3 — Click “Add Development Environment” Under the Development Environments section, click the Add Development Environment button to begin connecting an org.
Step 4 — Provide a Unique Name and Log In Enter a descriptive name for the environment (e.g., Dev-John-Feature-Auth), then click Login and authenticate with the sandbox or scratch org credentials.
Step 5 — Understand Supported Environment Types Only Developer sandboxes, Developer Pro sandboxes, or Scratch Orgs can be added as development environments in DevOps Center. Full and Partial Copy sandboxes are used for later pipeline stages.
Step 6 — Sync the Environment (If Out of Sync) If prompted with “This environment is out of sync,” click Go to Environment Tab, then click Sync → Start Sync to align the environment with the pipeline branch.
Step 7 — Activate the Pipeline After all environments are connected, click the Activate button to make the pipeline live. Work items can now be assigned and changes tracked across the team.
Multiple Developers, Multiple Environments: You can add multiple development environments to the same project pipeline — one per developer. Each developer selects their own environment when picking up a work item, keeping changes isolated until integration.
Which Environment Should You Choose?
There’s no single “right” answer — the best environment depends on your team’s size, project stage, and development approach. Here’s a practical decision framework:
- Learning Salesforce or studying for certifications? → Use a Developer Edition org — free, instant, no setup required.
- Want to try a new feature in isolation? → Use a Scratch Org — create, test, discard, repeat.
- Team doing traditional org-based development? → Use Developer or Developer Pro Sandboxes.
- Need integration or UAT testing with realistic data? → Use a Partial Copy Sandbox.
- Need a final staging environment that mirrors production exactly? → Use a Full Sandbox.
- Adopting modern DevOps and CI/CD? → Use Scratch Orgs in a DevOps Center pipeline backed by GitHub.
In practice, most enterprise teams use a combination: scratch orgs for initial development, a developer sandbox for integration, partial copy for UAT, and a full sandbox for staging — all managed through DevOps Center.
Ready to Master All of This?
If you’re serious about becoming a Salesforce developer — and earning the Platform Developer I certification — you need more than documentation. You need structured, hands-on learning.
The Salesforce Certified Platform Developer I Course at MyTutorialRack covers everything in this guide — and the entire exam blueprint:
- LWC & Aura Components (hands-on)
- Apex, SOQL, and Triggers deep dive
- Org types, development environments, and the application lifecycle
- Deployment strategies and DevOps Center
- Exam-focused practice questions
- Real-world projects
Frequently Asked Questions
What is the difference between a Sandbox and a Scratch Org in Salesforce?
A sandbox is a copy of your production org (metadata and optionally data), linked to production, with a persistent lifespan. A scratch org is a temporary (max 30 days), empty environment created from source control — not a copy of production. Scratch orgs are ideal for source-driven development and CI/CD pipelines, while sandboxes are better for org-based development with real production data context.
Can I use a Developer Edition org as a development environment in DevOps Center?
No. Developer Edition orgs cannot be added as development environments in DevOps Center pipelines. You can only connect Developer sandboxes, Developer Pro sandboxes, or Scratch Orgs as development environment stages. Developer Edition orgs are great for learning but are not supported in the DevOps Center pipeline flow.
How many scratch orgs can I create per day?
It depends on your Dev Hub edition. Developer Edition hubs allow 3 active scratch orgs and 6 creations per day. Enterprise Edition hubs allow 40 active / 80 per day. Unlimited and Performance Edition hubs allow 100 active / 200 per day. If you hit these limits, delete existing scratch orgs before creating new ones.
Which development environment is best for the Platform Developer I exam?
A free Developer Edition org is the ideal environment for Platform Developer I exam preparation. It’s free, permanent, and supports all the features tested — including Apex, LWC, Aura, SOQL, triggers, and deployment concepts. Pair it with structured course training for the fastest path to certification.
What types of environments can be added to a DevOps Center pipeline?
DevOps Center supports Developer Sandboxes and Developer Pro Sandboxes as development environment stages, and Scratch Orgs for source-driven development. For later stages like UAT and staging, Partial Copy and Full sandboxes are typically used. The final release environment (production destination) is your production org or a Full sandbox.
Is Salesforce DevOps Center free?
Yes. DevOps Center is a free managed package installable in Professional (with API access), Enterprise, Unlimited, and Developer Edition orgs — at no additional cost. It represents Salesforce’s commitment to democratizing DevOps practices across the entire Salesforce ecosystem.
Conclusion
Salesforce development environments are the foundation of every successful Salesforce project. Whether you’re a solo learner spinning up a free Developer Edition org, a developer working with scratch orgs in a CI/CD pipeline, or a release manager orchestrating a full DevOps Center workflow — the right environment makes all the difference.
Here’s what to remember:
- Use Developer Edition orgs for learning, certification prep, and experimentation.
- Use Scratch Orgs for modern source-driven development, CI/CD, and team isolation.
- Use Sandboxes (Developer, Partial, Full) for org-based workflows and realistic testing.
- Use DevOps Center to bring all environments together in a governed, GitHub-integrated pipeline.
As Salesforce continues evolving — with features like Scratch Org Snapshots, Org Shapes, Quick Clone for sandboxes, and deeper DevOps Center automation — staying current on development environments is not optional for serious Salesforce professionals. It’s the edge that gets you certified, promoted, and building better solutions.
Start Your Platform Developer I Journey Today
Don’t leave your certification to chance. The Salesforce Certified Platform Developer I course at MyTutorialRack gives you the structured curriculum, hands-on labs, and exam-focused practice you need to pass with confidence.
