> For the complete documentation index, see [llms.txt](https://django-cloud.gitbook.io/django-cloud-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://django-cloud.gitbook.io/django-cloud-docs/reference/limitations.md).

# Known limitations

What to know before you build on DjangoCloud. We list these plainly so you aren't surprised later.

## The container is ephemeral

Files written to disk are lost on every restart and deploy. Use a managed database and object storage. See [Persistent files and the ephemeral container](/django-cloud-docs/how-it-works/ephemeral-container.md).

## How your app is served

Your app is started with **uvicorn** when it has an ASGI app (`asgi_module`), and with gunicorn when it only has a WSGI app. Both use the `workers` from your [build settings](/django-cloud-docs/how-it-works/build-settings.md). Websockets work with uvicorn. Each deployment is a single small container, so the number of concurrent connections is limited by its size, and a restart or deploy closes open connections. You can replace the command with `start_command`, but that is your own responsibility to test.

## Build and source limits

* The source upload is limited to **100 MB**.
* A build that runs for around 9 to 10 minutes is stopped. Keep images lean, and avoid compiling large dependencies from source during the build.
* Python 3.10 to 3.13 are supported, with pip or uv.
* Only a folder with `manage.py` is deployed. If your project lives in a subfolder, set `root` in the build settings.

## The first build in a brand-new AWS account can take hours

A new AWS account starts with no build capacity. DjangoCloud asks AWS to enable it automatically, and the deployment page says so while it waits. This happens once per account.

## Rollbacks restore code, not data

A rollback does not reverse database migrations. DjangoCloud blocks a rollback that would run old code against a newer schema unless you confirm it. See [Releases and rollbacks](/django-cloud-docs/how-it-works/releases-and-rollbacks.md).

## What we keep, and for how long

|                                                                  | Your own AWS account | Company | Enterprise |
| ---------------------------------------------------------------- | -------------------- | ------- | ---------- |
| Releases you can roll back to (their images and uploaded source) | 3                    | 3       | 10         |
| Logs                                                             | 3 days               | 7 days  | 30 days    |

CPU and memory graphs keep 30 days. Older images and uploads are deleted automatically after a new release goes live, and a release whose image was deleted can't be rolled back to. The live release is never deleted.

When you **delete a deployment**, its server and images are deleted from AWS too. A database is deleted after we save a final snapshot of it in your AWS account, so you can still restore it.

## Environment variables

* Up to 200 per deployment.
* Changes apply on the next deploy, not to the running release.

## Regions

You can deploy to the [regions listed here](/django-cloud-docs/reference/regions.md), where Lightsail container services exist. A deployment stays in the region it was created in.

## Metrics and logs

Logs and metrics are collected every few minutes, so the newest lines can be a little behind.

## Starter plan: you run your own cloud

On Starter, your app runs in your AWS account. You pay AWS directly, you set up your own domain and certificate, and AWS limits and quotas on your account apply. Hosted Company and Enterprise plans are coming soon.

## Early access

DjangoCloud is early. Some things, such as custom domains, are new and may need a retry or a word in Slack. The [Slack community](/django-cloud-docs/community-and-support/support.md) is the best place to ask what's ready.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://django-cloud.gitbook.io/django-cloud-docs/reference/limitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.