PlatformStatic sites
Static site hosting, free on every plan.
A folder of HTML, or a frontend that builds to files. Host as many as you like, with HTTPS and an address from the first deploy. Static sites never count against your apps or your deploys, on any plan, forever.
- Unlimited, foreverNever counted against any plan, as many sites as you like
- Failed deploys are freeFix it and push again at no cost
- HTTPS includedA name.antideploy.app address with its certificate
- About 36 secondsFrom push to live, for a static site, from the platform's own records
01How it works
Three ways in. Same result.
However your files reach Antideploy, the site is checked, built if it needs building, and served over HTTPS.
Ask your agent, push to GitHub, or drag a folder.
Paste the sentence into your coding agent and it deploys the folder for you. Or connect a GitHub repository once and every push goes live. Or drop a folder or a .zip into the console: no Git and nothing to install, and dependencies and build output are skipped for you.
- No repository needed for an agent or a folder deploy
- Dependencies, build output and junk such as .git and node_modules are skipped
- Rename your address whenever you like, on every plan
# with your coding agent
> Deploy this site with Antideploy
# or with GitHub connected, every push goes live
$ git push
Files, or a frontend that builds to files.
A static site is anything that is only files. That includes a plain folder of HTML, CSS and images, and frontends such as Vite, Create React App, Astro and Gatsby that compile to files. Antideploy runs the build for the second kind, then serves the result.
- No server to run, so nothing to keep up to date or patch
- A frontend that also needs a server of its own is a full app, not a static site
- Whether a project is static is decided when it is analysed, and the deploy says what it found
my-site/ # a folder of files
index.html
about.html
assets/
my-vite-app/ # a frontend that builds to files
package.json # "build": "vite build"
src/
02What you get
Free, and not a demo.
Static sites are not a trial of the paid plans. They are free on every plan, with the same address, the same HTTPS and the same checks.
-
Never counted. A static site does not use one of your live apps and its deploys do not use one of your deploys. Nothing about it is metered, so a hundred static sites cost the same as one.
-
HTTPS and an address from the first deploy. The certificate is issued automatically. Your site is live the moment it deploys, at
name.antideploy.app, and you can rename it any time. -
Checked for phishing before it goes live. Every static site is checked for phishing pages before it goes live, and the security check that runs after every deploy looks at what the site shows the public. See security checks.
-
Your own domain from Go. Free accounts get an Antideploy address. From the Go plan you can attach your own domain with HTTPS included. See custom domains.
-
Sleeps when idle, like everything else. A static site that nobody is visiting goes to sleep and wakes on the next visit. A sleeping site costs you nothing.
-
The same history and logs. Every deploy is listed with the commit it built, and a failed one says why, in a sentence you can act on.
03Reference
What counts against your plan.
For a static site, nothing does.
| Thing | How it is treated |
|---|---|
| Static sites | Never count. Unlimited on every plan, forever. |
| Deploys of a static site | Never count against the monthly deploy allowance. |
| Failed deploys | Free, on every plan. |
| Custom domains | From the Go plan: 3 on Go, and unlimited on Pro and Scale. |
| Storage, bandwidth and build minutes | Not metered or capped today. |
| Upload size | A folder or archive pushed to Antideploy can hold up to 4,000 files and 28 MB. |
04Before you commit
Here's where it stops.
A static site is the simplest thing Antideploy hosts. Here is what that simplicity leaves out.
-
Files only
There is no server code and no database in a static site. If your project needs either, it is a full app and counts as one.
-
No custom domain on Free
Free accounts use an Antideploy address, which they can rename. Your own domain starts on Go.
-
A first visit can be slow
Like every app, a static site sleeps when idle, and the first request after it wakes takes a few seconds.
-
Phishing pages are stopped
A page built to collect passwords or card numbers and send them somewhere else is refused before it goes live. A login box that posts nowhere, or an ordinary contact form, passes.
05Questions
Static site questions, answered.
Anything else? Write to us and a person answers.
support@antideploy.comAre static sites really free?
Yes. On every plan, forever, and as many as you like. A static site is anything that is only files, such as a folder of HTML or a frontend that builds to files. It never counts toward your live apps or your deploys.
What counts as a static site?
A folder of HTML, CSS and images, or a frontend such as Vite, Create React App, Astro or Gatsby that builds to files. Whether a project is static is decided when it is analysed, and the deploy says what it found.
How long does a static site take to go live?
About 36 seconds from push to live, taken from the platform's own records.
Can I use my own domain on the free plan?
Not on Free: free accounts get an Antideploy address, which you can rename as often as you like. Go includes 3 custom domains and Pro and Scale include as many as you need, all with HTTPS.
Do static sites sleep?
Yes, like every app. A site that nobody is using goes to sleep and the next visit wakes it. A sleeping site costs you nothing.
Why are static sites checked for phishing?
Free, unlimited static hosting is where phishing pages tend to appear, and one fake bank login can get a whole domain flagged. A page that collects a password or a card number and sends it somewhere else, such as a chat bot or an outside form handler, is refused. A login form that posts nowhere, or a normal contact form, is fine.
What if my site needs a server later?
How big can a pushed folder be?
Up to 4,000 files and 28 MB. Dependencies and build output are skipped, so a project with a build step is usually far below that.
+The rest of the platform
Everything else your app can use.
Every service is created by your coding agent, wired into your app, and included in the plans. See the whole platform.
- Hosting
- Deployments
- Database
- Authentication
- File storage
- AI models
- Cron jobs
- Custom domains
- Environment variables
- Logs and monitoring
- Security checks
- Console
- Agent API
Facts on this page were checked against the live platform on 5 October 2026.
Put your site online. For free.
Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.