Run Python web apps the standard production way: NGINX in front, Gunicorn or Uvicorn running your code under systemd, and PostgreSQL or MySQL behind. We install the stack on a hardened KVM VPS; you deploy with Git and pip.
Any Python version, system libraries and build tools.
Reserved vCores and RAM
Guaranteed resources for workers and background tasks.
NVMe storage
Fast virtualenv installs and database I/O.
Daily backups
Automatic backup of the previous 24 hours.
Why a VPS
Why Host Python Apps on a VPS
Python apps usually need more than a web process: background workers, scheduled jobs, system libraries and a real database. A VPS runs all of them.
01
Background tasks next to the app
Run Celery, RQ or Dramatiq workers, and a scheduler such as Celery beat, as systemd services beside your web app.
02
System libraries you control
Install what packages such as Pillow, psycopg, lxml or scientific libraries need to build, without platform restrictions.
03
The Python version you target
Install the version your project needs alongside the system Python, with a virtual environment per app.
04
ASGI and WebSockets
Run FastAPI or Django Channels under Uvicorn with long-lived connections, proxied by NGINX.
The stack
How a Python Web App Is Served
NGINX takes HTTP, an application server runs your code, and systemd keeps everything running.
Request from a browser or app (HTTPS)
Reverse proxy
NGINX
Terminates HTTPS, serves static and media files and proxies requests to the app server over a socket.
App server
Gunicorn (WSGI) or Uvicorn (ASGI)
Runs Django, Flask or FastAPI with several worker processes, managed by systemd.
Application
Your code in a virtualenv
Dependencies isolated per app; settings in environment variables.
Background
Celery or RQ + Redis
Workers for email, reports and long tasks, with Redis as the broker.
Database
PostgreSQL or MySQL
Listening on localhost, with a user for your app.
Worth knowing
Django: run collectstatic and let NGINX serve STATIC_ROOT; never DEBUG = True in production.
The Flask development server is not for production; Flask apps run under Gunicorn.
FastAPI is ASGI: use Uvicorn, or Gunicorn with Uvicorn workers.
A common starting point is (2 × vCores) + 1 Gunicorn workers.
What you can run
What You Can Run
Django sites and SaaS
Content sites, dashboards and SaaS products, with the Django admin.
FastAPI and Flask APIs
REST and async APIs for web and mobile front ends.
Data and model APIs
scikit-learn or small models served on CPU behind an API.
Scrapers and scheduled jobs
Scrapy spiders and scripts run by cron or systemd timers.
Bots and automations
Telegram and Discord bots and integrations that run all day.
Wagtail and django CMS
Content management on Django for marketing and documentation sites.
Shared hosting vs VPS
Outgrown shared hosting? A VPS has no shared limits.
Shared hosting is a good place to start. When a busy site keeps hitting its account limits, a VPS removes them.
On shared hosting
CPU, memory and processes are capped per account, so traffic spikes hit the ceiling.
You share the server with other sites.
No root access, and only the software the host supports.
Background workers, queues and WebSockets are limited.
On your own VPS
CPU, RAM and NVMe storage are dedicated to your server, not shared with neighbours.
Your plan's resources are yours, with no per-account caps to hit.
Full root and SSH access: install any software you need.
Run workers, cron jobs, queues and WebSockets freely.
A VPS is unmanaged: we install and secure it for you, then you run it. Prefer us to run everything? See managed hosting.
VPS Plans
VPS Plans for Python Apps
VPS-1 runs a Django or FastAPI app with PostgreSQL. Add Celery workers and VPS-2 gives more headroom; data-heavy jobs benefit from the 12 GB RAM of VPS-3.
VPS-1
Small websites, APIs, bots and development servers.
* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.
Prices exclude 18% GST, which is added to invoices for customers in India.
Sizing guide
Which Plan for Your Python App
Every Gunicorn worker loads your app into memory. Add Celery workers and the database, then size from there.
Recommended VPS plan for each Python workload
Workload
Start with
Why
Small Django or FastAPI app
VPS-12 vCores · 4 GB RAM
A few Gunicorn workers with PostgreSQL.
Production app with Celery
VPS-24 vCores · 8 GB RAM
Room for web workers, task workers and Redis.
Data-heavy jobs or model inference
VPS-36 vCores · 12 GB RAM
12 GB RAM for dataframes, models and caches.
Several apps or large datasets
VPS-48 vCores · 24 GB RAM
24 GB RAM and 8 vCores.
A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.
Python on a PaaS or on a VPS?
A platform builds and runs your app for you; a VPS runs the same app with no per-process billing.
Example shell commands; adjust paths, names and versions to your project.
Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).
Free one-time setup
Installed and Secured Before You Log In
The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers
do the first setup once, free, so you start from a hardened server with Python in place.
1
Choose a plan and location
Pick the resources you need and the datacentre closest to your users.
2
Tell us your Python setup
Versions, database and domain: at order or right after.
3
We install and secure it
Server hardened, Python installed and tested, HTTPS on your domain.
4
You take over with root
SSH access to a working server, ready for your code and data.
Your Python stack
Python 3 with venv and pip, or the version you specify
Gunicorn or Uvicorn as a systemd service
NGINX reverse proxy serving static files
PostgreSQL or MySQL with a database and user for your app
Redis for caching or as a Celery broker, on request
Yours to run after handover
Ongoing server administration
Application maintenance and updates
Debugging your code
Migrating existing sites or data
Not included in the free setup, but we can quote for it.
No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost;
cPanel and Plesk need their own licence.
Under the hood
Platform Specs and Locations
The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.
VPS platform specifications
Virtualisation
KVM with reserved vCores and RAM
Storage
NVMe SSD on every plan
Network
Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan
Operating systems
Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD
Access
Full root over SSH, key-based login
Backups
Automatic daily backup of the previous 24 hours; snapshots and longer retention on request
Protection
Always-on anti-DDoS mitigation
Availability
99.9% uptime SLA
Secured before we hand it over
Non-root sudo user created for daily work
SSH key login, password login for root disabled
Firewall (UFW) open only for the ports you use
Fail2ban blocking repeated login attempts
Automatic security updates enabled
Free Let's Encrypt SSL on your domain
Timezone, swap and hostname configured
Asia-Pacific
Mumbai
Singapore
Sydney
Europe
London
Limburg
Roubaix
Gravelines
Strasbourg
Milan
Warsaw
North America
Beauharnois
Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.
Who it's for
Who a Python VPS Suits
Django and FastAPI developers
You deploy over SSH or from CI and want a standard, understandable server.
Data teams shipping an API
You need to put a model or data service online behind HTTPS.
Projects outgrowing PaaS limits
Worker hours, sleeping apps or build limits on platforms are getting in the way.
Running it well
Security and Performance for Python Apps
Security
Keep DEBUG off in production and SECRET_KEY out of the repository.
Set ALLOWED_HOSTS in Django (or validate the Host header) and serve only over HTTPS.
Pin dependencies and check them with pip-audit.
Run the app as its own user, with only its media directory writable.
Performance
Start with (2 × vCores) + 1 Gunicorn workers and adjust by memory use.
Serve static and media files from NGINX, not from Python.
Cache expensive views and queries in Redis.
Move slow work to Celery so requests return quickly.
Python VPS FAQs
Questions Before You Deploy
Not covered here? Ask an engineer before you order.
Yes, any of them. Django and Flask run under Gunicorn; FastAPI and other ASGI apps run under Uvicorn. NGINX sits in front for HTTPS and static files, and systemd keeps the app server running.
Your operating system's Python 3 by default, for example Python 3.12 on Ubuntu 24.04. Tell us at order if your project needs another version and we install it alongside.
The free one-time setup installs Python, the app server, NGINX, your database and SSL on a hardened server. Deploying your code, running migrations and maintaining the app are yours to do, or can be quoted.
Yes. Celery workers and beat run as systemd services with Redis as the broker. Cron and systemd timers work for simpler scheduled scripts.
Django supports both. PostgreSQL is the common choice in the Django community and supports more of the ORM's database-specific features; MySQL and MariaDB work well too. We install the one you choose.
Yes, on CPU. The VPS plans have no GPU, so they suit inference with small or medium models and classical machine learning, not training large models.