engineering··5 min read·WoWSQL Team

Indian SaaS Selling to the US: Pick Your DB Region

Indian SaaS with US customers? Choose Mumbai, US East or both: latency maths, what the DPDP Act says on transfers, and how WoWSQL sets region per project.

If most of your paying customers are in the US, put your production database in US East (N. Virginia), next to them and next to your app servers, and keep Mumbai for products whose users are mainly in India. If you have real customer bases in both markets, run one project per market instead of stretching a single database across the world. WoWSQL lets you pick Mumbai (ap-south-1), US East (us-east-1) or Frankfurt (eu-central-1) for each project, so you can start with one region and add another when a second market is real.

This guide is for Indian founders building SaaS for global buyers. It covers the latency maths, what India's Digital Personal Data Protection (DPDP) Act actually says about sending data abroad, the three setups that work, and how to move later. Facts were checked on 22 November 2026.

Key facts

  • WoWSQL regions (regions API, checked 22 November 2026): Asia Pacific (Mumbai) ap-south-1, US East (N. Virginia) us-east-1, Europe (Frankfurt) eu-central-1. You choose the region when you create a project. There is no UK region.
  • WoWSQL plans (pricing): Free $0 (1 project, 256 MB database, 10,000 MAU); Pro $25/month (first dedicated project, 10 GB database, 100,000 MAU, daily backups kept 7 days); Scale $99/month (high-performance dedicated project, 2,000,000 MAU, custom domains). Yearly billing saves 7%.
  • DPDP Act, section 16 (Act text on meity.gov.in): the Central Government may restrict transfers to countries it notifies. It is a blocklist model, not a requirement to keep all data in India.
  • DPDP Rules, 2025 (MeitY): notified on 13 November 2025. Rule 15 (transfers) and most obligations start 18 months after publication; Rule 13(4) lets the government require Significant Data Fiduciaries to keep specified data in India.
  • Physics: light in optical fibre covers about 200 km per millisecond. Mumbai to N. Virginia is about 12,850 km in a straight line, so no network can do a round trip in under about 129 ms.
  • Company: WoWSQL Technologies Private Limited, Tamil Nadu, India; NVIDIA Inception member; DPIIT-recognised startup.

Why the region matters more than you think

A single database round trip is rarely the problem. The problem is that one page load or one API call usually makes several queries, often one after another. Each sequential query pays the full round trip between your app server and the database.

Here is the lower bound set by physics, using straight-line distance and light in fibre at about 200,000 km/s. Real routes are longer, so real numbers are higher. Treat these as floors, not forecasts.

Path Straight-line distance Minimum round trip
Bengaluru → Mumbai ~845 km ~8 ms
Delhi → Mumbai ~1,150 km ~11 ms
New York → N. Virginia (Ashburn) ~350 km ~4 ms
San Francisco → N. Virginia ~3,880 km ~39 ms
New York → Mumbai ~12,540 km ~125 ms
San Francisco → Mumbai ~13,490 km ~135 ms
Mumbai → Frankfurt ~6,560 km ~66 ms

Distances are great-circle calculations we ran on 22 November 2026; they are not measurements of any provider's network.

Now multiply. A dashboard that runs 6 queries in sequence, with an app server in Virginia and a database in Mumbai, waits at least 6 × 129 ms ≈ 0.8 seconds before it does any work. The same dashboard with both in Virginia waits a few milliseconds. That is the whole argument: put the database where the app server is, and put the app server near most of your paying users.

Two corollaries:

  1. The user-to-app hop matters less than the app-to-database hop. A US customer reaching an app in Virginia pays one round trip per request. The app then talks to the database many times per request.
  2. Frontends served from a CDN hide some distance, databases don't. Static assets can sit at an edge near every user. Your rows live in one region.

What the DPDP Act says about storing data outside India

