Skip to main content
Antideploy takes a project and gets it running in production. You don’t describe your app to it; it reads the code and works out what it is, what it depends on, how to build it, and how to start it.

​
Getting code in

GitHub

Connect a repository. Every push to the default branch redeploys.

Upload

Drag a folder or ZIP into the dashboard. No Git required.

API

Push a project directory over HTTP. What a coding agent uses.

​
What happens after that

1

Analysis

Antideploy reads your files and produces a spec: language, framework, build command, start command, port, and whether it needs a database. You can see exactly what it concluded, and the evidence for each conclusion, before anything is built.
2

Provisioning

If your code uses Postgres, a database is created and its connection string is injected as DATABASE_URL. This is the only infrastructure Antideploy provisions today.
3

Build

Your project is built into a container image. Static sites skip the buildpack step entirely and are layered onto a minimal server, which takes them from roughly three minutes to about seventy seconds.
4

Release

The container is deployed and given an HTTPS URL. Environment variables are injected at this point. The previous version keeps serving until the new one reports healthy.

​
What you never configure

  • Containers. No Dockerfile unless you want one; if you have one, it’s used.
  • Build and start commands. Inferred from your project, and shown to you.
  • Postgres. Created and wired up when your code needs it.
  • TLS. Every app gets HTTPS.
  • Idle cost. Apps scale to zero and cost nothing while nobody is using them.

​
What Antideploy does not do yet

Being straight about this is more useful than a longer feature list.
  • No object storage. Files written to disk are lost on restart or redeploy. Bring your own S3-compatible bucket.
  • No custom domains. Apps are served on a generated HTTPS URL.
  • No background workers or cron. If your project defines them, Antideploy tells you at analysis time; they will not run.
  • No staging or preview environments. One deployed version per project.
  • No horizontal scaling. Each app runs on a single instance that scales to zero when idle.
  • No Redis or caching layer. Supply your own REDIS_URL.
Antideploy raises these as hazards during analysis, before you deploy, rather than letting you discover them in production.

​
Operating a deployed app

Logs

Search and read your application’s output.

Deployments

Full history, with one-click rollback to any previous release.

Monitoring

Health checks, with email when an app goes down or recovers.

Environment variables

Configuration and secrets, encrypted at rest.

​
Start

Deploy something in five minutes

Connect a repository, upload a folder, or push over the API.