17 Sep 2026
There is no single revenue number or team size that tells a SaaS company it is time to leave AWS. What there is, reliably, is a small cluster of signals that tend to show up together, and once three or four of them are present at once, the economics have usually already shifted even if nobody has run the numbers yet.
There is no single revenue number or team size that tells a SaaS company it is time to leave AWS. What there is, reliably, is a small cluster of signals that tend to show up together, and once three or four of them are present at once, the economics have usually already shifted even if nobody has run the numbers yet.
Early in a company's life, demand is a guess. Cloud is built for exactly that uncertainty, you pay a premium for the right to scale up or down without committing to hardware you might not need. That trade is worth it when you genuinely do not know next quarter's load.
The signal changes the moment growth becomes steady rather than exponential. 37signals, the company behind Basecamp and HEY, described this shift directly when explaining its own move off AWS: the business was “growing steadily and sustainably,” not doubling year over year. Once growth looks like a line instead of a curve, a company can forecast its capacity needs accurately enough that paying for elasticity it no longer needs stops making sense.
This is the single most concrete trigger to track, and the easiest to miss because most finance teams review cloud spend and revenue separately rather than as a ratio. If infrastructure cost as a percentage of revenue has been rising for two or three consecutive quarters, that is not a scaling problem, it is a pricing model mismatch. 37signals went from a cloud bill it considered reasonable to one exceeding 3.2 million dollars a year specifically because usage-based pricing does not naturally flatten the way a maturing company's actual resource needs do.
Data egress out to the internet, cross-Availability Zone traffic, and NAT Gateway processing rarely appear in a company's original cost projections, because they scale with usage patterns that only become visible after the product is live. As of 2026, AWS charges $0.09 per GB for the first 10 TB of monthly internet egress, plus $0.01/GB in each direction for cross-AZ traffic and $0.045/GB for NAT Gateway processing on top of that. For a SaaS product with a distributed architecture, these charges commonly add up to 10 to 30 percent of the total AWS bill. When a finance or engineering leader can point to data transfer as a specific, growing line item rather than an assumed cost of doing business, that is a signal the underlying architecture has outgrown pay-per-byte pricing.
This is the most practical signal of all, because it creates a natural decision window rather than requiring a company to interrupt anything mid-contract. Multi-year Reserved Instance or Savings Plan commitments lock in a discount against on-demand pricing, but they also lock in the assumption that public cloud is still the right home for that workload. The 90 to 180 days before a major renewal is the correct moment to run the comparison, not after signing another multi-year term out of inertia.
For SaaS companies selling into India's regulated sectors, this signal often arrives before the cost signals do. SEBI's Framework for Adoption of Cloud Services requires regulated entities to confirm data residency, retain their own encryption keys, and monitor deployments through a security operations centre before onboarding a vendor. A SaaS company hosted on standard multi-tenant AWS infrastructure, without having designed for these requirements from the start, typically cannot answer these questions satisfactorily without a genuine re-architecture, not just a policy document.
The same pattern applies to the Digital Personal Data Protection Act and its 2025 Rules: they do not mandate blanket localisation, but the moment a SaaS company's roadmap includes government, BFSI, or other regulated Indian customers, jurisdiction and key control stop being abstract questions and start being items on a security questionnaire.
Flexera's 2026 State of the Cloud Report puts average wasted public cloud spend at 29 percent industry-wide, the first increase in five years. If a cost review turns up idle instances, overprovisioned databases, or orphaned storage that nobody can attribute to a specific, justified need, that is not a one-off cleanup problem. It is evidence that the workload's actual shape no longer matches a metered pricing model built to charge for flexibility a steady-state product is not using.
None of this is an argument to abandon cloud entirely, and it would be dishonest to present it that way. Most companies that repatriate keep genuinely bursty, experimental, or geographically distributed workloads on public cloud, and move only the steady-state core, the parts of the product that have stopped changing shape month to month, to infrastructure priced on commitment rather than consumption. A hybrid outcome is the common one, not the exception.
It is also worth being direct about timing in the other direction: a company still searching for product-market fit should not be reading this as a reason to leave AWS early. The elasticity that feels expensive at scale is exactly what is worth paying for when demand is still a guess.
Before committing to either direction, a SaaS company should be able to answer these honestly:
Two or fewer of these, and the current setup is probably still the right one. Three or more, and it is worth running the actual comparison rather than assuming the answer.
Is there a specific ARR or team size where companies should leave AWS?
No single number applies universally. The reliable indicators are behavioural: growth flattening into a predictable line, infrastructure cost outpacing revenue, and a Reserved Instance or Savings Plan renewal approaching, not a fixed revenue threshold.
How long does moving off AWS typically take?
Documented cases, such as 37signals' migration, ran over 12 to 18 months for a full transition, often phased by workload rather than done as a single cutover, with the least critical or most distributed pieces moved last.
Should an early-stage SaaS startup ever consider leaving AWS?
Generally no. The elasticity AWS offers is most valuable precisely when demand is unpredictable, which describes most early-stage startups. This decision applies to companies whose growth has become steady enough to forecast.
What is the single clearest signal that it's time to evaluate a move?
An approaching Reserved Instance or Savings Plan renewal, because it creates a natural decision point without requiring a mid-contract disruption, and forces the comparison to happen deliberately rather than by default.
Do Indian regulatory requirements change this timeline?
Often, yes. SaaS companies selling into SEBI-regulated financial entities, or handling data covered by the DPDP Act's stricter obligations, frequently hit the compliance signal before they hit the cost signal, since a regulated customer's security questionnaire can surface jurisdiction and key-control gaps well before a finance review would.
Disclaimer
ZeaCloud Services Private Limited operates ZeaStack, a managed sovereign private cloud platform from Tier III data centres in India, built for companies whose workloads have outgrown metered public cloud pricing. This article is part of ZeaCloud's ongoing coverage of cloud economics and FinOps.