Hyperforce Overview

What Is Hyperforce?

Hyperforce is the next-generation Salesforce infrastructure architecture, built for the public cloud. Hyperforce infrastructure is composed of code rather than hardware, so that the Salesforce platform and applications can be delivered rapidly and reliably to locations worldwide, giving customers more choice and control over data residency.

Salesforce products running on Hyperforce benefit from its integration of enhanced standards for compliance, security, agility, and scalability, and from Salesforce’s continued commitment to privacy. By providing a common foundation for deploying our application stacks, Hyperforce accelerates Salesforce’s ability to innovate across product clouds and deliver additional business value to customers.

To see additional information on Hyperforce, please watch this introductory video.

Hyperforce Delivers:

Data Residency – Hyperforce lets customers serve their employees and customers globally while providing choice and control for residency and compliance.
Scalability – Customers will be able to grow and scale their business more flexibly and sustainably.
Security – Hyperforce is secure by default, with least-privileged control, zero-trust principles, and encryption of customer data at-rest and in-transit.
Privacy – Hyperforce provides comprehensive privacy standards that help give customers control and transparency over their customers’ data.
Agility – Hyperforce increases agility with no downtime for releases and general maintenance, faster dev and test environments, and enormous new interoperability with AWS. (Downtime may be required during org migrations or for major technology upgrades.)

NOTE: This document is for informational purposes only, and is not part of any legal or otherwise binding agreement. The policies and practices described in this document are subject to change at Salesforce's sole discretion.

Frequently Asked Questions

General

What products are currently available on Hyperforce?

For the most up-to-date information about products and services that are available on Hyperforce see the Hyperforce SPARC documents in the Trust and Compliance Documentation.

Are there videos I can watch about Hyperforce and getting ready for the move?

Watch the extensive video series to learn about Hyperforce and to get ready for the migration on the YouTube Salesforce Support channel, Get Ready for Hyperforce . There are also events and a Trailblazer Community you can leverage such as, "Ask a Hyperforce Expert ", a Hyperforce Webinar , and the Hyperforce Trailblazer Community .

Is Salesforce Express Connect available in Hyperforce?

No. Hyperforce runs on Amazon Web Services (AWS). Salesforce Express Connect (SEC) provides direct network connectivity only to Salesforce-operated data centers. Customers who want direct network connectivity to Hyperforce must contact their telecom provider to procure and implement a comparable alternative to SEC before upgrading to Hyperforce. The recommended solution uses AWS Direct Connect (DX) with a Public Virtual Interface (VIF) to create a secure connection. Find guidance in How to Access Salesforce Hyperforce Securely and Reliably with AWS Direct Connect. The AWS DX solution is in addition to, not a replacement for, SEC.

Are there additional costs associated with moving to Hyperforce?

There is no additional cost associated with residing on the Hyperforce infrastructure.

Can I expect any changes to my org?

Once you have prepared your org for migration, the org will function just as it does today. Services not hosted on the Hyperforce platform will continue to operate as they do today.

NOTE: Upgrading to Hyperforce results in a change of the Documentation applicable to your Services. For further information, please refer to our Trust and Compliance Documentation and review the Documentation for Services on Hyperforce.

Where can I learn about data residency?

Review the information in the article on Hyperforce Data Residency .

Post Migration

How do I know if we have moved to Hyperforce?

Check for the instance name by Viewing instance information for your Salesforce Organization and then check if the instance is on a Hyperforce infrastructure as noted in Where is my Salesforce instance located article. The Find My Instance map contains symbols and information that will designate "Non-Hyperforce" or "Hyperforce" when the Instance name is entered.

Why are my CRM Analytics dashboards not loading post org migration?

If your CRM Analytics dashboard has not been run recently, it may take some time for the data to refresh after an org migration. The time for your dashboard refresh to complete depends on the size of the data in the dashboard. Refer to CRM Analytics dataflow warnings and errors for more information.

Will my Release and Maintenance Window dates change after upgrading to Hyperforce?

Many customers' maintenance window dates will remain the same; however, some will experience a shift in their maintenance window dates, including Major Release dates, upon migrating to Hyperforce. Two possible date shifts are: (1) If the migration results in your org moving to a region with a different time zone, then the maintenance windows may change to align with the local time where the region is located (2) The org migration may cause a change in pre-planned maintenance dates, including Major Releases, if the target Hyperforce region is on a different maintenance schedule than the first-party data center from which your org is migrating. Refer to the Preferred Salesforce Maintenance Schedule, which can provide further guidance on preparatory actions. Once customers receive notification of their new Hyperforce instance name, they can visit Salesforce Trust (Status Site), enter the instance name, and find their Major Release schedule under the Maintenance Tab on the instance page. All customers experience a shift in their maintenance window duration. The maintenance window for major releases on Hyperforce is 30 minutes, during which the release is delivered with zero downtime.

Why doesn’t my SmartComm managed package work correctly?

If you are not using the current version of the SmartComm managed package, it may not function as expected after your upgrade to Hyperforce. Please review this SmartComm community article (login required) for instructions on how to upgrade to the latest version.

