What is ServiceNow data-center strategy through 2027?

The Footprint Today

AWS regions (primary hyperscaler):

• us-east-1, us-east-2, us-west-2 (commercial US)
• AWS GovCloud (US-East, US-West) for FedRAMP High + DoD IL5
• eu-west-1 (Ireland), eu-central-1 (Frankfurt), eu-west-2 (London)
• ap-southeast-2 (Sydney), ap-northeast-1 (Tokyo), ap-south-1 (Mumbai)
• Trainium2 capacity in us-east-2 for Now LLM inference

Azure regions:

• East US, West US 2 for commercial multi-cloud customers
• Azure Government (US Gov Virginia, US Gov Texas) for FedRAMP High parity
• UK South for UK GovCloud workloads
• Germany West Central for EU sovereign-adjacent

GCP regions:

• us-central1, us-east4 for commercial spillover + GenAI co-location
• europe-west4 (Netherlands) for EU multi-cloud
• Smaller footprint than AWS/Azure, used selectively for AI workloads

Sovereign cloud regions:

• Germany sovereign cloud (BSI C5 + future EUCS)
• France SecNumCloud-aligned (via partner)
• UK GovCloud High (live, MOD-eligible)
• Saudi Arabia (PIF / Vision 2030 alignment, Riyadh)
• India (MeitY-empaneled, Mumbai + Hyderabad)
• Australia IRAP PROTECTED (Canberra + Sydney)

Owned data centers (held flat):

• San Jose, CA (HQ-adjacent, legacy)
• Toronto, ON (Canadian residency)
• Amsterdam, NL (legacy EU)
• Equinix colos in 8+ metros for low-latency edge

What Drives Expansion 2026-28

• Sovereign cloud regulations — EUCS (EU Cloud Services scheme) finalization, UK NCSC guidance, Saudi NCA cloud framework, India DPDP Act enforcement, Australia Hosting Certification Framework refresh
• FedRAMP High demand — DoD IL5 and IL6 RFPs increasingly require ServiceNow as ITSM standard; capacity in AWS GovCloud + Azure Gov is the gating factor on bookings
• GPU capacity for Now LLM inference — Now Assist + AI Agent Studio inference is doubling QoQ; NVIDIA Blackwell H200/B200 contracts and AWS Trainium2 commits go out 18-24mo
• Named-customer requirements — Deutsche Bank, BMW, Saudi Aramco, BHP, Tata Consultancy Services all driving region-specific buildouts as deal conditions
• Workflow Data Fabric residency — federated query across customer-owned data lakes requires per-region presence to keep query plans inside sovereign boundaries
• AI Control Tower telemetry — agent observability data is high-volume and sticky; needs regional capacity to avoid egress costs

The Sovereign Cloud Strategy

• Germany sovereign cloud — BSI C5 Type 2 attested today; positioning for EUCS "High" tier when finalized; Deutsche Telekom + SAP partnerships in play
• France SecNumCloud — partner-led delivery (via OVHcloud/Outscale), targets defense + intelligence accounts
• UK GovCloud High — MOD-cleared, used by HMRC, NHS Digital expansion, Ministry of Justice
• Saudi Arabia — Vision 2030 mandate, PIF investment alignment, Aramco + STC + Saudi Vision Realization Office deployments
• India MeitY DPDP — empaneled as cloud service provider; TCS, Infosys, HDFC, Reliance Jio as anchor tenants
• Australia IRAP PROTECTED — Defence + Home Affairs + ATO; Canberra-region buildout active
• Named-customer wins per region justify the GM drag during ramp

The GPU + AI Inference Strategy

• NVIDIA partnership — multi-year H200/B200 commit announced March 2024, expanded 2025 to include Blackwell Ultra; co-developed Now LLM with NVIDIA NIM microservices
• AWS Trainium2 adoption — second-source GPU strategy to reduce NVIDIA dependency; Now LLM 4o-class models being ported to Trainium2 for inference cost reduction
• GPU capacity planning — 18-24mo forward contracts; co-located in AWS us-east-2, Azure East US, and a small NVIDIA DGX Cloud footprint
• Now LLM hosting — exclusively on ServiceNow-controlled GPU pools (no third-party LLM hosting for customer data); inference latency target sub-300ms p95
• AI Agent Studio inference cost optimization — dynamic routing between Now LLM (cheap) and partner LLMs (Anthropic, OpenAI via private endpoint) based on task complexity