Founders often assume Indian law forces them to host in Mumbai. For most SaaS companies it does not, at least on the text as of today.

  • Section 16(1) of the Digital Personal Data Protection Act, 2023: "The Central Government may, by notification, restrict the transfer of personal data by a Data Fiduciary for processing to such country or territory outside India as may be so notified." Transfers are allowed unless a country is notified. We could not find any such notification on MeitY's site when we checked on 22 November 2026.
  • Section 16(2) keeps stricter sector laws in force. If you handle payments data, insurance, or other regulated data, your sector regulator's rules can require local storage regardless of the DPDP Act. Check those first.
  • Section 17(1)(d) exempts certain processing of personal data of people outside India when it happens under a contract with a person outside India. Whether it covers your own SaaS users is a question for a lawyer, not a blog post.
  • Rule 15 of the DPDP Rules, 2025 allows transfers abroad, subject to requirements the government may set about making data available to a foreign State.
  • Rule 13(4) lets the government require Significant Data Fiduciaries to keep specified personal data, and its traffic data, inside India. Most early-stage SaaS companies will not be designated as one, but it is the clause to watch if you grow large in India.
  • Timing: Rule 1 says Rules 3 and 5 to 16 come into force 18 months after publication. The gazette notification is dated 13 November 2025, so those obligations start in mid-May 2027.

So the honest summary: the DPDP Act mostly cares about how you process Indian users' data (notice, consent, security, breach reporting), not where the server sits. Your US customers will mostly care about their own laws and contracts. Read the Act and Rules yourself, and get legal advice for anything regulated. Our older post on data residency in India for Postgres goes deeper on the India side.

Three setups that work

Setup 1: One project in US East

Best for: SaaS where most revenue and usage comes from the US, and Indian users are a minority or are your own team.

Create the WoWSQL project in us-east-1, run your API or server functions in the same region, and accept that users in India see higher latency. Your team in Bengaluru or Chennai will notice the dashboard is slower for them; your customers will not.

Setup 2: One project in Mumbai

Best for: India-first products that sell a few US accounts, or B2B tools where the buyer is Indian even if their customers are abroad.

Keep the database and app in ap-south-1. If US usage grows, look first at reducing sequential queries (batch reads, use views or SQL functions, cache read-heavy endpoints) before moving regions.

Setup 3: One project per market

Best for: products with real customer bases in both India and the US (or the EU), especially when each customer's data only needs to live in one place.

Create one project in Mumbai and one in US East (and one in Frankfurt for EU customers if needed). Assign each customer account to a region at sign-up and route requests to that project's URL. This is the cleanest way to give each market low latency and a clear answer to "where is my data?".

What it costs you: two schemas to migrate, two sets of keys, and no cross-region joins. Keep migrations in version control and apply them to every project with the WoWSQL CLI (wowsql migration up, see the CLI migration docs). For tenant design inside each project, see multi-tenant SaaS on Postgres.

On pricing: WoWSQL Free covers one project. Pro at $25/month includes the first dedicated project, so check the pricing page or ask support about the cost of a second project before you plan a split.

What we do not recommend

Do not try to run a single database that is "close to everyone". Cross-continent replication with writes in two places is hard to get right, and WoWSQL's docs do not describe multi-region replication for a project. Splitting by market is simpler and more honest.

Region options compared (checked 22 November 2026)

Provider India region US regions Europe regions Notes
WoWSQL Mumbai ap-south-1 US East (N. Virginia) Frankfurt Flat plans $0 / $25 / $99; no UK region (regions API)
Supabase Mumbai ap-south-1 N. California, Oregon, N. Virginia, Ohio Ireland, London, Paris, Frankfurt, Zurich, Stockholm 17 specific regions listed (Supabase regions)
Neon None (nearest is Singapore) N. Virginia, Ohio, Oregon Frankfurt, London 8 AWS regions (Neon regions, updated 18 Nov 2026)
Appwrite Cloud Bangalore listed as "coming soon" New York, San Francisco Frankfurt (Amsterdam and London coming soon) Plus Sydney, Singapore, Toronto (Appwrite regions)

