Your agent can build it. It can’t ship it.
siteio gives it somewhere to ship to. One command deploys the folder to your own server — with auth, a database, file storage and realtime already behind it. One more hands the live site back to your assistant.
→ https://demo.yourdomain.com
MIT licensed. Runs on your server, not ours. There is no plan to sign up for.
You know this moment.
The agent finishes. Everything works on localhost. And then it hands the problem back, politely, in whatever words it uses for this part is yours:
You know every one of those words. You have never had to be the person who does them.
So the project stays on your laptop, or it goes up as a static page with the interesting half removed. It isn’t that the agent doesn’t know how. It’s that there’s nowhere for it to do it.
Three things are yours. The rest is the agent’s.
siteio runs on a server you own. That sounds like the hard part, and it used to be. It is now a purchase, a paste and a sentence.
Buy a box.
Any VPS from any provider — Hetzner, DigitalOcean, Vultr. The cheapest tier is fine, around five euros a month. You are buying a machine, not a plan.
Paste the credential.
The provider gives you an IP address and a root login. Hand them to your agent the way you would hand keys to a contractor.
Ask.
One sentence. The agent connects over SSH, installs siteio, and tells you when there is somewhere to deploy to.
Install siteio on my server at <ip>, set it up for <yourdomain.com>, and tell me when I can deploy to it.
You do need a domain, and a wildcard DNS record pointing at the box. Your agent can walk you through the record; the registrar’s own interface is the one part nobody has automated.
Two commands, and it’s on the internet.
This is the entire tool, for the two cases you actually have: a site your agent built, and an app that needs to keep running.
A site
$ siteio sites deploy ./folder -n demo
→ https://demo.yourdomain.com
The folder your agent has been building all afternoon, served over HTTPS.
An app
$ siteio apps create api \
--git <repo> --port 3000
→ running behind the same domain
A Docker app with environment variables and volumes, on the same box.
You will mostly not type these. Your agent will. But you can read them, and that is the point — nothing here happens behind a dashboard you can’t see.
A site here is allowed to do things.
The second stop is always the same: the page is live, and then something on it needs to remember, admit, store or update. That is normally where you go shopping for four services and wire them together.
Logins
Members-only pages and client portals, without a plugin.
Saved data
Submissions, bookings, signups. Stored, exportable, yours.
File uploads
Let people send you files, straight into the site.
Live updates
Things that change without someone hitting refresh.
They’re there when the site wants them.
What it costs today.
siteio is free and it always will be, because we don’t run the servers. The only bill is a machine you rent from somebody else, and you can check every line of it yourself.
The last row is not a promotion. We don’t bill per site because we don’t know how many you have.
If we ever host it for you.
These are the tiers we would charge if siteio ran the servers instead of you. None of them exist. There is no signup, no waitlist and no card — they are here so you can see the shape of the idea and tell us whether it’s the thing you actually want.
- 1 website
- Address at you.siteio.app
- Editing by chat
- HTTPS included
- 7 days of history
- Small siteio badge
- 5 websites
- Your own domain
- Logins & saved data
- 10 GB of uploads
- 30 days of history
- No badge
- Unlimited websites
- Unlimited custom domains
- Client share links
- 100 GB of uploads
- Full history & rollback
- Docker apps · 3 seats
- Everything in Studio
- White-label
- Separate client accounts
- 1 TB of uploads
- 10 team seats
- Same-day support
The only thing that would make us build any of this is people asking for it. Until then the row above is the whole price: your own box, and a tool that costs nothing.
What doesn’t exist yet
Said plainly, so you can tell whether this is for you today:
- A hosted version. There is a tool, and a server you own.
- A web dashboard. The interface is the CLI and your agent.
- A one-click custom domain. You set a wildcard DNS record once.
- An account, a signup, or a card on file.
- Customers, case studies or testimonials we could show you.
When any of that changes, this page will change. It won’t change first.
There’s nothing to leave.
Every site builder you have used was designed so that getting out would cost more than staying. siteio is MIT licensed and it runs on your machine. The software serving your site is the software in the repository. There is no account to close, no export to request and no plan to cancel, because none of those things exist.
We don’t have a way to hold your site hostage. That isn’t a policy. It’s the architecture.
The things you’re about to ask.
I’ve never bought a server. What am I actually buying?
A computer you rent by the month. You get an IP address and a login. Nothing is installed on it, and nothing is expected of you.
What if my agent breaks it?
It’s a machine that costs five euros and holds nothing but your sites. Destroy it and make another; it is the least precious thing you own. Once it holds real data, take backups.
Do I need to use the terminal?
You need to have one open. Your agent types in it. Reading what it typed is a good habit, not a requirement.
Can I use this without an agent?
Yes. It’s a CLI, and it was a CLI first. But this page is aimed at people who have an agent, because that is who this stops being hard for.
What about a custom domain?
Sites land on subdomains of a domain you already control, via a wildcard record you set once. There is no one-click flow and we’re not going to pretend there is.
Is there a hosted version?
No. If that changes, this page will say so.
Buy a box. Paste a credential. Ask your agent.
siteio sites deploy ./my-app -n demo
MIT licensed. Runs on a server you own. There is no account.