Getting started

Deploy your first Django app

Five steps from an existing project to a live HTTPS URL. This is the overview; the quickstart has the exact instructions.

The five steps

1. Create an account

Sign up and add a card. The subscription covers Django Cloud itself; on Self-hosted, AWS bills you separately for what you run.
2. Choose where it runs

On Self-hosted, create a role in your AWS account that trusts Django Cloud (one CloudFormation stack, with the policy shown in the docs) and paste its ARN into Settings, AWS account. No secret is stored. On Fully managed there is no AWS account to connect.
3. Install the CLI and sign in

The CLI shows a short code that you approve in the browser, so no password is typed in a terminal.
```
$ pip install djangocloud-cli
$ python manage.py djangocloud login
```
4. Deploy

On the first run the CLI asks which project this folder deploys to, shows the server size, and creates nothing until you confirm. Prefer GitHub? Connect a repository and push instead.
```
$ python manage.py djangocloud deploy
```
5. Check it and add your domain

Open the URL the CLI prints, read the logs if something looks off, set your environment variables, then add your own domain from the Domains tab.
```
$ python manage.py djangocloud status
$ python manage.py djangocloud logs
```

Python 3.10 to 3.13 and Django 4.2 or newer
An ASGI or WSGI application, such as config.asgi:application, which the CLI detects
Dependencies in requirements.txt, or in pyproject.toml and uv.lock
Postgres, and file storage for uploads, rather than SQLite and local files

You want to tweak and optimize your deployment fully
You already run Kubernetes or manage your own EC2 servers. You will want that control, and that is a good thing.
You need custom networking, GPUs or multi-region failover.
You need scheduled jobs today (Celery beat and cron are not available yet).

Create an account and deploy with one command.