Where others are better: Supabase offers far more regions, including Mumbai and several US options, and Neon and Supabase publish SOC 2 reports that some US enterprise buyers ask for. WoWSQL does not claim SOC 2 or HIPAA, so if a US customer's security questionnaire requires a SOC 2 report from every sub-processor, factor that in before you choose. Where WoWSQL fits: a flat monthly price, a Mumbai region alongside US East and Frankfurt, and an Indian company working in your time zone.

How to choose in 15 minutes

  1. List where your paying users are. Use revenue, not sign-ups. If 70%+ of revenue is in one market, start with Setup 1 or 2.
  2. List where your app servers run. If your API is on a US host, a Mumbai database will hurt. Move one or the other so they share a region.
  3. Check for sector rules. Payments, lending, insurance and health data can carry local-storage requirements beyond the DPDP Act.
  4. Check customer contracts. Some US and EU buyers specify hosting regions or require named certifications.
  5. Create the project in the chosen region at wowsql.com. Region is picked in the create-project form.
  6. Measure from where your users are. Run this from a laptop or server in each market against a real table:
curl -s -o /dev/null \
  -H "apikey: $WOWSQL_ANON_KEY" \
  -w 'connect %{time_connect}s  first byte %{time_starttransfer}s  total %{time_total}s\n' \
  "https://$PROJECT.wowsqlconnect.com/rest/v1/plans?select=id&limit=1"

time_starttransfer includes the trip to the database region, so compare it across regions rather than trusting any published number, including ours.

Moving regions later

WoWSQL's docs describe choosing a region when you create a project; they do not describe moving an existing project. Plan a move as a migration:

  1. Create a new project in the target region and enable Authentication if you use it.
  2. Export the old database with pg_dump (schema first, then data) and load it into the new project.
  3. Re-apply RLS policies and test them with a signed-in user, as in the row level security guide.
  4. Switch the frontend's project URL and keys, then keep the old project read-only until you are sure.

The same steps work when moving between providers; see Migrate from Supabase to WoWSQL.

Related guides

FAQ

Should an Indian startup with US customers host its database in Mumbai or US East?

Host where most of your paying users and your app servers are. If most revenue is from the US, use US East (N. Virginia); if most users are in India, use Mumbai. A database on the other side of the world adds at least about 125–135 ms per round trip, and pages usually make several. WoWSQL offers both regions, plus Frankfurt, and you choose per project.

Does the DPDP Act require Indian companies to store data in India?

Not as a general rule. Section 16 lets the government restrict transfers to countries it notifies, and we found no such notification on MeitY's site as of 22 November 2026. Sector regulators can still require local storage, and Rule 13(4) of the DPDP Rules, 2025 lets the government require Significant Data Fiduciaries to keep specified data in India. Get legal advice for regulated data.

When do the DPDP Rules' transfer provisions take effect?

Rule 1 of the DPDP Rules, 2025 says Rules 3 and 5 to 16, including Rule 15 on transfers, take effect 18 months after publication. The notification is dated 13 November 2025, so that is mid-May 2027.

Can I run one WoWSQL project in Mumbai and another in US East?

Yes. Region is chosen per project, so you can run a Mumbai project for Indian customers and a US East project for US customers, with the same schema applied by CLI migrations. The Free plan covers one project, and Pro includes the first dedicated project, so check pricing for additional projects.

Does WoWSQL replicate one database across regions?

Not according to its docs: each project runs in one region, and cross-region replication is not described. For multiple markets, use one project per market and route each customer to their project, rather than replicating writes across continents.

Is WoWSQL SOC 2 certified for US enterprise customers?

No. WoWSQL does not claim SOC 2, HIPAA or GDPR certification. If your US buyers require a SOC 2 report from your database provider, check that requirement before choosing; Supabase and Neon publish SOC 2 positions.

Create a free WoWSQL project · Pricing · Docs