Put a website online

This is the simplest thing agenthost does, and the free one. If your project is a set of files with an index.html in it, there is nothing to build and nothing to start.

Ask for it

put this site online

Add a name if you care what the address looks like:

put this online and call it spring-launch

You get back a link like spring-launch-8f2a.customer.agenthost.eu, with HTTPS already working. Anyone with the link can open it.

What counts as a site

• A hand-written HTML page and whatever sits beside it — CSS, images, fonts.
• A multi-page site: about.html is served at /about.html, docs/index.html at /docs/.
• A built single-page app. React, Vue, Svelte, Astro — if your agent has already run the build, the output folder (dist, build, out) is a site. Ask it to build first and deploy the output.

If your project needs code running to answer a request — a form that saves something, an API, a login — that's an app, not a site.

What your files should look like

The only rule: index.html at the project root. That's what tells us this is a site, and it's what gets served at /.

Then

• Change it and ask again — the same link updates. See Update what's live.
• Put it on your own domain — decide this when the app is created if you can. See Use your own domain.
• Keep it private — invite-only by email, for a client preview. See Make something private.

Under the hood

Your files are served by nginx, exactly as handed. There is no build step, no framework detection and nothing to start, so a static deploy is the fastest thing here — usually well under a minute.

A single-page app that does its own client-side routing has one caveat: paths that don't match a real file return a 404 rather than falling back to index.html. Use hash routing, pre-render your routes, or deploy it as a Node app that serves the fallback itself.

The static runtime is inferred from an index.html at the project root and takes no version. Full detail: Static sites.