The Cost Discipline

• Each new sovereign region adds 50-150bps of GM drag for the first 12-18 months until utilization climbs above 60%
• Multi-cloud cost premium — Azure + GCP run roughly 8-15% more expensive than AWS-primary at equivalent capacity, justified only by customer concentration or sovereign requirement
• Sovereign cloud premium pricing — list price uplift of 20-35% on sovereign SKUs absorbs most of the infrastructure cost; net GM drag is the timing gap
• CFO Gina Mastantuono commentary — repeated framing on "infrastructure leverage as we scale Now Assist"; expect 50-100bps of GM expansion in FY27 from GPU utilization improvements
• Trainium2 substitution math — every 10% of Now LLM inference moved from H200 to Trainium2 saves an estimated 30-40% per-token cost

What's NOT In The Strategy

• No aggressive China expansion — geopolitical risk + data residency requirements make China-mainland a hard pass; Hong Kong via partner only
• No LATAM ex-Brazil sovereign cloud — Mexico, Argentina, Chile served from AWS us-east-1 + Sao Paulo; no dedicated sovereign builds planned through 2027
• No own-DC build-out beyond named existing sites — capex discipline; the Toronto/Amsterdam/San Jose footprint is held flat, all growth is hyperscaler
• No Oracle Cloud expansion — OCI not in the multi-cloud roadmap despite Oracle's GenAI push; ServiceNow staying on AWS/Azure/GCP triumvirate
• No edge-compute / on-prem appliance push — unlike Salesforce Data Cloud's Hyperforce-on-prem flirtation, ServiceNow is pure cloud; edge is partner territory

Region x Cloud Provider Status Matrix

Driver to Region to Outcome Flow

Related on PULSE

