The verdict in three sentences
Making a SaaS scalable costs between 15,000 and 60,000 EUR (excl. VAT) in 2026, depending on the levers activated (cache, queue, replicas, CDN). The trap isn't technical but temporal: scaling too early wastes budget on users who don't exist, scaling too late causes outages at the worst moment (traffic spike, fundraising). The 2026 golden rule: measure first, optimise the real bottleneck, never anticipate blindly.
Scalability levers and their cost
Each lever solves a specific bottleneck. Activate them in order of impact/cost ratio, not all at once.
| Lever | Bottleneck solved | Setup cost (EUR excl. VAT) | Monthly cost |
|---|---|---|---|
| Cache (Redis) | Slow repeated queries | 3,000 - 6,000 | 20 - 80 EUR |
| Queue (async jobs) | Blocking heavy tasks | 4,000 - 9,000 | 15 - 60 EUR |
| Database read replicas | Saturated reads | 5,000 - 12,000 | 80 - 300 EUR |
| CDN (assets, images) | Geographic latency | 2,000 - 4,000 | 10 - 100 EUR |
| Horizontal auto-scaling | Traffic spikes | 6,000 - 15,000 | Variable |
| Sharding / partitioning | Massive data volume | 15,000 - 40,000 | 200 - 800 EUR |
In 80% of cases, a simple Redis cache + a queue absorb the first growth wave for under 10,000 EUR. Database sharding is only justified beyond several hundred thousand active users.
When to invest: trigger thresholds
The right moment to activate a lever shows in the metrics, not in optimistic projections. Here are indicative 2026 thresholds.
| Measured signal | Alert threshold | Lever to activate |
|---|---|---|
| P95 response time | > 1 s | Cache + query optimisation |
| Database CPU | > 70% sustained | Read replicas |
| Job queue backlog | > 5 min | Dedicated queue |
| Out-of-region latency | > 300 ms | CDN |
| Server usage at peaks | > 80% | Auto-scaling |
| Main table size | > 50M rows | Partitioning |
Wait for the alert threshold, not the crash: between crossing the threshold and an outage, there are usually a few weeks to act calmly.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Thomas, CTO of an invoicing SaaS in Lyon, sees traffic triple after a partnership. P95 response time climbs to 1.8 s and the database runs at 85% CPU at peak. Over-engineering panic: a vendor proposes a microservices rebuild at 55,000 EUR (excl. VAT).
The measured calculation: the audit reveals 60% of the load comes from 3 uncached queries and reports generated synchronously. By activating a Redis cache (5,000 EUR) and a queue for reports (7,000 EUR) — i.e. 12,000 EUR (excl. VAT) — P95 drops to 400 ms and database CPU to 45%. Thomas avoids a 55,000 EUR rebuild, gains 12 to 18 months of scaling headroom, and postpones adding replicas until he genuinely needs them. Immediate ROI: 43,000 EUR not spent.
FAQ
Do you need microservices to scale? Rarely at first. A modular monolith with cache, queue and replicas carries a SaaS to several tens of thousands of users. Microservices solve a team-organisation problem as much as a load one.
How do you find the real bottleneck? Through observability: APM (traces), database metrics, latency logs. Without measurement, you optimise at random. Monitoring tooling costs 2,000-5,000 EUR to set up and pays off with the first prevented incident.
Can caching cause bugs? Yes, cache invalidation is a classic. You control it with short lifetimes on volatile data and explicit invalidation on critical data. Done well, caching is the best gain/cost ratio.
What does scaling too early cost? A premature microservices architecture can add 40,000-60,000 EUR of development and double infra costs, for users who never arrive. It's the most expensive mistake of technical startups.
Does auto-scaling handle everything? No. It absorbs web traffic spikes but solves neither a saturated database nor badly optimised queries. Activate it after handling cache and database, never before.
Let's scope your project. Send us your metrics (response time, database load, traffic peaks) and your growth horizon: we'll pinpoint the real bottleneck and quote the useful levers, without over-engineering. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.