What is the best way to host a small web app cheaply?
Options for low-cost hosting
If your app is mostly static (HTML, CSS, JS) with some dynamic features, static hosting plus serverless functions can be very cheap or free. Providers like Netlify, Vercel, and Cloudflare Pages offer generous free tiers and pay-as-you-go pricing for functions. For apps needing a persistent server, a low-end VPS from providers like DigitalOcean, Linode, or Hetzner costs around $5–$10/month.
Platform-as-a-Service (PaaS) options like Render, Railway, and Fly.io offer free or low-cost tiers for small apps, but they may sleep after inactivity or have resource limits. Shared hosting is another option for traditional stacks (PHP, MySQL), often $2–$5/month, but can be restrictive.
- Static + serverless: free tiers available, scales automatically
- VPS: $5–$10/month, full control, requires server management
- PaaS: free or $5–$15/month, easy deployment, limited resources
- Shared hosting: $2–$5/month, good for PHP/MySQL, less flexible
How to decide
Start by estimating your traffic and resource needs. If you expect low traffic and can tolerate cold starts, serverless or a free PaaS tier may suffice. If you need a database, check whether the host includes one or if you need a separate service like Supabase or PlanetScale, which have free tiers.
Consider your technical comfort: managing a VPS requires sysadmin skills, while PaaS and serverless abstract that away. Also factor in scalability: serverless scales automatically, but costs can spike with high traffic; a VPS has fixed costs but limited resources. For a small app, a $5 VPS with a reverse proxy and a lightweight database often provides the best balance of cost and control.
- Estimate monthly visitors and peak concurrency
- Check if database is included or extra
- Consider cold start tolerance for serverless
- Evaluate management overhead vs. cost savings
- Look for free tiers with no credit card required
Common mistakes
- Assuming free tiers are always sufficient; they often have limits on bandwidth, build minutes, or database size.
- Forgetting about egress fees; some providers charge for outbound data transfer.
- Choosing the cheapest option without considering scalability; migrating later can be costly.

Related questions
- How do I choose between Docker and a virtual machine for deployment?
- Is Kubernetes overkill for a small team?
- Should I use a PaaS like Heroku or manage my own server?
- Why do I need CI/CD for a solo project?
- Can I deploy a full-stack app without using Docker?
- Should I use Vercel or Netlify for hosting my frontend?