01
WSGI or ASGI server
Choose the serving interface from the framework and workload, then configure workers from measured concurrency and memory use.
Unmanaged Python hosting
Python hosting on an unmanaged VPS
Use an unmanaged KVM VPS for Django, Flask, FastAPI, and workers when you want to choose the Python runtime, WSGI or ASGI server, proxy, database, and deployment workflow.
Bitfoo opens for orders soon.
- Platform
- Unmanaged VPS
- Serving
- WSGI or ASGI
- Environment
- Isolated
- Access
- Full root
Linux administration required
Chosen by the application
venv or another tool
Custom packages supported
Choose by responsibility
Choose VPS when the Python runtime is part of the product
A VPS supports custom libraries, native packages, persistent APIs, background work, and framework-specific deployment patterns—with the corresponding operational responsibility.
Custom runtime
Choose a Bitfoo VPS
Operate the application server and supporting services directly.
- Native system dependencies or custom Python versions
- Persistent WSGI, ASGI, worker, or scheduler processes
- The team owns deployments and Linux operations
Managed runtime
Consider a Python application platform
Reduce server work when direct access to Linux is not required.
- Platform-managed builds and process types are preferred
- Automatic scaling matters more than host control
- No one is assigned to security and recovery
Production foundation
Separate the application from the public edge
Production Python applications typically run behind a proxy and under process supervision rather than exposing a development server directly.
02
Reverse proxy
Terminate TLS and handle public connection behavior at Nginx, Caddy, or another intentional proxy.
03
Dependency isolation
Pin Python and package dependencies in a repeatable environment and account for native libraries outside the package lock.
04
Background processes
Supervise workers and schedulers separately from the web process, with their own health and restart behavior.
Plan comparison
Size for workers and supporting services
Memory must cover web workers, background workers, the database and cache if local, deployments, and the operating system—not only one development process.
Swipe horizontally to compare every plan.
| Specification | VPS-1 Development, staging, or a light Python service | VPS-2 A small production web application Recommended starting point | VPS-4 More workers, a database, or several services | VPS-8 Higher-traffic or data-heavy Python 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
Turn the local command into a production service
Document how every runtime dependency and process is installed, started, observed, and restored.
- 01
Pin Python and packages
Record the Python version, dependency lock, native libraries, and build steps required to reproduce the environment.
- 02
Choose process types
Define web, worker, scheduler, database, and cache services independently.
- 03
Handle secrets and migrations
Keep configuration outside source control and make schema changes part of the controlled release sequence.
- 04
Test restart and restore
Prove that the application starts after reboot and that data can be recovered on a clean server.
Related hosting guidance
Common questions
Can I run Django, Flask, or FastAPI?
Yes. Full server control lets you install the framework and production WSGI or ASGI server appropriate for the application.
Can I use Celery or another worker system?
Yes. Run workers as supervised services and account for their broker, concurrency, memory, monitoring, and deployment restart behavior.
Does Bitfoo configure Python or Nginx?
No. The VPS is unmanaged. Your team installs, configures, secures, monitors, updates, and backs up the complete stack.
Which plan should I start with?
VPS-2 is the general production starting point shown here. Final sizing depends on worker count, per-process memory, local database or cache services, and traffic behavior.