• [What is Datadog data-center strategy through 2027?](/knowledge/q1696)
• [What is Salesloft data-center strategy through 2027?](/knowledge/q1815)
• [What is Outreach data-center strategy through 2027?](/knowledge/q1756)
• [What is Salesforce data-center strategy through 2027?](/knowledge/q1550)
• [What is ServiceNow developer-platform strategy through 2027?](/knowledge/q1666)
• [What is ServiceNow's M&A strategy through 2028?](/knowledge/q1655)

Geographic Expansion and Regulatory Compliance

ServiceNow's data-center strategy is heavily influenced by evolving data sovereignty regulations across key markets. In the European Union, the company is expanding its Frankfurt and London regions to comply with GDPR and the upcoming EU Data Act, which mandates stricter data localization for critical infrastructure. Similarly, in Saudi Arabia, ServiceNow partnered with Alibaba Cloud to launch a dedicated sovereign region in Riyadh, addressing the National Data Management Office's requirements for government workloads. For India, the company is leveraging Azure's Mumbai region to meet Reserve Bank of India guidelines for financial services data. These sovereign builds often require 18–24 months from announcement to operational readiness, as they involve custom network isolation, local support teams, and compliance certifications like FedRAMP equivalency. By 2027, ServiceNow expects to have 12–15 sovereign regions globally, up from 8 in 2024, with each region costing $10–$30 million to establish depending on local infrastructure costs.

AI Workload Optimization and Cost Management

The shift to AI-native workloads is reshaping ServiceNow's capacity planning. The Now LLM and AI Agent Studio require GPU clusters for both training and inference, with inference demand projected to grow 3–5x annually through 2027. To manage costs, ServiceNow is adopting a tiered GPU strategy: NVIDIA H100s for training, Blackwell B200s for high-throughput inference, and AWS Trainium2 for cost-sensitive inference tasks. The company estimates that Trainium2 can reduce inference costs by 30–40% compared to H100s for standard NLP tasks, making it viable for high-volume use cases like virtual agent conversations. ServiceNow is also implementing spot instance usage for batch inference jobs, targeting 20–30% of GPU capacity from spot markets by FY27. This hybrid approach aims to keep AI infrastructure costs below 15% of total cloud spend, compared to 25%+ for some competitors.

Disaster Recovery and Business Continuity

ServiceNow's multi-cloud strategy extends to disaster recovery, with active-active configurations across AWS and Azure for critical workloads. The company maintains a Recovery Time Objective of 15 minutes and a Recovery Point Objective of 5 minutes for its Now Platform, achieved through synchronous data replication between paired regions. For sovereign clouds, DR is handled locally—for example, the EU sovereign region replicates data between Frankfurt and Paris, while the UK region uses London and a planned Manchester site. ServiceNow is also piloting a "chaos engineering" program that randomly fails over 5–10% of tenant workloads each quarter to validate resilience. By 2027, the company aims to have all tier-1 workloads running in at least three geographically separated availability zones, with automated failover testing every 30 days. This approach adds 10–15% to infrastructure costs but is required for enterprise SLAs and insurance compliance.

Sources

• ServiceNow official website — product documentation and strategic announcements regarding data-center operations and cloud infrastructure.
• Gartner — industry analysis reports on enterprise cloud and IT service management trends.
• Forrester Research — research on digital workflow platforms and data-center modernization.
• IDC (International Data Corporation) — market forecasts and vendor strategy analyses for cloud and data-center services.
• Uptime Institute — independent research and benchmarks on data-center reliability and infrastructure.
• CRN (Channel Partner Network) — news and analysis on ServiceNow partner ecosystem and infrastructure developments.

FAQ

Does ServiceNow plan to shut down all its owned data centers? No. ServiceNow is keeping its owned footprint flat in Toronto, Amsterdam, San Jose, and Equinix sites. These are used for legacy workloads and specific compliance needs, but net-new capacity is directed to hyperscalers and sovereign clouds. Owned sites will likely represent only about 5% of total capacity by FY27.

Why is ServiceNow using three different hyperscalers (AWS, Azure, GCP) instead of just one? The multi-cloud approach gives ServiceNow regional breadth and access to elastic GPU capacity from each provider. It also avoids vendor lock-in and allows them to negotiate better pricing. Each hyperscaler offers unique AI hardware—like AWS Trainium2—that ServiceNow uses for specific inference workloads.

What is a "sovereign cloud" and why does ServiceNow need them? Sovereign clouds are data centers operated within a specific country or region that guarantee data never leaves that jurisdiction. ServiceNow builds these in places like the EU, UK, Saudi Arabia, India, and Australia to meet strict regulatory requirements. Without them, ServiceNow would be blocked from government and regulated-industry contracts in those regions.

How does ServiceNow decide where to put new data centers? Every decision is a cost-versus-compliance tradeoff. If a region has strict data residency laws, ServiceNow may build a sovereign cloud there even though it adds 50-150 basis points of gross margin drag for 12-18 months until utilization catches up. In regions without such laws, they use hyperscalers for lower cost and faster deployment.

Will ServiceNow's AI features work differently depending on which region my data is in? The AI models themselves are the same, but inference may happen on different hardware (NVIDIA Blackwell or AWS Trainium2) depending on regional capacity. Data residency is enforced per-tenant via region pinning, so your data never leaves your chosen region. Performance should be consistent, though latency may vary slightly based on local infrastructure.

What does "infrastructure leverage" mean in ServiceNow's strategy? It means ServiceNow wants to grow revenue faster than infrastructure costs. By shifting to hyperscalers and optimizing GPU utilization, they aim to keep gross margins stable even as AI workloads increase. CFO Gina Mastantuono emphasizes this on earnings calls because it's key to maintaining profitability while scaling.

Bottom Line

ServiceNow's 2026-27 infrastructure strategy is disciplined multi-cloud hyperscaler-primary, with surgical sovereign-cloud builds where regulator gates justify the GM drag, and aggressive GPU dual-sourcing (NVIDIA + Trainium2) to keep Now Assist inference economics workable. The owned-DC footprint is frozen, capex is going to hyperscaler commits, and the named CFO commentary on "infrastructure leverage" telegraphs FY27 GM expansion as GPU utilization climbs. The differentiator vs. Salesforce/Workday isn't the footprint itself — it's the willingness to take 50-150bps of short-term GM pain for sovereign builds that unlock multi-year named-customer ARR. (see also: q1613, q1626, q1627)

People also search for: what is servicenow data-center strategy through 2027 · servicenow data-center strategy through 2027 explained · servicenow data-center strategy through 2027 definition