The pattern: sign up at developer.salesforce.com, log in periodically to prevent reclamation, use for learning and building, graduate to sandboxes or production orgs when work warrants. The cost is zero; the value is access to a full-featured Salesforce environment for indefinite use.
- Sign up at developer.salesforce.com
Provide email, name, username (must be globally unique on Salesforce), security question. Salesforce provisions the org within minutes.
- Log in and reset the temporary password
Welcome email contains the login URL and temporary password. First login forces password reset.
- Explore the org and verify feature access
Object Manager, Setup, Flow Builder, Apex Developer Console. Confirm the features you plan to use are accessible.
- Use for Trailhead modules, certification prep, or proof-of-concept work
The org supports most learning activities. Configure objects, write Apex, build Flows, configure Permission Sets.
- Log in every few months to prevent reclamation
Inactivity reclamation runs at 365 days. Periodic login resets the clock; calendar reminder helps.
- Document the org URL and username
Easy to lose track of which Developer Edition org is for what. Maintain a list with purpose and last-login date.
- Graduate to sandbox or Trial Edition when work needs production-grade features
Developer Edition limits make it unsuitable for production. When work needs more (sandbox refresh, production user counts), move to the appropriate edition.
Developer Edition; free, persistent, full-feature for learning.
2 users included. No expansion beyond the included count.
Small (typically 5 MB data, 20 MB files). Suitable for learning, not production data volume.
365 days typical before reclamation. Periodic login resets the clock.
Most platform features available; some enterprise add-ons and sandbox refresh excluded.
- Developer Edition orgs reclaim after extended inactivity. Periodic login is non-optional for orgs with work to preserve.
- The username must be globally unique on Salesforce. Common names are taken; appending a random number or organizational suffix is usual.
- Developer Edition is not suitable for production. The user count, storage, and SLA limits are intentional and not expandable.
- Some enterprise features (Shield, certain Industries Cloud) are not available or limited in Developer Edition. Confirm feature scope before assuming the org supports your use case.
- Sandbox refresh is not supported from Developer Edition. Use a Trial Edition or partner-provided sandbox for sandbox-required workflows.