Getting started

What agenthost is

Hosting your agent drives. You ask for a link; your agent sends the files and we run them. What you need, what you can put online, and what you never have to learn.

You built something with an agent — a page, a small app, a tool for your team — and now it only exists on your computer. agenthost is where it goes to become a link you can send to someone.

The difference from every other host is who does the work. You do not sign up for a dashboard, pick a framework preset, set a build command and open a port. You ask your agent, and your agent does all of it through a connection you set up once.

What you need

  • An agent that can write code and use tools. Claude (app or claude.ai), Claude Code, Cursor, VS Code with Copilot agent mode — anything that speaks MCP. See Connect your agent.
  • An email address. That is the whole of signing up. There is no password and no API key to paste anywhere.
  • Something you made. It does not have to be finished.

You do not need to know what your project is built with. Your agent already does, and it tells us.

What you can put online

What you madeWhat it needsNotes
A website, landing page, portfolio, docsNothing running — just filesFree on the Starter plan
A single-page app you've already built (React, Vue, Svelte…)The built filesStill just files, so it counts as a site
An app that runs code — a form that saves things, an API, a dashboardA server behind itNode, Python or PHP. Needs the paid plan
A tool only your team should seeA server or files, plus invite-only accessSee Make something private
A preview for a client, on your own domainYour domain pointed at usSee Use your own domain

What runs is Node, Python, PHP, or plain files served as-is. If your agent wrote it in something else, ask it — it can usually build the project down to one of those.

What it looks like in practice

you    can you put this online?

agent  It's live at recipe-box-8f2a.customer.agenthost.eu
       Anyone with the link can open it.

you    can it be on recipes.mydomain.com instead?

agent  Add this DNS record at your registrar and it'll switch over:
       CNAME  recipes  →  ingress.agenthost.eu
       HTTPS is set up automatically once that resolves.

That is the actual shape of it. The link works immediately; the domain and the padlock follow when DNS does.

What you never have to learn

Ports, Dockerfiles, nginx, TLS certificates, DNS record types, build commands, CI pipelines, package managers, reverse proxies. agenthost has no settings for any of them — not hidden ones, none at all. How an app starts is fixed by convention per language, so there is nothing to get wrong.

If you want to know, all of it is written down in Runtimes and the toolbelt. It is just never required.

What it costs

Static sites are free — a real allowance, forever, with no card. Anything that runs code is on the paid plan, at a small monthly amount per app, and you add them one at a time rather than jumping to a bigger tier. The pricing page has the current numbers and worked examples; Plans & what counts explains how the counting works and why a site with twelve pages is still one site.

Where your app lives

In Europe — your app and its data sit in EU data centres, under European rules. Your files are yours, and you can ask your agent for them back at any time. Nothing here is a format only we can read.