Global Locations

No. ERPStack is remote-first and holds no office, legal entity or staff in any of the 40 locations listed on this page. What is local is the deployment: the system runs in the AWS or Microsoft Azure region your regulator expects — ap-south-1 for Mumbai, eu-west-2 for London, ap-southeast-2 for Sydney — and the contract, the invoicing format and the audit exports are built for that jurisdiction. One senior team delivers across every location, inside your working hours, on the same Next.js and PostgreSQL stack.

Fifteen of these 40 locations do, and each page names the code: Mumbai (ap-south-1), Hyderabad (ap-south-2), Sydney (ap-southeast-2), Melbourne (ap-southeast-4), Tokyo (ap-northeast-1), Seoul (ap-northeast-2), Hong Kong (ap-east-1), Tel Aviv (il-central-1), Dubai (me-central-1), Zurich (eu-central-2), Stockholm (eu-north-1), Paris (eu-west-3), London (eu-west-2), Frankfurt (eu-central-1) and Singapore (ap-southeast-1). Boston, Chicago, Atlanta, Denver, Houston, Miami, Minneapolis, Phoenix, Portland, Los Angeles and Seattle are instead served by an AWS Local Zone hanging off a parent region.

Residency rules first, latency second. Where a rule pins the data the region is settled before anything else: RBI's payment-data circular keeps a Mumbai ledger in ap-south-1, ITAR technical data keeps a Seattle aerospace build in us-west-2, Swiss banking secrecy keeps Zurich in eu-central-2. Where nothing pins it we take the nearest AWS or Microsoft Azure region, or an AWS Local Zone, with a paired recovery region. Both choices live in Terraform, so the region a locations page names is the region the pipeline actually deploys.

The same way everywhere: fixed-scope milestones against a written specification, with no per-seat licence and no charge for extra users, partner portals or environments. Currency, tax treatment and contracting entity change by jurisdiction; the engineering rate card does not. Because ERPStack keeps no office in these locations, no local overhead is priced into the quote — the cost sits in senior engineering hours plus the AWS or Microsoft Azure bill, which you own directly rather than paying us to resell.

Within reason. ERPStack works remotely across all 40 locations and fixes an overlap window with your team rather than promising 24-hour coverage it cannot staff. European and Middle Eastern locations get a full working-day overlap, Indian and South-East Asian locations most of one, North American locations the morning. Delivery is asynchronous by default — written specifications, pull requests through GitHub Actions, recorded demos — so progress never depends on one call being taken.