Skip to main content
Three ways in. All three end at the same place: Antideploy reads your code, works out what it needs, builds it, and gives you an HTTPS URL.

​
Method 1: GitHub

Best when you want every push to redeploy.
1

Install the GitHub App

From the dashboard, choose Repositories and install the Antideploy GitHub App on the account or organization that owns your repo. Grant it access to all repositories, or pick specific ones.
2

Pick a repository

Select the repo you want to deploy. Antideploy fetches it and analyzes it immediately.
3

Review what it found

You’ll see the detected runtime, framework, build and start commands, port, and whether a database is needed, with the evidence for each. Warnings and hazards appear here, before anything is built.
4

Deploy

Press Deploy. Progress is shown step by step: analyze, build, release, health check. When it finishes you get a live HTTPS URL.
Every subsequent push to the default branch redeploys automatically.

​
Method 2: Upload a folder

Best when there’s no Git repo, or the code isn’t on GitHub.
1

Create a project

In the dashboard, choose New project → Upload.
2

Drag your folder in

Drop the project folder or a .zip onto the upload area. Dependency and build directories (node_modules, .git, dist, .next) are excluded automatically; you don’t need to clean the folder first.
3

Review and deploy

Same analysis and same deploy flow as above.
To ship a new version, upload the folder again.

​
Method 3: Push over the API

Best for scripts and AI coding agents. There is no CLI to install.
1

Get a credential

If an agent is doing this, let it run the terminal login itself. You approve one browser prompt, and it creates the project and stores the token without anything being copied or pasted.Working by hand instead? In the dashboard, choose New project → API. You get a project API key, shown once, scoped to that one project.
2

Push the project directory

From your project root:
An account token has to say which project it is for: add ?applicationId=$APP_ID to the URL. A project key already knows.
Send the whole directory, not just your entry file. A push containing only index.html succeeds, deploys, and then serves a page whose scripts, styles and images all 404. Check the files array in the response: if you expected a project and see one file, the upload was wrong.
3

Watch it finish

The response includes a taskId and a watch URL. Poll it until status is succeeded or failed:
If you’re pointing an AI agent at Antideploy, give it https://antideploy.com/llms.txt and nothing else. It explains the whole path from an empty terminal to a live URL, and links the full contract at https://antideploy.com/api/v1, which is readable without a credential.You do not need to hand it a key. It can get its own, and a credential pasted into a chat window stays in that conversation’s transcript for good.
See Deploy over the API for the complete reference.

​
What you get

A live HTTPS URL, a history of every deploy, searchable logs, and health checks that email you if the app goes down.

​
Before you rely on it

Antideploy raises hazards during analysis for things that will not work once deployed: files written to local disk, background workers, polling loops. Read them. They are the difference between “deployed” and “working.”