Hosting for Django: what 17 makers' products chose
Among 17 makers' products built with Django that we know the hosting of, DigitalOcean leads: 8 of them (47%). Next come Heroku (6) and Vercel (5).
What shape is your app? A frontend or serverless app fits a frontend cloud. Long-running servers, background workers and databases fit a PaaS or container platform. A hyperscaler cloud has every building block but leaves you to assemble them; a platform or framework that deploys into your own cloud account sits between, with platform-style deploys and the resources on your own cloud bill.
What makers on Django chose
| Option | Django products | All makers | Free for | Team of 5, 10,000 users |
|---|---|---|---|---|
| 8 (47%) | 4% | — | — | |
| 6 (35%) | 1% | — | — | |
| 5 (29%) | 57% | None | $120/moPro + Flat Rate CDN 10M | |
| 4 (24%) | 13% | None | $17/moPay as you go (Lambda + EC2 t4g.small) | |
| 2 (12%) | 11% | ~830 users | $12/moWorkers Paid | |
| 1 (6%) | 3% | None | $13/moCPX12 |
Live makers' products with a source for both: that they're built with Django, and what they use for hosting. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Vercel 5 here - Your app is a static site or docs and should cost nothing to host
Cloudflare 2 here - You want a flat monthly bill and full control, and don't mind running one server
Hetzner Cloud 1 here
DigitalOcean
PaaS8 Django products here (47%).
llms.txtBest forApp Platform deploys from git next to DigitalOcean's managed databases, storage and droplets.
Trade-offFewer built-in extras than Vercel or Railway, and instances are billed per size, not per request.
“We chose DigitalOcean for its cost-effective, scalable cloud infrastructure, providing a flexible and manageable environment to host our app.”
Status page: 16 incidents in the last 90 days, 2 major (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so +1 · source ↗“We chose DigitalOcean for its cost-effective, scalable cloud infrastructure, providing a flexible and manageable environment to host our app.”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗
Heroku
PaaS6 Django products here (35%).
llms.txtCLIBest forA long-established git-push platform with managed Postgres, Redis and a large add-on marketplace.
Trade-offNo free tier, and since March 2026 Heroku runs as a sustaining-engineering platform focused on stability rather than new features.
“Listed in their tool stack on Starter Story (platform)”
“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so +1 · source ↗“The easiest way is probably going for a managed hosting solution like Heroku .”
HostingMaker says so · source ↗
Vercel
Frontend cloud5 Django products here (29%). About $120 a month for a team of 5 with 10,000 users (Pro + Flat Rate CDN 10M).
llms.txtMCPCLIIn v0Best forNext.js apps — zero-config deploys and preview URLs.
Trade-offThe Hobby plan is non-commercial; costs grow with usage.
“Listed in their tool stack on Starter Story (platform)”
- Pushing to Git deploys automatically with zero configuration. 4 sources
- Every commit or pull request gets a preview URL, so changes are reviewed live before release. 4 sources
- Heavy bot traffic, such as Meta's crawler, can multiply the bill with little protection. 3 sources
- Execution limits and middleware quirks need workarounds. 1 source
Can I run a Python, Go or Docker backend on Vercel, not just JavaScript? Yes. Official function runtimes cover Node.js, Bun, Python (ASGI/WSGI apps such as FastAPI, Flask and Django), Go, Ruby, Rust and Wasm, and container images pushed to Vercel's registry can run as functions (in beta). Vercel docs ↗
Status page: 21 incidents in the last 90 days, 12 major (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so +1 · source ↗
Amazon Web Services
Hyperscaler cloud4 Django products here (24%). About $17 a month for a team of 5 with 10,000 users (Pay as you go (Lambda + EC2 t4g.small)).
Best forThe widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure.
Trade-offYou wire up networking, permissions and deploys yourself; billing is per service and hard to predict.
“The platforms we rely on the most are AWS and HubSpot .”
- It offers a huge catalog of services in one place, from databases to queues to AI. 4 sources
- It scales up and down with bursty traffic without re-architecting. 3 sources
- Major outages, from long us-east incidents to struck data centers, have taken customer services down. 4 sources
- Its services can be tricky to configure. 1 source
“The platforms we rely on the most are AWS and HubSpot .”
HostingMaker says so +1 · source ↗“There are however services you need to pay for like domain registration ( Godaddy ) and the Ubuntu linux server on AWS (Amazon Web Services).”
HostingMaker says so · source ↗“The loadbalancing goes hand-in-hand with our ECS usage, and ACM makes provisioning all of our certificates and serving them pretty trivial. I’d maybe have gone full AWS if Terraform/IaC wasn’t a thing, but hooking the CloudFlare & AWS providers up is easy as heck.”
HostingMaker says so · source ↗All of Amazon Web Services: who uses it, alternatives, pricing →
Cloudflare
Edge platform2 Django products here (12%). Free up to about 830 users. About $12 a month for a team of 5 with 10,000 users (Workers Paid).
llms.txtMCPBest forCheap global hosting with Workers, plus database (D1) and storage (R2) on the same platform.
Trade-offThe Workers runtime isn't full Node.js; some libraries need adapting.
“Cheap/free and rather powerful DNS/routing tools. Ubiquotous CDN. If Cloudflare goes down, so does the rest of the internet. Antiquoted is the least of your worries.”
- Workers, D1, R2, Durable Objects and more combine as bindings on one platform instead of separate vendors. 4 sources
- The free tier bundles DNS, CDN, TLS and abuse protection in one dashboard. 2 sources
- Bot checks and default AI-crawler blocking get in the way of legitimate users and automation. 4 sources
- The dashboard is slow and buggy, with login and passkey problems. 2 sources
Status page: 48+ incidents in the last 90 days, 5 major (its own page, 2026-10-19).
“Cheap/free and rather powerful DNS/routing tools. Ubiquotous CDN. If Cloudflare goes down, so does the rest of the internet. Antiquoted is the least of your worries.”
HostingMaker says so · source ↗Also chosen, and not seen yet
Fewer Django products here: Hetzner Cloud (1).
Real options for hosting not seen among these Django products yet: Netlify, Railway, Render, Fly.io, Coolify.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Django.
- Vercel → Cloudflare 242 pull requests · how they moved
- Cloudflare → Vercel 83 pull requests · how they moved
- Amazon Web Services → Cloudflare 39+ pull requests · how they moved
- Vercel → Amazon Web Services 38 pull requests · how they moved
- Amazon Web Services → Vercel 15 pull requests
- Vercel → Hetzner Cloud 11 pull requests
Getting hosting right
Connect the repo so every push deploys and every pull request gets a preview URL. Put secrets in the platform's environment variables, never in the repo.
- Leaving a paid platform on its default autoscaling and spend limits, so one viral day or a bot crawl turns into a surprise invoice.
- Putting a long-running job, websocket or large upload behind a serverless function and hitting its time or size limit in production.
- Keeping the database on a different provider or region from the app, so every query crosses the internet and pages get slow.
The rest of the Django stack
What makers' Django products chose for their other decisions, the most common pick for each:
- Transactional Email: SendGrid 7 of 14
- Payments: Stripe 12 of 13
- Web Analytics: Google Analytics 10 of 12
Questions
What do most Django apps use for hosting?
Among 17 makers' products built with Django that we know the hosting of, DigitalOcean leads: 8 of them (47%). Next come Heroku (6) and Vercel (5).
What does hosting cost for a Django app with 10,000 users?
On our usage model for a team of 5 with 10,000 users, Vercel comes to about $120 a month (Pro + Flat Rate CDN 10M); Amazon Web Services comes to about $17 a month (Pay as you go (Lambda + EC2 t4g.small)); Cloudflare comes to about $12 a month (Workers Paid); Hetzner Cloud comes to about $13 a month (CPX12). Prices are from each vendor's pricing page.
Which hosting option stays free longest for a Django app?
Cloudflare: on our usage model its cheapest plan stays free up to about 830 users.
How this is counted: a product is on Django when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its hosting. How evidence is collected.