United States
Deploy from N. Virginia, Ohio, or Oregon for products serving customers across the United States, on either coast.
Explore web hosting →Global infrastructure · 4 continents
Run your application close to the people using it.
Nineteen published locations across North America, South America, Europe, and Asia Pacific. Deploy websites, APIs, background jobs, AI agents, and data services from one managed platform, and keep pricing, location, and operations visible on every one of them.
- 19
- Published deployment locations
- 4
- Continents covered by the catalog
- 12
- Markets served from an in-region location
- 1
- Platform for compute, data, and operations
Wherever your customers already are.
Each market below is served from a location that actually exists in the catalog. We name the city, not a marketing region.
Canada
Run applications from Central Canada for Canadian traffic and teams that want their workloads on Canadian soil.
Explore web hosting →Brazil
Serve Brazil and the wider Latin American market from São Paulo instead of routing every request north.
Explore web hosting →United Kingdom
Choose London for applications serving the United Kingdom, with managed HTTPS, logs, and scaling included.
Explore web hosting →Germany
Deploy to Frankfurt for German and Central European traffic and for workloads that must stay inside the EU.
Explore web hosting →France
Run customer-facing applications from Paris with Git deployments and built-in operations.
Explore web hosting →Spain
Use the Spain location for websites and applications serving Spain and Southern Europe.
Explore web hosting →Sweden
Stockholm covers the Nordics, with the same pricing model and operational tooling as every other location.
Explore web hosting →India
Mumbai keeps latency low for products serving India and South Asia, including data-heavy workloads.
Explore web hosting →Singapore
Singapore is the hub for Southeast Asia, alongside Jakarta and Malaysia for in-market deployments.
Explore web hosting →Japan
Tokyo serves Japan, with Seoul and Hong Kong available for the rest of North East Asia.
Explore web hosting →Australia
Sydney covers Australia and New Zealand without sending traffic across the Pacific and back.
Explore web hosting →Every published location, by continent.
Location names come from Darwa’s current public catalog. Test with your own application and users before committing regulated or latency-sensitive workloads.
North America4
- N. VirginiaUnited States · basic
- OhioUnited States · basic
- OregonUnited States · basic
- Central CanadaCanada · basic
Asia Pacific8
- Hong KongHong Kong · premium
- JakartaIndonesia · premium
- MalaysiaMalaysia · premium
- MumbaiIndia · basic
- SeoulSouth Korea · basic
- SingaporeSingapore · basic
- SydneyAustralia · basic
- TokyoJapan · basic
Europe6
- FrankfurtGermany · basic
- IrelandIreland · basic
- LondonUnited Kingdom · basic
- ParisFrance · basic
- StockholmSweden · basic
- SpainSpain · premium
South America1
- São PauloBrazil · basic
One platform, every application layer, any location.
Web hostingNext.js, PHP, WordPress, and websites→Web servicesAPIs, application servers, and WebSockets→Static websitesFrontends delivered through the global edge→Background workersQueues, schedules, and long-running jobs→AI agentsManaged n8n and agent applications→DatabasesPostgreSQL, MySQL, MongoDB, and Redis→
Latency and residency, stated clearly.
Where can I deploy on Darwa?+
There are 19 published locations across North America, South America, Europe, and Asia Pacific. Every location is in the public catalog with its pricing tier shown before you deploy, and any product that supports regions can use any of them.
How do I choose a location?+
Start with where your users are, then check where your data and third-party dependencies live. A request that crosses an ocean twice will always be slower than one that does not, and the platform shows the location on every service so the choice stays visible.
Can I keep application data in a specific country or region?+
Choose a compute location in that region and a compatible regional data service. Darwa never labels a location as being somewhere it is not — if a country is not in the catalog, we do not claim in-country hosting for it. Review your own regulatory obligations before placing regulated data.
Can I run one application in several locations?+
Yes. Deploy separate services per location and put them behind your own routing, or use static websites and the global edge for the frontend while the backend stays in one region. Multi-region orchestration as a single service is not in the product yet.
Does pricing change between locations?+
Locations are tiered. Basic locations use the standard price, and premium ones carry a documented multiplier. Both the tier and the resulting price appear in the UI before you deploy.
What if the country I need is not listed?+
Tell us which market and workload. The catalog grows based on where customers actually run, and we would rather add a real location than rebadge an existing one.