Frameworks/Deploy Django on your own server
Django

Deploy Django on your own server

Push a Django project and Railpack builds it, runs your migrations and serves it with Gunicorn, on a server you own.

From repo to live in three steps

  1. 01Connect the repository that holds your Django app.
  2. 02Railpack recognises the Django project and builds it into an image.
  3. 03Push to the branch: every push builds and rolls out a new version.

What Deplo sets up

  • Recognised from manage.py and Django among the dependencies.
  • Dependencies installed with pip, Poetry, PDM, uv or Pipenv, whichever the repository uses.
  • python manage.py migrate runs before Gunicorn starts the app.
  • HTTPS through Traefik as soon as the domain points at the server.

Deplo builds with Railpack by default, so a Django project needs no Dockerfile to get started.

Django on Deplo

Short answers to what comes up before moving a Django app onto your own server.

From the WSGI_APPLICATION setting, or from the RAILPACK_DJANGO_APP_NAME variable when you set it.

Yes. Managed databases live in the same environment and reach the app over the internal network.

In the app's settings, per environment. They are available during the build too, and secret values are write only: nothing reads them back.

Ten minutes from now,
it's live.

Answer three questions and pick a host, or install Deplo on a server you already have. It's free, and leaving is as easy as arriving. What you do with the money you save is your business.