What happened to SVG file previews?

Hyperforce generates file previews as JPGs, not SVGs, regardless of the account preference settings. SVGs that were generated for previously uploaded files will remain accessible, but newly uploaded files will generate JPG previews. The end user experience remains the same -- files preview and download as expected. But, custom implementations using SVG previews will be impacted.

Upgrading to Hyperforce

Why is my org migrating and when will I know when I'm migrating?

We regularly move customers in order to balance our workload and modernize our systems. Customers will receive migration notices containing the Org ID, migration date, and the new target instance name 30 or 90 days before migration based on your support level, and reminder emails 15 days prior. If there are any questions or concerns about when you are migrating, please contact your Salesforce Account Team.

My org was selected to upgrade, but the timing is inconvenient for our business. What are my options?

Migrations take place during Preferred Maintenance Windows. If you have a business need that requires that you move outside your pre-determined migration window, please contact your Salesforce Account Team.

Who receives org migration notifications?

Customers will be notified by receiving Product and Service notifications. Please refer to the Product & Service Notifications knowledge article. It is possible to manage notification preferences using the KB article referenced.

What can customers do to ensure a smooth upgrade to Hyperforce?

Use the Hyperforce Assistant in Setup to guide you through your upgrade and review a summary list of tasks in the Hyperforce Upgrade Preparation Online Help.
Watch the Salesforce Support YouTube video to Get Ready for Hyperforce - Part 5: Org Migration Overview
Prepare for your org migration by following best practices that include updating hard-coded references and allowing all Salesforce required domains.
Review Retain uninterrupted access to Salesforce services on Hyperforce and adopt necessary technical best practices.
For frequently asked questions about org migrations, see our Org Migration FAQ.
Learn more about the org migration process by reviewing our Salesforce Org Migration overview Knowledge Article.
Review the Trust and Compliance Documentation identified here as applicable to Hyperforce, including additional sub-processors for the Services purchased through Salesforce or a third party.

Are trial orgs available?

Trial orgs are available. If you are interested in a new Trial org on Hyperforce, Please contact your Salesforce Account Team. When you convert your trial org to active, paid status, your trial services will be briefly unavailable while Salesforce migrates your org to a production instance.

How is my org affected during the org migration, and how long does the org migration take?

During this planned service downtime, the applicable Salesforce.com org will be in read-only mode. The duration of the planned service downtime is around 3 hours. For more information, review the How to Prepare for an Org Migration Knowledge Article. During this org migration, maintenance notifications aren’t posted on the Salesforce Trust site.

Will Hyperforce instances be listed on the Salesforce Trust site?

Yes, all Hyperforce instances that currently accept customer traffic are live on our Salesforce Trust site.
After upgrading to Hyperforce, subscribe to Trust notifications for your new instance. To learn more about Trust Notifications and how to subscribe, review the Trust Notification User Guide.
- NOTE: During org migrations to Hyperforce, maintenance notifications aren’t posted on the Salesforce Trust site.

If Hyperforce is the future Salesforce platform, why are some orgs schedule for first-party org migrations?

We continue maintaining our first-party data centers to balance utilization and avoid resource contention. If your org is eligible for Hyperforce, we will work to avoid any first-party migrations before your Hyperforce upgrade. However, depending upon the timing of your Hyperforce eligibility and our first-party data center maintenance needs, there is a slim possibility that your org will undergo multiple org migrations.

Security, Compliance, and Contract Information

Are the same certificates and audits available to my org after upgrading to Hyperforce?

Salesforce currently has security controls and audits in place for the Services on Hyperforce. For more information about the status of certifications, please review the certificates and audits that apply to your org and region post upgrade on the Salesforce Certifications, Standards, and Regulations site. You can find this information on the site by clicking on the Service(s) you purchase. Be sure to bookmark this site and check back for additional certificates that will be available at a future date.

What if I require a certification that is currently not on Hyperforce?

Some customers, such as health and life sciences customers, may require certifications that are either not in your current region or take longer to complete. If you are concerned that the certification you need is not listed on the Salesforce Certifications, Standards, and Regulations site, please contact your Salesforce Account Team.

Hyperforce Resilience

What is the resilience model for Hyperforce?

Each Hyperforce region is configured and deployed across at least three separate locations called availability zones (AZs). A system failure in one AZ, such as power or network, does not affect other AZs. These systems are designed to deliver high availability and to recover from failure with minimal disruption.
Hyperforce uses standardized and automated processes to build and deploy a complete operating image, including infrastructure, operating system, applications, and configuration. The images are defined and managed as code. The deployment process is exercised frequently to replace individual instances, for example, to apply patches. The Covered Services’ Disaster Recovery processes are built on the standard deployment process, which ensures that Disaster Recovery is done using a well understood and continually validated process.
For more details, see the “Reliability, Backup, Business Continuity, and Disaster Recovery” section from the Hyperforce Security, Privacy and Architecture document.

To learn more about possible Hyperforce network changes and endpoint updates for SSO, OAuth and JSON Web Tokens, please review Hyperforce Techncial Considerations .

Introducing Hyperforce - General Information & FAQ