Best VPS for Python & Django in 2026
Updated Aug 2026 · 8 plans benchmarked
A Django app wants steady single-core performance, RAM for Gunicorn workers plus Postgres, and a region near your users. These plans run a production Django + Postgres stack comfortably on the entry tier.
- RAM for several Gunicorn/uvicorn workers plus the database and cache.
- Consistent CPU for request handling; steady clock beats bursty shared cores.
- Fast NVMe for the database, and headroom for a virtualenv and static files.
- A region near your users to keep request latency low.
The picks
4 GB RAM runs several Gunicorn workers plus Postgres and Redis on one box, and strong single-core performance keeps p95 latency low.
4 GB NVMe at a low price fits a Django app with Postgres alongside; included backups cover the database.
Scale workers by bumping RAM/CPU on demand, and deploy close to your users across the US, EU, or Asia.
One-click apps and excellent Django-on-Ubuntu docs shorten the first-deploy loop. Hetzner is the value pick once the stack is familiar.
The picks, side by side
Prices verified Aug 2026 · How we benchmark →
Common questions
How much RAM does a Django app need?
Each Gunicorn worker uses tens to a few hundred MB; with Postgres and Redis alongside, 2–4 GB comfortably runs a small-to-medium production app.
Can I run Django and Postgres on the same VPS?
Yes — at small scale it's the simplest, cheapest setup. Move Postgres to its own box once it competes with the app for memory.
How many Gunicorn workers should I run on a small VPS?
A common starting point is (2 × CPU cores) + 1, then tune down if memory is tight. On a 2-core box that's about 5 workers, adjusted to your RAM.