01
Production settings
Disable debug behavior, set allowed hosts, protect the secret key, configure HTTPS and cookies, and run Django’s deployment checks.
Unmanaged Django hosting
Django hosting on an unmanaged VPS
Use an unmanaged KVM VPS when you want control over WSGI or ASGI serving, static files, the database, workers, production settings, and the deployment sequence.
Bitfoo opens for orders soon.
- Platform
- Unmanaged VPS
- Serving
- WSGI or ASGI
- Static files
- Collected
- Checks
- check --deploy
Linux administration required
Production server required
Served outside development mode
Run against production settings
Choose by responsibility
Choose VPS for a deliberate Django production stack
A VPS provides the control needed for Django’s application server, database, cache, workers, and optional real-time services, but it does not configure them for you.
Own the Django stack
Choose a Bitfoo VPS
Operate the framework, serving layer, data services, and Linux host directly.
- Custom Python and system dependencies
- Celery, Redis, Channels, or other persistent services
- The team owns deployments and server operations
Reduce infrastructure work
Consider a managed Django platform
Use a platform-managed runtime when host access is less important than operational simplicity.
- Builds, process types, and deploys should be managed
- No one owns Linux security and database recovery
- Automatic application scaling is a core requirement
Production foundation
Move every development convenience into production deliberately
Django’s deployment checklist is useful because production changes how settings, serving, files, errors, and security are handled.
02
WSGI or ASGI serving
Use a production-ready server and choose ASGI when persistent connections or asynchronous behavior require it.
03
Static and media files
Collect static assets for the public web layer and treat user-uploaded media as persistent data with its own backup plan.
04
Migrations and workers
Coordinate schema changes with releases and restart long-lived Celery, Channels, or other worker processes safely.
Plan comparison
Size Django, data services, and workers together
Include the application server, database, Redis or cache, Celery or Channels workers, deployment tasks, and operating system in the memory and CPU decision.
Swipe horizontally to compare every plan.
| Specification | VPS-1 Development, staging, or a light Django site | VPS-2 A production Django application Recommended starting point | VPS-4 More workers, Channels, or a local database | VPS-8 Higher-traffic APIs or multi-service Django stacks |
|---|---|---|---|---|
| vCPU | 1 | 2 | 4 | 6 |
| RAM | 1GB DDR5 | 2GB DDR5 | 4GB DDR5 | 8GB DDR5 |
| Storage | 25GB NVMe | 50GB NVMe | 100GB NVMe | 200GB NVMe |
| Bandwidth | 1TB | 2TB | 4TB | 6TB |
| IPv4 | 1 | 1 | 1 | 1 |
| Price | Coming soon | Coming soon | Coming soon | Coming soon |
| Availability | Join waitlist → | Join waitlist → | Join waitlist → | Join waitlist → |
Exact prices will appear when ordering opens. VPS plans are unmanaged and do not include an automated backup service.
Before deployment
Run Django’s production checklist as part of release
Treat framework checks, infrastructure configuration, and data migration as one deployment system.
- 01
Create production settings
Separate secrets, hosts, HTTPS, cookies, email, logging, database, and cache configuration from development defaults.
- 02
Collect and serve files
Move static assets to the configured production path and decide how user media is persisted and backed up.
- 03
Coordinate migrations
Design backward-compatible schema changes when old and new application versions may overlap.
- 04
Check, observe, and restore
Run deployment checks, monitor errors and worker health, and test database and media recovery.
Related hosting guidance
Common questions
Should I use WSGI or ASGI?
Use the serving interface required by the application. Standard synchronous deployments commonly use WSGI; persistent connections and asynchronous features may require ASGI.
Does Django serve static files in production?
Django’s development server is not the production file-serving plan. Collect static assets and configure the public web layer or another storage service to serve them.
Can I run Celery, Redis, or Django Channels?
Yes. A VPS supports persistent services, but you must install, supervise, secure, monitor, size, and back them up appropriately.
Does Bitfoo configure Django?
No. The VPS is unmanaged. Your team is responsible for Django, the application server, proxy, database, workers, deployments, OS security, monitoring, and recovery.