Files in, page out.
An index.html and whatever sits next to it. No build step, no bundler, no framework to declare — and this is the free part of agenthost.
index.html, at the top level.
The only convention is an index.html at the root of the files you send — not inside a dist/ or public/ folder. Everything beside it is served at the path it sits at, so about.html is at /about.html and css/site.css is at /css/site.css.
If your project has a build step — Vite, Astro, a static Next export — run it locally and send the output folder, not the source. Your agent knows to do this; agenthost never runs a build for a static site.
Anything loaded from a CDN works as-is, because nothing needs compiling first. Tailwind from a script tag, Alpine, htmx, a Google font — all fine.
index.html styles.css logo.svg about.html
Everything the platform expects.
Four facts, and they are the complete set — there is nothing else to get right.
index.html at the root of what you send, and no package.json / requirements.txt / composer.jsonindex.html as the entry page- build commands
- start commands
- ports
- Dockerfiles
- nginx
- systemd
- process managers
You configure none of this.
There is no build command, no start command and no port setting — for any runtime. Your agent sends files; what runs them is worked out from what's inside.
- TLS renewal
- health checks
- restart policies
- log rotation
- scaling rules
- deploy hooks
- CI pipelines
The one thing each runtime does expect is its entrypoint, and that’s on this page. The deploy reference is the exhaustive version your agent reads.
Will it run what you built?
We'd rather you found out here than mid-deploy, so both halves get the same billing.
Yes — what people deploy here
Landing pages · portfolios · documentation · one-pagers · link-in-bio pages · event and wedding pages · generated reports and charts · the built output of any static site generator
No — what doesn’t work
Anything that needs a server. There is no server-side code, no request handling and no database — so no form that saves what a visitor typed, no login, no API keys that stay secret. Those need Node, Python or PHP. A form that posts to someone else’s API is fine, as long as the key in it is safe to be public.
Why a deploy doesn't come up.
Your agent will usually get these right, and can read the logs when it doesn't. Listed anyway, because knowing the shape of the failure makes the log message make sense.
index.html is one folder down.
Sending a project whose page is at dist/index.html means there is no index.html at the root, so the site isn’t detected as static at all. Send the contents of dist/, not the folder containing it.
A stray package.json.
A package.json at the root makes this look like a Node app, and then it fails for want of a start script. If your build tooling left one behind, it shouldn’t be in what you send.
Absolute paths from your machine.
A link to /Users/you/project/logo.svg works locally and nowhere else. Paths need to be relative to the site, which is what your agent will produce if it knows this is going online.
Not what you're building?
Point your agent at it.
Ten static sites free forever, no card. Your agent reads the deploy reference itself, so you don't have to.