Most software builds include hosting as a footnote. The developer says "we'll deploy to AWS" or "we'll use Vercel" and the conversation moves on. Months later you're staring at a monthly invoice and wondering where the €300 suddenly came from.
The hosting decision made in week two of a project determines your running costs for the entire lifespan of the software. It also determines uptime, scaling headroom, and how much pain a failure causes. Here's what hosting actually costs in 2026, the difference between the main options, and the questions worth asking before your developer picks the infrastructure.
The three categories of hosting
Managed platforms — Vercel, Render, Railway, Heroku, Netlify. You push code, the platform handles the rest: deployment, scaling, SSL certificates, monitoring basics. Pricing is transparent and the operational burden is minimal. The right default for most business applications that don't need to run at unusual scale.
Cloud infrastructure — AWS, Azure, Google Cloud. More control, more configuration, a much higher ceiling — and a significantly higher floor of complexity. You pay for engineering time to set it up and ongoing attention to keep it running. Justified when your application genuinely needs the flexibility; overkill for most SMB business software.
Self-managed servers (VPS) — Hetzner, DigitalOcean, Contabo. Fixed monthly pricing, full control, no managed services. Cheapest per resource, but someone has to install updates, manage backups and respond to failures. Usually the domain of developers who prefer control over convenience.
What hosting actually costs
For a small application — internal tool, dashboard, portal for under 50 concurrent users — realistic monthly costs:
- Managed platform: €20–€100/month
- VPS: €10–€40/month
- Cloud infrastructure (AWS/Azure): €50–€150/month — often overkill for this size
For a medium application — customer portal, order management system, an API handling thousands of requests per day — the numbers shift:
- Managed platform: €100–€500/month
- Cloud infrastructure: €150–€600/month
- VPS cluster: €80–€250/month
For high-traffic or data-intensive applications, cloud infrastructure scales to €500–€3,000+ per month depending on volume. Most business applications never reach this range.
A project scoped at €40,000 to build can easily run €200–€400/month to host. That's €2,400–€4,800 per year, every year — and it belongs in the total cost calculation alongside the build, the maintenance retainer and any SaaS subscriptions the application connects to.
The hidden cost lines most estimates leave out
Database hosting. Almost every business application needs a database, and hosting it separately as a managed service adds €40–€200/month on top of the application server. Worth it for automated backups, point-in-time recovery and scaling without downtime — but it needs to be in the budget, not discovered on the first invoice.
Staging environment. Deploying changes to a test environment before they reach real users is a basic operational standard. A staging instance is typically 30–50% of the production cost. It often gets dropped from early estimates and added back when something breaks in production for the first time.
Monitoring and alerting. Something should tell you before your users do when the application stops responding. Basic uptime monitoring is often free; production-grade observability — error tracking, performance metrics, alerting — adds €20–€100/month via Sentry, Datadog, or similar. Not glamorous, but the difference between a 5-minute outage and a 3-hour one.
Bandwidth and egress. Cloud providers charge for data that leaves their network. Applications that generate large file exports, send attachments, or process images can see bandwidth costs that compound silently. Ask about this specifically if your application handles files.
EU hosting and GDPR
For Dutch and European businesses, where data is stored is a compliance question, not just a preference. Personal data about EU residents must in most cases be processed on EU-based infrastructure. AWS eu-west, Azure westeurope and Google Cloud europe-west all qualify — but you need to verify that your developer actually configured the project to run in an EU region, not the default US-east-1 that most tutorials assume.
Third-party services in the stack need the same check: email providers, monitoring tools, AI APIs. A well-built application that routes customer data through a US-based email provider without a proper processing agreement is still a GDPR exposure, regardless of where the main server runs. More on this in the context of security and GDPR essentials and the specific question of AI integrations and where data goes.
Questions to ask your developer before they pick the infrastructure
You don't need to evaluate the technical details yourself. These questions cover what matters:
- What's the monthly hosting cost at normal load, and what would a 10x traffic spike cost? The answer should be specific and not require weeks of testing to estimate.
- In which country or region are the servers? The answer should be an EU region, with a reason if it isn't.
- Who holds the hosting account credentials — us or you? The account should be in your company's name, with the developer added as a collaborator. This is the same principle as owning your own code repository and domain — when the relationship ends, you keep everything. The detail is covered properly in the post on avoiding vendor lock-in.
- Is there a staging environment, and what does it cost?
- What monitoring is in place, and who gets the alert when something breaks?
What good infrastructure looks like
A few signals that separate a properly set-up application from a fragile one:
- Automatic daily backups with a tested restore process. A backup you've never restored from is a backup you don't have.
- Secrets stored in environment variables, not in the codebase. API keys and database passwords in a Git repository are a security incident waiting to happen.
- Deployments that don't require a manual restart. If someone has to SSH into a server to update the application, that's manual overhead and a bottleneck.
- Separate production and staging environments. Everything that changes in production should be tested in staging first. No exceptions.
The upshot for your budget
When comparing quotes or planning a software project, add a hosting line explicitly. For most business applications, €100–€400/month is a realistic all-in range: application, database, staging, monitoring and backups. Over a five-year lifespan that's €6,000–€24,000 — significant money, and it belongs in the same conversation as the build cost when you're evaluating whether custom software is the right investment against a SaaS subscription.
The hosting choice doesn't change the build cost, but it changes the total cost of ownership substantially. A developer who defaults to over-provisioned cloud infrastructure because "that's what we use" is spending your ongoing budget without a business reason. Ask for the reasoning — the right answer is "this is the simplest option that fits your scale," not the most impressive-sounding one.
Thinking about the full cost picture for a custom software project? The custom software cost breakdown covers the build side, and what maintenance costs after launch covers the years that follow. If you want a realistic all-in number for your specific situation, get in touch.