Runtime and processes
Check Django deployments that need a Python environment, WSGI or ASGI process supervision, static/media handling, migrations, database connectivity, and background jobs.
Django application hosting
Run Django with your chosen Python environment, database and application server. A self-managed VPS gives you control over deployment and background tasks.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check Django deployments that need a Python environment, WSGI or ASGI process supervision, static/media handling, migrations, database connectivity, and background jobs.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
Django runs behind a WSGI or ASGI server such as Gunicorn or Uvicorn, and worker count is the main sizing decision. A common starting formula is two times the CPU cores plus one for sync workers, then adjust using measured request times, since each sync worker handles one request at a time.
Serve static files from the web server or a dedicated static host after running collectstatic, and keep media uploads on disk space you monitor separately. The frequent bottleneck is database connections: each worker opens its own connections, so multiply workers by connections per worker and compare against the database limit.
Use sync workers for CPU bound views and an async worker class for long lived connections such as websockets. Mixing both workloads on sync workers blocks ordinary pages.
Run migrations once per release before the new code serves traffic. Two app servers migrating at the same time can lock tables and fail halfway.
Read SECRET_KEY, database credentials, and ALLOWED_HOSTS from environment variables. A missing host entry shows up as repeated 400 errors in the logs.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.