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.
Each entry says what it does, where it stops, and whether it is a screen or something your agent does for you.
The same software runs on a server of your own: Run your own → Set up.
Where you manage things. Every entry says which screen it lives on:
At simple-host.app/your-handle. Signing in takes you here. It is where you manage every site: its address, versions, rename, domain, lists, saved data, download and delete. It also has an Analytics tab and the setup panel for your AI app.
The older screen, reached with ＋ New site from your sites page. It lists your sites with a Manage link back to your sites page, and holds Sign out everywhere.
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.
One account covers everything: publishing your own sites, and signing in as a visitor on somebody else's.
Your personal address opens your showcase by default. Choose one of your sites as home in Your address, or ask your connected app to “make this my home page”. Its normal address keeps working; if it is unavailable your showcase appears.
GET/PUT /v1/me/home; connector set_home_page. Visitor sign-in and saved data cover the selected site only. A custom home can list your projects live from GET /v1/u/{handle}/showcase.json; it includes the public showcase’s entries, metadata, bio and curated order.set_bio and set_showcase_site; REST GET/PUT /v1/me/bio and GET/PUT /v1/sites/{site}/showcase. The bio limit defaults to 280 characters and is configurable. On small-box path installs, the public person page opens the selected site’s usual URL; the owner dashboard keeps its address. Simple Hack has no personal sites.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 part 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.A visitor's sign-in is scoped to the address they signed in on, and they can end it.
Sign out ends the key this browser holds. Sign out everywhere stops every key on the account at once, disconnects every connected app and ends every sign-in on your sites; the browser you pressed it in gets a fresh key.
Move the account to another address. A code goes to the new address and another to the current one, and both are needed. Your handle, sites and connected apps stay; other keys are signed out.
After each sign-in (code, link or Google) or app connection you get one short email: when, which browser or app, and a link to Sign out everywhere.
Download my data gives one .zip of everything held about you: account details, keys (never the keys themselves), connected apps, what you sent to other people's sites, and every site with its saved data. Delete my account removes the account and all of it at once.
Ask your own AI app (with Simple Host added to it) to publish. It ends at a 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.
files; images, fonts and other binaries go base64-encoded in files_base64 in the same request. A site must include a home page, and script files are refused.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.
One call creates the site the first time and publishes a new version after that, so a build pipeline (GitHub Actions and the like) can publish on every push.
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.
https://<site>.<handle>.simple-host.app/. On a brand-new account it can be https://<handle>.simple-host.app/<site>/ for the first few minutes, until its certificate is ready; the address shown is always the one that works. For a nicer address, take a free <name>.simple-host.app or connect your own domain.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: old <handle>.simple-host.app/<site>/ and sites.simple-host.app/<handle>/<site>/ links redirect to the site's own address.
Take a copy any time. Simple Host keeps your 4 latest versions; operator exceptions apply. Self-hosted instances choose their own retention.
One list of everything you have published, with its address, its current version number, and whether it is live.
Keep your live version and 3 to roll back to, numbered and dated. An older live version always stays. The operator decides who can change the count.
Pick any earlier version and make it the live one again. The switch is immediate.
Ask your AI app to store a change without publishing it, then open a preview link that shows that version exactly as visitors would see it. Any earlier version can be previewed the same way before you put it back.
Give a site a new name without republishing it. Its versions and its saved data come with it.
Takes the site offline at once, with every version and its saved visitor data. Recently deleted keeps it for 7 days, and Restore brings it back exactly as it was.
Every address of the site shows “This site is offline” and visitors can no longer save anything, while its pages, versions and saved data stay exactly as they are. Put it back online whenever you like.
One file with every page of the live version, the site's saved data and everything its lists hold, to keep as a backup or take elsewhere.
.tar.gz archive, as it is at that moment. There is no way to upload it back in one step; your agent can republish the pages from it.A public site is listed on your profile page. Unlisted: hidden from your showcase page, and from search engines unless the site has its own domain or name. Anyone with the link can still open it.
Your handle has its own page showing your public sites, https://<handle>.simple-host.app/, 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.
Each person's records: people add records, see only their own status and history; you see and update all. For shop orders, RSVPs and event sign-ups, bookings and appointments, applications (jobs, clubs, hackathons), support requests, homework or assignment submissions, survey answers people can revisit, and a waitlist with “my place in line”.
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.
Pages and shared data are public; Each person's records, private Submissions and Personal records have their own read rules.
Every save from a page needs a signed-in visitor, so a passer-by cannot fill your store with junk. Your agent saves with your API key (or the connector). Reading never requires either.
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 well past it (a declared Submissions name holds at most 10,000 live entries).
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.
Every list on a site, with whether it is public or private, how many entries it holds and when the last one arrived, and a table of the entries themselves. You can delete any entry (spam in a guestbook, a test RSVP), correct an entry in a private list, or clear a whole list after typing its name.
One button gives you the whole collection as a CSV file you can open in any spreadsheet.
A collection can be made private: only signed-in visitors can submit; you read them all, and each visitor sees, changes and withdraws only their own. Each entry is stamped with the visitor's verified email and the time.
Each data name a site uses is one kind, and the kind decides who reads and who changes what: Page info (you write, everyone reads), Submissions (visitors send; private to you by default), Personal (one private record per visitor that follows them to any device) and Shared board (a list a group edits item by item). A name nobody declared is Shared, as before.
Choose whether anyone who signs in may save on a site, or only listed emails and whole @domains. Block next to any entry stops that person saving there again.
New Submissions can email you: once a day (the default for private ones), soon after each arrives, or not at all. Every email has a link that stops them.
Every change to saved data is kept, with who made it: open History to undo one change or put a whole document back, and Recently deleted to restore entries one by one or all at once.
Want a nicer address? Take a free <name>.simple-host.app, or connect your own domain so nothing in the address mentions this service. The site moves there and its old address redirects. It is optional: sign-in and private collections already work on every site's own address.
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: its <site>.<handle>.simple-host.app address redirects there, and visitors sign in and save there.
409 domain_taken). A name another site on this server already serves cannot be connected.Connecting hands back the two DNS records to paste into your registrar: the one that points your domain here, and a TXT record that shows the domain is yours (keep it in place). No guessing, no documentation to read.
A connected domain is served over HTTPS with a valid certificate.
_simple-host.<your domain>) is in place, usually within minutes. Until then your site keeps its current address. www and the bare domain can both work on one certificate.Your sites page shows the domain you attached, with its status. Until it is live, Domain shows the two DNS records to add, what the last check found, when an unproven connection lapses, and Check again.
Detaches the domain and stops serving your site from it, freeing the domain to be used on another site. The site's <site>.<handle>.simple-host.app address stops redirecting and serves the site again, with sign-in and saving there, and links people kept to the domain stop working.
Take a short free address such as my-shop.simple-host.app for a site. It is live at once, with HTTPS and nothing to set up at a registrar, and the site's longer address redirects there.
Connect brand.com and www.brand.com answers too (or the other way round): the partner name redirects to the one you chose, on the same certificate.
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 three groups (People, Bots and Infra) and they are never added together into one misleading total. A fourth figure, Earlier, is history from before the split; nothing new ever lands there.
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.
For each site, the pages people read most and the sites whose links brought them, for the period you chose.
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.
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 two records to add (the address record and the TXT ownership record), then check the domain itself until it answers.
Pick your AI (ChatGPT, Claude, Grok or a coding agent) and it opens to the two or three steps that add Simple Host to it, with the address or command ready to copy.
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.
Add Simple Host to ChatGPT, Claude or Grok once, sign in, and the chat app can publish and manage your sites for you. Each connected app is listed with the device it was connected from (for example "Chrome on macOS") and when it was last used. In Claude, the Simple Host plugin adds the connector and the skills together in one step.
https://simple-host.app/mcp), or the plugin for Claude. Connected apps on your sites page lists them, with Disconnect.The same software runs on a server of your own, from one install command. The setup helper asks a few questions and writes the settings, and an optional check looks over the numbers you changed.
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.
Complete, browsable documentation of everything the service can do, for anyone integrating directly rather than through a skill.