Definition
A specific Salesforce server (identified by names like NA1, EU5, CS42) that hosts a group of Salesforce orgs, determining the login URL and API endpoint for the organizations running on that server.
Real-World Example
Consider a scenario where the IT director at Vertex Global is working with Instance to scale their operations using the Salesforce platform. Instance gives them the infrastructure and tools needed to support new business requirements, handle increased data volumes, and serve a growing user base without compromising performance.
Why Instance Matters
An Instance in Salesforce is a specific server (or cluster of servers) that hosts a group of Salesforce organizations. Instances are identified by names like NA1, NA15, EU5, AP12, CS42 (for sandboxes), with the prefix indicating the geographic region (NA for North America, EU for Europe, AP for Asia-Pacific, CS for Customer Sandbox). The instance determines the login URL, API endpoint, release schedule, and physical infrastructure for the orgs running on it.
Knowing your org's instance matters for several reasons: it affects which release wave (preview versus regular) your org gets, when maintenance windows happen, and the URL structure for various Salesforce services. Salesforce's Trust site (trust.salesforce.com) provides instance-specific status information. Hyperforce, Salesforce's modern public-cloud architecture, is gradually replacing the traditional instance model, with orgs being migrated from named instances to Hyperforce regions. Eventually, the explicit instance concept may fade, but for now it remains relevant for any operational work involving specific orgs.
How Organizations Use Instance
- •TerraForm Tech — Monitors trust.salesforce.com for their specific instance to track planned maintenance and incidents affecting their org.
- •NovaScale — Knows their org's instance details for API endpoint configuration in integrations and for verifying release schedules.
- •CodeBridge — Tracks the gradual migration of client orgs from traditional instances to Hyperforce, since the architectural change has implications for some integrations.
