When to use it
- No Git repository: the project lives only on disk, or came out of a tool that never made one.
- A quick test: you want to see it running somewhere real before wiring up anything permanent.
- An AI-generated project: Claude Code, Cursor, Bolt and the like leave you a folder, and a folder is exactly what this takes.
Upload your app
1
Start a new application
Click New application in the dashboard and choose the upload option.
2
Pick the folder
Your browser opens a folder picker. Select the project root, the
directory holding
package.json, requirements.txt, or index.html.Dependency and build directories are filtered out as it reads, so there is
nothing to clean up first.3
Review what was detected
Antideploy shows the runtime, framework, install and start commands, the
port, and any database it found, each with the evidence behind it.Read the warnings and hazards here. This is the moment to catch a project
that will build fine and then not do what you meant.
4
Deploy
Click deploy and watch the steps. When it finishes you get an HTTPS URL.
What is excluded automatically
node_modules · .git · .next · dist · build
These are dependencies and build output. Antideploy installs and builds on its
side, so sending them wastes your upload budget and changes nothing.
Limits
Compared to GitHub deploy
Preview environments, per-branch deploys and pull-request builds do not exist on
either path; see what is not provisioned.
Environment variables
Supplying the values your app expects before the first deploy.