An entrepreneur just published the maths on running multiple five-figure monthly revenue businesses on infrastructure costs that wouldn't cover a Netflix subscription.
The breakdown is specific. Real numbers. Real products. £20 in monthly server costs supporting businesses generating £10,000 in monthly recurring revenue each.
This isn't a theory. It's a working model. And it challenges every assumption about what infrastructure "should" cost.
What the Stack Actually Looks Like
The entire technical foundation runs on a single virtual private server. Not a managed platform. Not serverless architecture. Not a cloud provider charging by the millisecond. One VPS. £20 a month.
The products handle real traffic. Real users. Real payments. But the architecture is deliberately simple. Static file serving. Minimal databases. No microservices. No container orchestration. No deployment pipelines that need their own infrastructure.
The businesses run on boring technology. The kind of stack a developer could build in an afternoon and maintain in an hour a month. Not because cutting-edge tech doesn't work - because it's unnecessary.
Why This Matters for Business Owners
The conventional wisdom in tech is that scaling requires spending. More users means bigger servers. More features means more infrastructure. Growth equals increased costs.
This model proves the opposite. You can build profitably from day one if you're willing to stay simple. The limitation isn't technical capability. It's discipline.
Most businesses overspend on infrastructure before they have revenue. They adopt complex architectures designed for problems they don't have yet. They pay for managed services to handle scale they haven't reached.
The result is businesses burning cash on operational costs before they've proven the model works. By the time they hit meaningful revenue, the infrastructure bill is already eating margins.
This approach flips it. Start with the simplest possible stack. Prove the business works. Scale infrastructure only when actual traffic - not projected traffic - demands it.
The Trade-Offs Nobody Mentions
Running lean infrastructure isn't free. The cost is time and technical skill. You're trading money for expertise. If you know how to configure a server, optimise databases, and debug production issues at 2am, you can run cheap. If you don't, managed services exist for a reason.
The other trade-off is redundancy. A single VPS is a single point of failure. If it goes down, everything goes down. For a £10K MRR business, that's acceptable risk. For a £100K MRR business, maybe not.
But here's what the conventional advice gets wrong. You don't need enterprise-grade infrastructure on day one. You need something that works. The gap between "works" and "enterprise-grade" is where most founders waste money.
What Builders Can Learn
The technical lesson is straightforward. Most web applications don't need complex architectures. A well-configured server, a competent developer, and disciplined feature scope can handle more traffic than you think.
The business lesson is more interesting. Revenue doesn't require spending. You can build profitably if you're willing to stay disciplined. The pressure to adopt expensive infrastructure comes from comparison, not necessity.
Every founder sees competitors raising funding, hiring teams, building complex systems. The assumption is that's what success looks like. But profitable businesses running on minimal infrastructure don't make headlines. They just quietly print money.
The Infrastructure Spending Trap
The trap most builders fall into is premature optimisation. They design for scale before they have users. They build redundancy before they have revenue. They adopt tools designed for enterprises when they're still validating product-market fit.
This model demonstrates the opposite approach. Build the simplest thing that could work. Ship it. Charge for it. If it generates revenue, you've proven the concept. Then - and only then - consider whether you need more infrastructure.
The cultural pressure in tech is to build impressive systems. Nobody brags about running on a single VPS. But impressive systems cost money. Simple systems make money.
What This Means Practically
For developers building side projects or launching products, this is the permission structure you need. You don't need Kubernetes. You don't need serverless functions. You don't need a managed database cluster.
You need a server, a domain, and the discipline to keep things simple. If you can write code, you can run infrastructure. If you can run infrastructure, you can keep costs below revenue.
The businesses in this example aren't small hobby projects. They're generating five figures monthly. Real products. Real customers. Real revenue. All running on infrastructure costs that round to zero in the P&L.
That's not a hack. It's a choice. The choice to prioritise profitability over complexity. To build for revenue, not for resumes. To ship products that work instead of architectures that impress.
The tech industry romanticises scale. But scale isn't the goal. Profit is. And profit comes from revenue exceeding costs. The simplest way to achieve that is keeping costs low while building things people will pay for.
This model proves it's possible. Not theoretical. Not aspirational. Actually possible. Right now. With technology that's been stable for a decade.
The question isn't whether you can build profitably on minimal infrastructure. It's whether you're willing to resist the pressure to do otherwise.