# Antideploy

## Docs

- [Antideploy: Deploy Any App Without Configuring Infrastructure](https://antideploy.com/docs/introduction.md): Antideploy reads your code, works out what it needs to run, and deploys it: no Dockerfile, no YAML, no cloud console.
- [Get Your First App Live in 5 Minutes](https://antideploy.com/docs/quickstart.md): Connect a GitHub repo, upload a folder, or push over the API: Antideploy analyzes your code and deploys it.
- [How Antideploy Analyzes Your Code and Deploys It](https://antideploy.com/docs/how-it-works.md): What happens between handing Antideploy your project and getting a live URL: analysis, provisioning, build, and release.
- [Deploy from GitHub](https://antideploy.com/docs/deploying/github.md): Connect a repository and every push to its default branch redeploys automatically.
- [Deploy by Uploading a Folder](https://antideploy.com/docs/deploying/upload.md): Pick a folder in the dashboard and deploy it: no Git repository, no CLI, nothing to install.
- [Deploy from a Coding Agent](https://antideploy.com/docs/deploying/mcp.md): Give Claude Code, Cursor, or any MCP client the ability to deploy your project: no browser, no Dockerfile, nothing to configure.
- [Deploy from the CLI or an AI Agent](https://antideploy.com/docs/api/deploy.md): Push a project directory to Antideploy over the REST API and poll it to completion: the flow an AI coding agent uses when you tell it to ship.
- [Infrastructure Antideploy Provisions for You](https://antideploy.com/docs/infrastructure/overview.md): What Antideploy creates and manages on your behalf, and just as importantly, what it does not.
- [Managed Compute: Containers and Scale-to-Zero](https://antideploy.com/docs/infrastructure/compute.md): How Antideploy runs your app: container sizing, cold starts, and the single-instance limit.
- [Managed PostgreSQL: Provisioning and Connections](https://antideploy.com/docs/infrastructure/databases.md): Antideploy provisions PostgreSQL automatically when your code uses it, and injects the connection string as DATABASE_URL.
- [Health Checks and Downtime Email](https://antideploy.com/docs/operations/monitoring.md): Antideploy checks every deployed app every few minutes and emails you when one goes down or recovers.
- [Application Logs](https://antideploy.com/docs/operations/logs.md): Read what your running application printed to stdout and stderr, from the Logs tab in the dashboard.
- [Deployment History and Rollback](https://antideploy.com/docs/operations/deployments.md): Every release is recorded, and any previous one that produced an image can be restored without a rebuild.
- [Environment Variables](https://antideploy.com/docs/configuration/environment-variables.md): Set the values your app reads from its environment, from the dashboard or over the API. Every one is encrypted at rest and write-only.
- [Secrets and Credentials](https://antideploy.com/docs/configuration/secrets.md): How Antideploy stores credentials: one encrypted, write-only store shared with environment variables, and what that means for rotation.
- [Deploy Without a Dockerfile](https://antideploy.com/docs/guides/deploy-without-a-dockerfile.md): You do not need to write a Dockerfile to deploy a web application. Here is what replaces it, what you give up, and when you still want one.
- [Deploy an App With a Postgres Database](https://antideploy.com/docs/guides/deploy-an-app-with-a-database.md): Deploy an application and its Postgres database together, with DATABASE_URL injected and migrations run before the app starts rather than after it has crashed.
- [Why Did My Deployment Fail?](https://antideploy.com/docs/guides/why-did-my-deployment-fail.md): The failures that actually happen when you deploy a web app, what each one really means, and why the error you see is often not the thing that is wrong.
- [Roll Back a Bad Deploy](https://antideploy.com/docs/guides/roll-back-a-bad-deploy.md): Getting back to the version that worked, in about forty seconds, without rebuilding anything and without your database going with it.
- [Do I Need Kubernetes?](https://antideploy.com/docs/guides/do-i-need-kubernetes.md): For most web applications, no. Here is the honest boundary: what you actually need, when Kubernetes starts earning its cost, and where Antideploy stops.
- [Cloud Run the Hard Way](https://antideploy.com/docs/guides/cloud-run-the-hard-way.md): Seven things that break when you deploy a real application to Cloud Run by hand, and what each one actually means, including the build that reports SUCCESS and FAILURE at once.
- [Antideploy REST API: Overview](https://antideploy.com/docs/api/overview.md): Base URL, authentication, the four endpoints, rate limits, and error format for the Antideploy API.
- [API Authentication: Project Keys](https://antideploy.com/docs/api/authentication.md): How Antideploy API keys work: one key per application, how to create and revoke them, and what a leaked key can and cannot do.