> 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/how-it-works/billing.md).

# Billing and your account

## What you pay DjangoCloud

The plan fee, for example $0.99 a month for Starter, is charged by card through Stripe. You need a card on file to create deployments. Manage your card, invoices and subscription from **Settings → Billing** in the dashboard.

## What you pay AWS

On Starter your app runs in your own AWS account, so AWS bills you directly for the servers at AWS list prices. DjangoCloud doesn't see or charge for that. See [Pricing](/django-cloud-docs/reference/pricing.md) for the size prices.

## If a payment fails

Stripe retries a failed card for a while. If the subscription ends up **unpaid** or **canceled**, your account is **suspended**:

* New deploys are refused, including pushes from GitHub, and the deployment log says why.
* Your running apps are not stopped by DjangoCloud.
* Update your card in **Settings → Billing**. As soon as the subscription is active again the suspension lifts and you can deploy.

## Invoices

Manage your payment details and see your invoices from the billing portal linked in **Settings → Billing**.


---

# 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/how-it-works/billing.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.