Your agent built it. Let it put it online.

Ask, and your app is live on a real link you can send to anyone. No dashboard to learn, no settings to get wrong, nothing to set up first.

Whatever you made this week.

You don't need to know what it's built with. Your agent already does — it picks the right setup and tells us. Pick the one that sounds like your thing.

Are you a developer? That means static sites, Node, Python and PHP. The runtime pages and the deploy reference spell out exactly what runs.

Grows with you

Most hosting makes you graduate to a harder tool the moment your app starts to matter. Here you just keep asking for the next thing.

Can you make it live?

Your agent sends the files, we run them, and about a minute later there’s a link. Change something and ask again — it updates in place, and the link stays the same.

Can it be on my own domain?

Point your domain at your app and your agent handles the rest, including the certificate that puts the padlock in the address bar. It stops looking like a demo and starts looking like yours.

Can it remember things?

Every app comes with a database, already connected — there is no second thing to buy and no connection string to handle. Sign-ups, saved notes, orders: whatever your app collects is still there tomorrow.

Can I keep it private?

Say who’s allowed in and only those email addresses can open it. Good for showing a client, and good for the tool that’s just for you and two colleagues.

  • package managers
  • runtimes
  • build commands
  • ports
  • Dockerfiles
  • nginx
  • reverse proxies
  • SSH keys
  • firewall rules
  • systemd
  • Kubernetes

You never have to learn what any of this is called.

Every other host asks you to pick a framework preset, set a build command, fix the build command, open a port, then wait to find out which one you got wrong. agenthost has none of those settings — for anyone.

  • TLS renewal
  • health checks
  • cron syntax
  • log rotation
  • DNS records
  • SSL certificates
  • connection strings
  • YAML
  • environment variables
  • CI pipelines
  • server updates
  • load balancers

Your agent knows all of it. If you want to know too, it’s in the docs — just never required.

The things you're actually wondering.

What if I break it?

Every time you put something online it becomes a new version, and the old one is kept. Ask your agent to put the previous one back and it will. Nothing you deploy is one-way.

What is this going to cost me?

Static sites are free — ten of them, forever, with no card, and a site with several pages still counts as one. Anything that runs code is €4 a month with its database included, and you add those one at a time rather than jumping to a bigger tier. The whole thing is on the pricing page, with worked examples, before you sign up.

What if something breaks and I don't understand the error?

Ask your agent. It can read your app’s logs directly and tell you what happened in plain language — usually along with the fix. The thing that built your app is also the thing that debugs it.

Is it mine? Can I take it somewhere else?

Yes. Your files are yours and your data is yours, and you can ask your agent for either at any time. Nothing here is a format only we can read.

Where does my app actually live?

In Europe. Your app and everything it stores sit in EU data centres, under European rules — which matters more than usual once your app starts collecting other people’s details.

Do I have to be a developer?

No — that’s the whole point of building it this way. You do need an agent that can write the app, and a rough idea of what you want it to do. It helps you nothing to know what a container is.

Ask your agent to put it online.

Ten static sites free forever, no card, and your first link takes about a minute. When it needs a server behind it, that's €4 a month with a database included.