> ## Documentation Index
> Fetch the complete documentation index at: https://antideploy.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Infrastructure Antideploy Provisions for You

> What Antideploy creates and manages on your behalf, and just as importantly, what it does not.

Antideploy analyzes your code and provisions what it can. The honest list is
short, and knowing where it ends is more useful than a long one.

## What is provisioned

| Component         | What you get                                                                                          |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| **Compute**       | A container built from your code, running on managed infrastructure. Scales to zero when idle.        |
| **PostgreSQL**    | A managed database, created automatically when your code uses Postgres, with `DATABASE_URL` injected. |
| **HTTPS**         | TLS termination and a generated URL for every app.                                                    |
| **Configuration** | Environment variables and secrets, encrypted at rest and injected at release.                         |

<CardGroup cols={2}>
  <Card title="Compute" icon="server" href="/docs/infrastructure/compute">
    Container sizing, scale-to-zero, and the single-instance limit.
  </Card>

  <Card title="Databases" icon="database" href="/docs/infrastructure/databases">
    When Postgres is provisioned and how it is connected.
  </Card>
</CardGroup>

## What is not provisioned

<Warning>
  These are detected but **not** created for you. If your project needs one, you
  supply it and pass credentials as environment variables.

  | Component                          | Status                                                                                                       |
  | ---------------------------------- | ------------------------------------------------------------------------------------------------------------ |
  | **Object storage**                 | Not provisioned. Files written to local disk are lost on restart or redeploy. Bring an S3-compatible bucket. |
  | **Redis / caching**                | Not provisioned. Supply `REDIS_URL`.                                                                         |
  | **Queues and background workers**  | Not run. A worker defined in your project will not start.                                                    |
  | **Cron / scheduled jobs**          | Not run. Nothing on a schedule will ever fire.                                                               |
  | **Custom domains**                 | Not available. Apps are served on a generated URL.                                                           |
  | **Staging / preview environments** | Not available. One deployed version per project.                                                             |
</Warning>

Antideploy raises these during analysis as warnings or hazards, so you learn
about them before deploying rather than after.

## Bringing your own

Anything Antideploy does not provision can still be used; it just has to
already exist. Set the credentials as environment variables and your app picks
them up at release.

If your code contains a Supabase, Firebase, or S3 client, analysis will notice
and tell you it is leaving that alone rather than trying to replace it.

<Card title="Environment variables" icon="key" href="/docs/configuration/environment-variables">
  How to supply credentials for services you bring yourself.
</Card>