This is the complete list of what Simple Host can do today — one entry per capability, with where you find it and what it will not do. It exists so that "does this already exist?" has an answer you can read, and so a feature can never quietly stop working without someone noticing it is missing from a screen.
Entries that are half-built are marked as such rather than left off. A feature that does not finish the job is more expensive than one that was never offered, so the marked ones are the important part of this page.
Two owner screens exist. Every entry says which one it lives on:
Your own address — simple-host.app/your-handle. Signing in takes you here. It has a Sites tab, an Analytics tab, the AI chat and the setup panel for your AI agent.
The older screen, reached with ＋ New site from your sites page. It has the paste builder and the site cards, and it is the only place with Data and Connect domain.
Status marks used below:
Real and working, but there is no button for it. You ask your AI agent and it does it for you.
Only visible to the person who runs the service.
It exists, but it does not finish the job on its own. The gap is written out in the entry.
Built, but switched off or not connected up on this instance. It does nothing for you today.
One account covers everything: publishing your own sites, and signing in as a visitor on somebody else's.
Type your email, get a six-digit code, type it back. There is no password to choose or remember, and no separate sign-up step — your first code creates the account.
The same email carries a link. Tapping it signs you in without typing the code at all.
One tap instead of the email round-trip. It is the same account as the email sign-in when the addresses match, so you will not end up with two.
More providers later.
Every account gets a short public name. It is the front of every address you publish and the address of your public profile.
A personal key that lets your coding agent publish and manage sites for you without you being at the keyboard.
Someone reading one of your pages can sign in right there — with Google, or with a 6-digit code emailed to them — and the page can then save on their behalf.
auth.js) and that handles the rest.sites.simple-host.app host there is no visitor sign-in, because every site there shares one origin — pages there still save, but anyone can change that data. Connecting a domain is what adds sign-in.A visitor's sign-in is scoped to the one site they signed in on, and they can end it.
Three ways in: paste a page in, hand a folder to your agent, or have the AI write it. All three end at the same live address.
Send the page itself — the HTML and anything alongside it — and it is live in seconds. No build step, no upload dialog, no waiting.
Hand over a zipped folder — the output of a normal web build, images and fonts included — and the whole thing goes live at once.
Publishing again to the same name replaces what visitors see, instantly, at the same address.
The name you pick becomes the last part of the address, so it is worth choosing something readable.
The moment a site exists it has a working web address you can send to anyone, with HTTPS already on.
What you publish is served back exactly as it is. Your page's own scripts run in the visitor's browser as normal; nothing you upload ever executes on the server.
One account can hold up to a hundred separate sites, so throwaway experiments do not need a second account.
Sites published under the older style of address are forwarded to the current one, so links you have already shared keep working.
Everything published stays listed, versioned and reversible. Nothing is ever overwritten so completely that you cannot get it back.
One list of everything you have published, with its address, its current version number, and whether it is live.
Each time you publish, the previous state is kept intact and numbered, with the date it went live.
Pick any earlier version and make it the live one again. The switch is immediate.
Give a site a new name without republishing it. Its versions and its saved data come with it.
Removes the site, every version of it, and its address.
A public site is listed on your profile page. An unlisted one is not — it is reachable only by its link.
Your handle has its own page showing your public sites, so you can share one link instead of five.
A mistyped address on a site gets a clean, branded page with a way back, instead of a raw server error.
Every site gets a small shared store, with no database to set up. It is what makes a counter, a vote, a poll or a saved game state possible on a static page.
A page can add one to a number, add an item to a list, or remove one, without reading the whole box first. Two visitors doing it at the same instant both count.
A page can keep checking for changes very cheaply, so a count or a comment thread updates itself while people are looking at it.
Sites and their data are public to anyone with the link. This is stated plainly because it is the single most important thing to know before you build.
On the shared host anyone can read and write. On your own domain saving requires a signed-in visitor or an API key, so a passer-by cannot fill your store with junk. Reading never requires either.
sites.simple-host.app host there is no visitor sign-in, so writes there are open — anyone can change that data. Connect your own domain to add sign-in.A page hosted somewhere else entirely can use one of your sites here as its backend, once you have allowed that page's address.
Where form entries go. A collection is a growing list — one row per submission — separate from the shared box so it can grow without limit on the page.
Each submission is added to a named list — RSVPs, signups, orders, messages. Adding stays fast no matter how long the list gets.
A page can read its own entries, newest first, so you can build a guest list or a public wall that shows what has come in.
A panel listing each collection on a site with how many entries it holds and when the last one arrived, and a table view of the entries themselves.
One button gives you the whole collection as a CSV file you can open in any spreadsheet.
A site can be served from a domain you own, so nothing in the address mentions this service.
Attach a domain you own — a subdomain like recipes.yourbrand.com or the bare domain itself — to one of your sites. Once connected, the site is served only on your domain: the old sites.simple-host.app link redirects there, and saving happens only there.
409 domain_taken).Connecting hands back the single DNS record to paste into your registrar — no guessing, no documentation to read.
A connected domain is served over HTTPS with a valid certificate.
The site card shows the domain you attached, with a status next to it.
Detaches the domain and stops serving your site from it, freeing the domain to be used on another site. The shared-host address stops redirecting and serves the site again, saving goes back to the open shared-host model, and links people kept to the domain stop working.
Describe the site you want and watch it appear. There are two routes, and they differ in one important way: only one of them can publish.
Say what you want in plain language — "a landing page for my coffee shop" — and a complete page is built for you, working backend and all.
Ask for a change — different colours, another section, fix the wording — and the same page is revised rather than started over.
The built page appears live in the chat, and can be opened full-screen in its own tab to judge properly.
Copy a ready-made prompt, paste it into whichever AI you already pay for, and paste the answer back here. It arrives as a working site.
Before publishing you see the real page, with the file list, and can open it full screen.
Name it, publish, and it is live. From then on the builder stays tied to that site, so the next paste updates it rather than making a second one — with Publish as new if you do want a copy.
The chat runs on exactly one AI provider. If it is unavailable you are told the build failed — you are never quietly switched to a different, worse model.
A full build takes a minute or more, so it runs behind the scenes and the page keeps showing progress rather than freezing or timing out.
Two ways to describe a site without typing it — both aimed squarely at building from a phone.
Press the microphone, say what you want, and it becomes text in the box. The words stay editable before you send them, so a misheard name is fixable.
Words appear as you say them, so you can tell immediately that it is hearing you correctly instead of finding out at the end.
Speech is turned into text on this same machine rather than being sent to an outside company.
Add a picture of a design you like, or a page of notes, and have the site built from it instead of described from scratch. Both are genuinely read.
How many people actually read your site — separated from crawlers and from the service's own monitoring, because on a small site those swamp the real number entirely.
Every visit is put in one of four groups — People, Bots, Infra and Earlier — and they are never added together into one misleading total.
When you want one figure for how the site is doing, it is People. Everything else on the panel is context.
This machine checks every site is still up roughly twice a minute. That is thousands of hits a day per site and it is not audience, so it sits in its own Infra figure, out of the way.
The visitor figure is how many different people came over the whole period — not the daily figures added up. Someone who visits on five days counts once.
A small line per site showing day-by-day readership, so a spike or a decline is visible at a glance without opening anything.
A short bar chart of the last day, with people stacked above bots, so you can see whether something is happening right now.
Traffic recorded before 9 August 2026 predates the people-versus-bots split. It is real and it is still shown, but as its own Earlier figure rather than being guessed into the other columns.
Each site on the main dashboard carries its own last-30-days figures and its 24-hour chart, so you never have to open a separate report.
A dedicated screen with your totals across every site and one row per site, most-read first.
Switch the whole Analytics tab between the last 7, 14, 30 or 90 days.
Your sites are ordered by how many real people read them, so what is working is at the top instead of whatever you made first. You can also sort by bots, by all traffic, or by name.
There is no tracking script, no tag to install and no cookie banner to add. Counting happens on the service's side, and a visitor's address is never stored as-is.
People, by country, for each site — so you can tell whether a site is reaching the place it was made for.
For whoever runs the service. Everyone else gets an ordinary "not found" page, with no hint that these screens exist.
One card per person: their handle, when they joined, how many sites they have and where each one lives.
The full list of sites with their owner shown next to each, using the same cards and buttons as your own.
Today's calls, callers, errors and AI builds, plus two tables: what is being called most, and who is calling — with rough locations and when they were last seen.
The same people-and-bots split, widened from your own sites to every site on the service.
Accounts the operator nominates get sites that delete themselves after a set time — for a public demo or a workshop where nobody wants to clean up afterwards.
An escape hatch for a single site that has to keep accepting unsigned saves now that visitor sign-in is required.
Most of this service is designed to be driven by an agent rather than clicked. These are the pieces that teach one how.
Teaches your agent the whole job: sign you up, check a site before publishing, publish it, wire up the backend, and confirm the live page really works before saying it is done.
Helps decide whether an idea fits here before any code is written, maps it to what the service can actually do, and says plainly when an idea needs a real server instead.
Walks your agent through connecting your own domain: attach it, tell you the one record to add, then check the domain itself until it answers.
Four routes side by side — a coding agent, the Claude app, building here in the browser, or pasting a prompt into any chatbot — with the exact commands for each.
A single command installs the skills into your agent, on Mac, Linux or Windows, with no accounts to link and nothing to clone.
Tick which tools you use and which operating system you are on, and it writes out exactly the commands to run, with your key ready to copy underneath.
A button that opens the AI chat with your tool and operating system already filled in, so you can describe the problem instead of the setup.
If your agent is working from an old copy of the instructions, the service tells it so as it works, rather than letting it fail in a confusing way later.
A ready-written brief you paste into any AI, which makes it produce a site that works here — backend, live counts and all — with no skill installed anywhere.
Complete, browsable documentation of everything the service can do, for anyone integrating directly rather than through a skill.
Things people reasonably expect, or have read about somewhere, that do not exist. Listed so nobody spends a morning looking for them.
| Sharing a site with someone else | No collaborators, no second owner, no team. A site belongs to one account. |
| Editing or deleting one saved entry | Collections only grow. A mistaken or unwanted submission cannot be removed — not from a screen, not by an agent. |
| Private or password-protected sites | There is no way to put a password on a site, and no encrypted mode. Assume anything published is readable by anyone with the link. |
| Attaching a PDF to the AI chat | PDFs are not accepted. Screenshot the page you want copied, or paste the text. |
| Email when something arrives | No notifications of any kind — not for form entries or traffic. You check, or your agent does. |
| Referrers or page-level traffic | Traffic is per site: people, bots, monitoring, a trend and countries. Nothing about which link a visitor came from or which page they read. |
| Anything that runs on the server | No server-side code, no scheduled jobs, no image processing, no sending mail from your site. Deliberate, and it is what keeps this safe to host. |
If something you need is on this list, say so — the point of writing it down is to make the gap arguable rather than invisible.