What Simple Host is, and how its parts fit together
Simple Host puts websites online. Your own AI app or agent makes the site; Simple Host gives it an address, saved data, visitor sign-in, and the controls you need to run it.
This page is the map: every area of the product, the features inside each one, and where to read more. Simple Hack, which runs hackathons on simple-hack.app, is the same software run as its own product and has its own branch below.
The areas. Pick one to see the features inside it; open a feature for how it works, an example, which editions have it, and where to read more.
- Sites and deploy26Your AI app sends the finished site to Simple Host, which puts it online and keeps it there, with versions, a copy to download, and an undo for delete.
- Domains and addresses13Where a site answers: its own address from the first minute, a short free name, your own domain, or one wildcard for every site you own.
- Storage and saved data28Where a site keeps what visitors send and what the owner changes from chat, with rules for who may read, add, edit, and delete.
- Sign-in and access21How owners and visitors sign in, the keys an AI agent uses, and who may open a site.
- Notifications8A signed call to your receiver or your AI app the moment a visitor writes, and the emails Simple Host sends you.
- Agents and MCP18How an AI app or coding agent connects to Simple Host, what it may call, and what it is told while it works.
- Owner dashboard9The screens where you manage your sites yourself, and the screens your AI app can draw inside a chat.
- Showcase and home page4What opens at your handle's address: a public list of your sites you can pin, order, and caption, or one site you choose as home.
- Traffic and analytics17How many people read each site, counted on the server from the web log, with crawlers and the service's own monitoring kept apart.
- Admin and operations13What the operator can see and do, the rules every account and visitor meets, and how to run a copy of the software yourself.
- Simple Hack11Simple Hack runs hackathons from sign-up to results, team sites included. It is the same software run as its own product.A separate product on the same software
Sites and deploy
Back to the mapYour AI app sends the finished site to Simple Host, which puts it online and keeps it there, with versions, a copy to download, and an undo for delete.
Publish a page directlySend the page itself, the HTML and anything alongside it, and it is live in seconds with no build step or upload dialog.
Your AI app sends the files in one request. Text files go in files; images, fonts, and other binaries go base64-encoded in files_base64 in the same request. The site is live at its address as soon as the request returns. A site must include a home page.
Example. A consultant asks their chat app for a one-page rate card with a contact form; the app writes the page and publishes it in the same turn.
- Who
- Anyone with a finished page, and every AI agent publishing on your behalf.
- Where
- Whatever your AI does when you say "publish this".
- Limits
- Script files are refused. Each upload is capped by the per-upload size limit (see Publish a whole folder; Simple Hack allows 25 MB). A site must include a home page.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack team sites use the same route with a 25 MB upload limit.
Publish a whole folderHand over a zipped folder, the output of a normal web build with images and fonts, and the whole thing goes live at once.
A coding agent packages the folder as a tar.gz or zip and sends it in one upload. The upload becomes a new version and is live when it finishes. Shrink photos to about 1600 px wide, using WebP or JPEG at about 80% quality; phone photos are often 4 to 12 MB. Keep zip files, installers, and videos elsewhere and link to them.
Example. An agency builds a client's marketing site with a static site generator and has its agent publish the dist folder after each round of changes.
- Who
- Anyone with a real project rather than a single page: a built site, a portfolio, a documentation folder.
- Where
- No screen for it. Point your agent at the folder and it packages and sends it.
- Limits
- Up to 25 MB per upload. Operator exceptions apply. New websites from 5 October 2026 may use 200 MB including kept versions, and an account 1 GB; older sites have no total cap, and saved data and storage resources are counted separately. Script files are refused outright; anything that looks like a stored secret or a hidden settings file is silently left out without telling you. Remove files you no longer use and delete old sites you do not need.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack allows 25 MB per upload; a small box has no total cap unless its operator sets one.
Republish over the same sitePublishing again to the same name replaces what visitors see at once, at the same address.
Your AI app sends the new files to the same site name. The new version goes live immediately and the earlier version is kept, so you can go back to it. A republish replaces the whole site; to change a few files and leave the rest, see Change a few files.
Example. A restaurant updates its menu prices every month by telling its chat app what changed; the app republishes and the address stays the same.
- Who
- Anyone iterating, which is everyone, after the first day.
- Where
- Your AI does it when you ask for a change.
- Limits
- A republish replaces the whole site, it does not merge. Anything you leave out disappears from the live version, though the old version is still kept.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Change a few files of a siteSend only the files that changed and keep everything else live as it is, so a one-line fix does not resend the whole site.
Your AI app reads only the files it is about to change, then sends them with the instruction to keep the other live files. It can also name files to remove. The result is a new version with the rest of the site unchanged. The merge happens under the site's lock, so two edits never half-apply.
Example. A clinic changes its opening hours on one page of a twelve-page site; the agent sends that one file and the photos and other pages stay exactly as they were.
- Who
- Anyone making small edits to a site that already has many pages or photos.
- Where
- Ask your AI app. It uses
update_sitewithkeep_other_filesandremove_files. - Limits
- The same size and entry limits as a full publish apply to the merged result, and the site must still have a home page afterwards.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Publish from CI in one callOne call creates the site the first time and publishes a new version after that, so a build pipeline can publish on every push.
Create a Deploy only key and save it as the pipeline's secret. The pipeline sends the built folder with the create flag set; if the site does not exist yet it is created, otherwise a new version goes live. A plain create of a name that already exists is refused with a message naming the right call. GitHub Actions and the like work this way on every push.
Example. A product team keeps its documentation in a repository; every merge to main rebuilds the docs and publishes them to the same address.
- Who
- Anyone whose site lives in a repository with a build step.
- Where
- No screen. Create a Deploy only key in the Keys panel, save it as the pipeline's secret, and your agent writes the workflow.
- Limits
- A deploy key can create, update, roll back, and list sites, and nothing else. It cannot set the versions kept or the passcode. A deploy key can publish code that runs when you open your own site; treat it like the site itself.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise spells the create flag ?create=true where simple-host.app uses ?create=1.
Upload link for a big archiveWhen a site is too large to send inline, your agent gets a one-time link and uploads the tar.gz or zip to it from a shell.
The agent asks for an upload link for the site, then uploads the archive to it. The link creates the site or publishes a new version, works once, for one site, for 15 minutes, and checks your sign-in again at upload time. The upload meets the usual size, scope, and storage checks.
Example. A developer's coding agent builds a photographer's portfolio with 60 MB of images and uploads the archive through the link instead of pasting files into the chat.
- Who
- Coding agents with a shell publishing a built site with many images or fonts.
- Where
- Ask your AI app. It calls
create_upload_linkwitharchive: true. - Limits
- 15 minutes, one use, one site. At most 20 live links per account. Links stop working when you sign out, disconnect the app, or your sign-in expires. Never share the link or put it in a page.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
On Simple Hack the upload link is the default form of create_upload_link; Enterprise does not have upload links.
You choose the site nameThe name you pick becomes the last part of the address, so it is worth choosing something readable.
Your AI app asks for a name or picks one when it publishes. The name must be free on your account and is checked against a reserved list. You can rename the site later without republishing it.
Example. A bakery asks for menu rather than site-2, so its address reads as the menu it is.
- Who
- Anyone publishing anything.
- Where
- Your AI asks or picks one when it publishes; ask it for a different one any time.
- Limits
- Lower-case letters, numbers, and dashes only. Reserved names are refused. You can rename it later (Rename under Manage on your sites page); see Rename a site for what happens to the old name.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Pages only: nothing runs on the serverWhat you publish is served back exactly as it is; your scripts run in the visitor's browser and nothing you upload executes on the server.
Simple Host serves your files as static pages. Your page's own JavaScript runs in the visitor's browser as normal. Forms, bookings, and saved entries work through the site's saved data and storage, which the pages call from the browser.
Example. A startup's pitch page with a waitlist form runs entirely in the browser and saves entries to the site's storage; there is no server code to maintain.
- Who
- Everyone: it is why an AI-written site is safe to host here without review.
- Where
- Not a setting. It is how publishing works.
- Limits
- No server-side languages, no databases you install, no background jobs. If your idea needs a server that runs your code, this is not the right home for it.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Up to a hundred sitesOne account can hold up to a hundred separate sites, so experiments do not need a second account.
Every site you create counts toward the cap, including sites in Recently deleted until they are purged, so a restore never needs a check. The connector reports your cap, and your AI app can tell you how many sites you have.
Example. A freelancer keeps a separate site per client proposal and still has room for their own portfolio and tools.
- Who
- Anyone who builds a lot of small things.
- Where
- No screen shows your count against the limit; you find out when publishing is refused, or ask your AI app.
- Limits
- 100 sites on simple-host.app. Sites in Recently deleted count until they are purged. Delete something to make room.
- Simple Hostyes
- Simple Hackpartly
- Enterprisepartly
- Small boxpartly
The 100-site figure is simple-host.app's; Enterprise and self-hosted instances set their own site quota, and Enterprise also caps stored bytes per owner.
Website file allowancesA new site may use 200 MB including its kept versions, an account 1 GB, and a refused publish leaves the live site untouched.
Three limits apply to website files. Each upload may be at most 25 MB. A website created on or after 5 October 2026 may use 200 MB in total for its live files and all kept versions. An account may use 1 GB for all its website files and kept versions, including sites in Recently deleted until they are purged. The check runs before anything is written, using the size after old versions are pruned, so a refused publish changes nothing. Your sites page and your AI app show the same usage figures and the same tips.
Example. A real-estate agent publishing listing photos keeps them at about 1600 px wide and 80% quality, so twenty listings fit comfortably under the site's 200 MB.
- Who
- Anyone publishing photo-heavy pages, and anyone whose publish was refused for size.
- Where
- Usage and tips appear on your sites page and in your AI app's replies; a refused publish says which limit it hit, the current size, and what to do.
- Limits
- Sites created before 5 October 2026 have no total cap. Saved data and KV, SQLite, and file storage have their own limits and do not count toward either file cap. For personal photos use Add photos, which makes small copies on your device. Keep zip files, installers, and videos elsewhere and link to them. Remove files you no longer use and delete old sites you do not need. Operator exceptions apply to a few accounts.
- Simple Hostyes
- Simple Hackpartly
- Enterprisepartly
- Small boxpartly
Simple Hack keeps its own 25 MB upload limit and 2 versions; Enterprise caps stored bytes per owner instead; a small box has no site or account total unless its operator sets one.
See all your sitesOne list of everything you have published, with its address, its current version number, when it was last deployed, and whether it is live.
Your sites page lists every site as a card with Open and a Manage menu. Each card shows the live address, the version number, and the last deploy. Taken-down or offline sites say so. Your AI app gets the same list, newest edited first, with each site's file size.
Example. An agency with thirty client sites opens one page to see which were deployed this week and which still carry last month's version.
- Who
- Anyone with more than one site.
- Where
- Your sites page, with every button. The main dashboard lists the same sites with a Manage link back there.
- Limits
- Your own sites only. A search box appears once you have 10 or more sites; see Find sites by description.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Find sites by descriptionSearch your own sites by words from their pages or by date, so "the one with the pricing table" turns up without knowing its name.
At each deploy Simple Host captures a short summary of the home page: its title, meta description, first headings, and up to 300 bytes of text. Your AI app's site list and the search box on your sites page match words against that summary and the name, and can filter by created or updated date, order by name or date, and page through results.
Example. A consultant asks "open my site about the Lisbon workshop" and the app finds it by the heading on its home page.
- Who
- Anyone with enough sites that names alone stop helping, and every AI app asked to find "my site about X".
- Where
- The search box on your sites page (shown from 10 sites), or ask your AI app.
- Limits
- Plain word matching on the home page's summary, your own sites only. The summary is taken from the home page, so words that appear only on other pages are not matched.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Your 4 latest versionsSimple Host keeps your live version and 3 to roll back to, numbered and dated, and an older live version always stays.
Every publish makes a new numbered version with a timestamp. The newest 4 are kept, counting versions stored but not yet live; the live version is never pruned even when it is older. The version list shows the newest three and the live one, with Show all for the rest. The operator decides who can change the count; on simple-host.app the count is fixed, and asking for a different one answers "Simple Host keeps your 4 latest versions".
Example. A product team publishes a landing-page redesign on Monday and still has Friday's version to compare against.
- Who
- Anyone who has ever published something worse than what they had.
- Where
- Versions under Manage on your sites page, or ask your AI app.
- Limits
- Versions carry a number and a timestamp only; there is no note or label on them. Kept versions count toward the site's and the account's file allowance. Deploy-only keys cannot change the count.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack keeps 2 versions, Enterprise keeps 5, and a small box keeps every version unless its operator sets a count, which anyone there may also set per site.
Put an earlier version backPick any kept version and make it the live one again; the switch is immediate.
Choose a version in the list and make it live. Visitors see it at once at the same address. A version stored for preview but never published is made live the same way.
Example. A shop's agent publishes a new checkout page that hides the Buy button; the owner puts yesterday's version back while the fix is made.
- Who
- Anyone who broke a live page a minute ago and wants it back now.
- Where
- Make live in the version list under Versions, or ask your AI app.
- Limits
- This changes the pages only. Data your visitors saved is not rolled back: it is not part of a version. Only kept versions can be put back.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Look before it goes liveStore a change without publishing it, then open a preview link that shows that version exactly as visitors would see it.
Ask your AI app to publish without making it live. The version is stored and you get a preview link. Any kept version, live or not, can be previewed the same way from the version list. The preview is served on the site's own address, is hidden from search engines, and refuses saves. When you are happy, Make live switches visitors to it.
Example. A law firm's agent redesigns the home page; the partners open the preview link, ask for two changes, and only then make it live.
- Who
- Anyone whose agent is about to redesign a site people are already using.
- Where
- Preview and Make live in the version list under Versions, or ask your AI app.
- Limits
- A preview link is yours for one hour, and anyone who has it can open it in that hour. Nothing you do in a preview is saved, so forms there do not submit. A site with no address of its own yet cannot mint a preview link.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise preview links open only for the owner or a team member.
Drafts as versionsKeep several unpublished drafts of one site, each marked with who made it, and discard the ones you will not use.
Publish without making it live, and name the author with the deploy. The version list shows who made each draft and can show only the drafts that have never been live. Make the chosen one live from the list; discard the others and they are gone for good. Versions that have been live are kept by the normal retention rule and cannot be discarded by hand.
Example. A travel agency keeps one site per quote. Two staff each store a draft of the itinerary; the manager previews both, makes one live, and discards the other.
- Who
- Anyone whose agent prepares a few versions of a page before one is chosen: a quote, a proposal, a redesign.
- Where
- Versions under Manage on your sites page (the author beside each draft, Discard on drafts not live yet), or ask your AI app.
- Limits
- An author name is at most 80 characters. Discarding is final and applies only to versions that were never live; a deploy-only key or a Simple Hack team key cannot discard.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
On Simple Hack the version list and authors work the same way; team keys cannot discard.
Rename a siteGive a site a new name without republishing it; its versions and its saved data come with it.
Choose Rename and type the new name, or ask your AI app. The site keeps its versions, saved data, and storage. Its address changes with the name.
Example. A founder published a pitch as draft-3, closed the round, and renamed it investors before sending the link out.
- Who
- Anyone who picked a throwaway name and then kept the site.
- Where
- Rename under Manage on your sites page, or ask your AI app.
- Limits
- The new name must be free and follow the same rules as a new site's name. The old name keeps forwarding to the new address until you create a new site with the old name, which then takes it.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Delete a siteTakes the site offline at once, with every version and its saved visitor data, and keeps it in Recently deleted for 7 days.
Choose Delete and a dialog names what goes with it: how many list entries and whether saved data are included. The site goes offline immediately and moves to Recently deleted, which keeps it for 7 days; Restore brings it back whole. Download is in the same menu if you want a copy first.
Example. An agency closes a finished campaign site after taking a download for the client's records.
- Who
- Anyone clearing out experiments.
- Where
- Delete under Manage on your sites page, or ask your AI app.
- Limits
- After 7 days it is gone for good, saved data included. Until then its name stays yours and the site still counts toward your site quota and file allowance. A site taken down by the operator cannot be deleted until the operator acts. Deleting your whole account is immediate.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise keeps a deleted site for 30 days.
Recently deletedA deleted site stays in Recently deleted for 7 days, and Restore brings it back exactly as it was, name and data included.
Recently deleted on your sites page lists every site deleted in the last 7 days. Restore puts it back whole: its name, versions, saved data, lists, and any claimed name. Your AI app can list and restore them too. After 7 days it is removed for good by an hourly sweep.
Example. A consultant deletes a client portal by mistake on Friday and restores it on Monday with every entry still there.
- Who
- Anyone who deleted the wrong one.
- Where
- Recently deleted on your sites page, or ask your AI app.
- Limits
- After 7 days it is gone for good. A site in Recently deleted still counts toward your site quota and file allowance. Its old name does not forward while it is deleted.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise keeps deleted sites for 30 days, and a team member or admin may restore as well as the owner.
Take a site offlineEvery address of the site shows "This site is offline" and visitors can no longer save anything, while nothing is deleted.
Choose Take offline, or ask your AI app. Every address answers a plain "This site is offline" page, visitor saves and visitor sign-in are refused, and the site leaves your public showcase. Its pages, versions, and saved data stay exactly as they are. Put back online reverses it whenever you like.
Example. A conference closes its speaker application form the day the deadline passes and puts the site back online with the programme a week later.
- Who
- Anyone whose event is over, or whose form must stop taking entries today.
- Where
- Take offline and Put back online under Manage on your sites page, or ask your AI app.
- Limits
- It is offline for everyone at once. You and your agent can still update it and read its data while it is offline. The offline page is hidden from search engines. An operator take-down overrides the switch.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise has no offline switch; its only-me access level does the same job, with visitors seeing the sign-in gate and the owner still opening the site.
Download a siteOne file with every page of the live version, the site's saved data, and everything its lists hold, to keep or take elsewhere.
Choose Download on your sites page and a .tar.gz archive is prepared with the live files, the saved data, and the list entries with their ids, dates, and who submitted them. Your AI app gets a 10-minute download link to the same archive.
Example. A client ends an engagement and the agency hands over the download, pages and form entries together, so nothing is lost when the site is deleted.
- Who
- Anyone about to delete a site, make a big change, or leave.
- Where
- Download under Manage on your sites page, or ask your AI app.
- Limits
- A
.tar.gzarchive, 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 download link from your AI app expires after 10 minutes and stops working if the site is deleted or renamed in between.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
The Enterprise archive is a zip that also carries versions and uploaded files, through a single-use link.
List on my profileOn shows the site on your profile page; off leaves it off. New sites start off.
Turn List on my profile on to show the site on your profile page, or off to remove it. Every open site can be found by search engines.
Example. A designer shows finished portfolio pieces on their profile page.
- Who
- Anyone choosing which projects to show on their profile page.
- Where
- List on my profile under Manage on your sites page, or ask your AI app.
- Limits
- To keep a site out of search engines, use a passcode or named viewers, take it offline, or ship your own robots.txt / noindex.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise keeps its access levels; listed means internal company directory and search discovery.
A proper "page not found"A mistyped address on a site gets a clean, branded page with a way back, instead of a raw server error.
When a visitor asks for a page the site does not have, the web server hands the request to Simple Host, which answers a branded not-found page in the site's theme with a link back. The old name of a renamed site forwards instead of showing it.
Example. A customer follows a stale link to a product page that was renamed and lands on a clear page with a way back to the shop.
- Who
- Your visitors, on their worst moment.
- Where
- Automatic. Nothing to switch on.
- Limits
- You cannot customise it or point it at your own page.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Move a WordPress siteUpload the export of a WordPress site you own and Simple Host turns it into static pages at the same permalinks, with photos and menus.
Ask your AI app to start a WordPress import for a site name. It gives you a one-time page where you upload the export: the WXR .xml file, WordPress.com's .zip of XML files, and the media library as a .tar, .zip, or .tar.gz of wp-content/uploads. Conversion runs without AI and publishes through the normal deploy path, as a new site or a new version. Pages and posts land at their permalinks with category and tag archives, the menu, photos shrunk to 1600 px, galleries, YouTube and Vimeo embeds, approved comments as text, a search page, a sitemap, and a 404.html, in the built-in look or the old theme's stylesheets. A Squarespace export is recognised too, with its photos copied while the old site is still live. Afterwards your AI app reads the import report, which names the exact storage setup for each dynamic part: contact and subscribe forms become an inbox, comments and guestbooks become a comments preset, a forum becomes a wall.
Example. A yoga studio moves its 40-post WordPress blog with class schedule and contact form; the posts keep their addresses and the form keeps taking messages into the owner's inbox.
- Who
- Someone moving a WordPress or Squarespace site they own, with only a chat app.
- Where
- Ask your AI app. It calls
create_import_link, hands you the upload page, then readsget_import_report. - Limits
- Only public items are written: drafts, scheduled, pending, private, and password-protected pages and posts are left out, and the report counts the password-protected ones. Page-builder layouts (Elementor, Divi, WPBakery, Beaver Builder, and others) do not carry over; the report names those pages, forms whose fields were not in the export, and galleries it could not rebuild. Shops stay as pages with a Buy button only when you map products to payment links; cart, checkout, and account pages are left out. Donation forms are not supported. Photos missing from the upload are fetched only from the export's own hosts, WordPress.com's media hosts, or Squarespace's image servers. The upload page lasts 30 minutes, at most 20 import links per account, one conversion runs at a time, the report is kept 24 hours, and the usual site size caps apply.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
WordPress import is a simple-host.app feature; Simple Hack team sites are new builds and Enterprise does not have it.
Idle-site cleanup Off by defaultA site unvisited and unchanged for 90 days gets its owner a Keep link by email; 30 days later with nothing done it is deleted.
When the operator turns it on, a site with no visit by a person, no new version, no saved-data or list write, and no other change by its owner for 90 days gets its owner an email with a Keep it link and a link to their page. Keep it resets the clock without signing in. 30 days later with nothing done, the site moves to Recently deleted and a second email carries a Restore it link. The links open a confirmation page and act only on its button, so mail scanners change nothing. Any restore ends the idle state. Keep for good on your sites page, or keep_site from your AI app, marks a site the cleanup never touches.
Example. A developer's three test sites from a hackathon weekend are warned at 90 days; they keep the one they still show to clients and let the others go.
- Who
- Operators keeping disk for sites people use, and owners with forgotten experiments.
- Where
- Keep for good under Manage on your sites page, the idle warning with its date on the site's card, or ask your AI app.
- Limits
- Off by default; the operator turns it on. Sites with a custom domain or claimed name, kept sites, taken-down or offline sites, suspended accounts, preview sites, and admin, event, and reviewer accounts are never warned or removed. At most 50 emails go out per run, removals first. Nothing runs with under 90 days of visit records. All of an account's links stop working when its sign-in email changes.
- Simple Hostyes
- Simple Hackno
- Enterpriseyes
- Small boxyes
Simple Hack team sites are removed 30 days after an event is archived, with one warning 14 days before; Enterprise sets the idle period itself and shows a Not used lately card instead of emailing only.
Redirects and plain addressesKeep old links working when pages move.
Publish a root _redirects file with paths, splats, placeholders and query rules. Rules run after access gates; existing content wins unless forced.
Example. /old/* /articles/:splat 301 sends old blog links to their new pages.
- Who
- Anyone moving or reorganising a site.
- Where
- The root _redirects file sent with your site.
- Limits
- 1000 rules by default; 128 KiB file; 2048 bytes per line. Supports 301, 302, 404 and 410.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise port pending.
Domains and addresses
Back to the mapWhere a site answers: its own address from the first minute, a short free name, your own domain, or one wildcard for every site you own.
Every site gets a public addressThe moment a site exists it has a working web address you can send to anyone, with HTTPS already on.
Every site gets its own address, https://<site>.<handle>.simple-host.app/. Files are served at the root, and visitor sign-in, per-person saves, and private collections are bound to that host, so a sign-in covers that one site. On a brand-new account the address 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.
Example. A consultancy publishes a client proposal and sends the link the same hour; the client opens it over HTTPS with nothing to set up.
- Who
- Everyone. This is the point of the service.
- Where
- Under each site's name on your sites page, with its live version and when it was last deployed. A site with its own live domain shows that domain.
- Limits
- simple-host.app is the only address served and handed out by the hosted service; pages, API examples, connector text, and skills all use
.app. Old links on another base redirect to the matching.appaddress with path and query kept. A site's/v1/path is reserved for the API of that one site.
- Simple Hostyes
- Simple Hackpartly
- Enterpriseyes
- Small boxpartly
Simple Hack team sites live on the event's hosts; a small box without per-site hosts serves every site by path on one shared address.
Your handle is an address tooYour handle has its own host, https://<handle>.simple-host.app/, which lists your public sites or opens the site you chose as home.
Every handle is a host. By default https://<handle>.simple-host.app/ shows your public showcase. You can pick one of your sites as your home page instead (see Showcase and home page). On a brand-new account, until your certificate is ready, your sites are reached beneath it as <handle>.simple-host.app/<site>/; once it is ready those paths forward to each site's own address.
Example. A freelance designer prints https://meera.simple-host.app/ on a business card; it lists her live portfolio, a pricing page, and a client demo.
- Who
- Anyone who wants one link for all their work, or a short address to put on a card.
- Where
- Shown on your sites page under Your address. Your AI app reports it as your person page.
- Limits
- Only public sites are listed. A renamed handle keeps the old one forwarding to the new one. Handles that read as Simple Host or a sensitive function are reserved.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxpartly
Enterprise has an owner index page that needs company sign-in; a small box without per-site hosts serves the person page by path; Simple Hack has no personal sites.
Your own address is on its wayEach person gets a certificate for *.<handle>.simple-host.app on their first site, and the service tells you while it is still queued.
The certificate is requested automatically when you publish your first site and is usually ready within about 10 minutes. Until then your sites keep the <handle>.simple-host.app/<site>/ form, and every address handed out is whichever one is live. While it is not ready, your sites page shows a note at the top, and your AI app sees the state too: waiting (queued, with a rough time from the queue) or failing (retried after the issuer's six-hour wait). When the address switches, the note also says that visitors' sign-ins and anything a page kept in the visitor's browser start fresh on the new address.
Example. A new account publishes a landing page for a product launch at 9:00 and shares the path-form link; by 9:10 the site answers at its own address and the old link forwards.
- Who
- New accounts in their first minutes, and anyone wondering why a site still shows the path form of its address.
- Where
- A note at the top of your sites page while it is on its way; each site's card shows the address that currently works.
- Limits
- Brand-new accounts may queue behind the issuer's weekly and daily caps, and the note shows what was issued in the last week against those caps. A request that stays unready is retried on its own; nothing for you to press. Browser-kept data and sign-ins do not carry over to the new address.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxno
Enterprise issues per-owner certificates inside the cluster and shows the waiting state to admins only; a small box uses one shared address and needs no per-person certificate.
Old addresses still workLinks in the older address styles forward to the site's own address, so anything you already shared keeps opening.
Old <handle>.simple-host.app/<site>/ and sites.simple-host.app/<handle>/<site>/ links redirect to the site's own address, with the path and query kept. A renamed site's old name keeps redirecting on all three forms until a new site takes that name. A free name a site let go stays with it and redirects to its current address, or says "This site was removed" once the site is gone.
Example. A bakery's menu link printed on flyers last spring as sites.simple-host.app/anna/menu/ still lands on the menu at its current address.
- Who
- Anyone who published before the address format changed.
- Where
- Nothing to do: the old link forwards on its own.
- Limits
- Visitors land on the new address, so that is what they will see in the address bar and copy from then on. What a page kept in the visitor's browser starts fresh there; what the site saved on the server moves with it.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
The older address forms existed on simple-host.app only; a renamed site's old name redirects on every edition.
A free <name>.simple-host.appTake a short free address such as my-shop.simple-host.app for a site; it is live at once, with HTTPS and no registrar.
Pick a name and it is verified at once, first come first served. The site's longer address redirects to it, and sign-in and saved data move with it. If you later switch names, disconnect, or delete the site, the old name stays with that site and keeps redirecting to its current address.
Example. A yoga studio takes riverside-yoga.simple-host.app for its class schedule and reads it out at the end of each class.
- Who
- Anyone who wants a short link to print or say out loud.
- Where
- Domain under Manage on your sites page, or ask your AI app.
- Limits
- One name per site, first come first served. Lower-case letters, numbers, and dashes. Names that read as Simple Host or a sensitive function (support, admin, billing, login, and similar) are reserved. A released name cannot be taken by another site; it stays with the site that had it.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
Hosted Simple Host only. Simple Hack team sites live on the event's hosts, and Enterprise keeps the person's name in every address on purpose.
Point your own domain at a siteAttach a domain you own, a subdomain or the bare domain, to one site; it is then served only there and its old address redirects.
Attach a domain you own, a subdomain like recipes.yourbrand.com or the bare domain itself, to one of your sites. You add two DNS records at your registrar; the service checks them about every two minutes and requests the certificate on its own once both are seen. 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. Connecting a new domain to a site that already has one keeps the current address serving until the new one is live with its certificate; then the old one redirects.
Example. An architecture practice connects studio.hallam.co to its project showcase, so nothing in the address mentions a hosting service.
- Who
- Anyone with a brand, a business or a domain already bought.
- Where
- Connect domain under Manage on your sites page. Your agent can also do it, and there is a skill for exactly this.
- Limits
- One domain per site. A binding is provisional until its TXT ownership record proves it: another site can take an unproven one over, and it lapses after 24 hours if DNS never pointed here (7 days in any case). A proven domain is exclusive (
409 domain_taken). A name another site on this server already serves cannot be connected. Each account may ask for at most 5 new domain certificates a day; the sixth waits. Sites that are taken down, and suspended accounts, get no domain checks.simple-hack.appand the service's own zones cannot be connected.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Enterprise has no custom domains by decision; Simple Hack team sites live on the event's hosts; on a small box the server's own web front issues a connected domain's certificate on demand.
You are told the exact records to addConnecting hands back the two DNS records for your registrar: one that points the domain here and a TXT record that proves it is yours.
Connecting returns both records: a CNAME for a subdomain or an A record for a bare domain, and a TXT record at _simple-host.<your domain> holding the site's token. Keep the TXT record in place; the domain counts as verified only while it matches and the site answers over HTTPS. Your agent can repeat the records any time, and Check again re-proves them on the spot.
Example. The site is built by a marketing lead, but the domain lives with the company's IT person; the lead forwards the two records and IT pastes them in.
- Who
- Whoever has the login to the domain registrar; often not the person building the site.
- Where
- Shown when you connect, and repeatable by your agent afterwards.
- Limits
- Adding it at the registrar is yours to do, and changes can take from minutes to a few hours to spread. Domains verified before 27 September 2026 keep working without the TXT record while they stay verified. Check again allows 3 checks at once per account, then one every 30 seconds.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Follows custom domains: hosted Simple Host, and a small box that answers connected domains.
HTTPS on your domainA connected domain is served over HTTPS with a valid certificate, requested on its own once your records are in place.
The certificate is issued automatically once your domain points here and its ownership record (a TXT record at _simple-host.<your domain>) is in place, usually within minutes. The issuer re-checks the TXT record and that the domain still points at your site before issuing. Until then your site keeps its current address. www and the bare domain can both work on one certificate.
Example. A law firm moves its client intake page to intake.marsh-law.com; the padlock is there before anyone is sent the link.
- Who
- Everyone: a browser warning on your own domain is worse than no domain.
- Where
- Nothing to press.
- Limits
- At most 5 new domain certificates per account per day; the sixth waits and the status says so. A failed request is retried after 6 hours; DNS and TXT problems are retried after 15 minutes. A domain that points here but never proves itself is released after 7 days, and the site's earlier address comes back.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Follows custom domains: on a small box the server's own web front issues the certificate on demand.
The connection badgeYour sites page shows the domain you attached with its status, the records still to add, the last check's result, and Check again.
Until the domain is live, Domain shows the two DNS records to add, what the last check found, when an unproven connection lapses, the certificate's state, and Check again. For www and the bare domain it also shows the partner's record and whether it was set up. Your agent reads the same status.
Example. A shop owner adds the records on Friday evening, sees pending with "TXT record not found", fixes a typo, presses Check again, and sees active.
- Who
- Anyone checking whether the connection worked.
- Where
- Next to the site's name on your sites page, and under Domain.
- Limits
- Re-checked about every two minutes: pending until the domain resolves here and answers over HTTPS, then active (or error, with the reason). An active verdict is re-proved every hour. Opening the domain is still the surest test.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Follows custom domains.
A domain that stops pointing here is let goA connected domain that keeps failing its checks is emailed about and then disconnected, so the site's own address serves again.
If it fails every check for a day, the owner is emailed with the last error. After three days the domain is disconnected and released completely: the binding, the server entry, and the certificate go, the site's own <site>.<handle>.simple-host.app address serves again, and the domain can be connected afresh with the TXT proof. The earlier address kept while a new domain is pending is checked the same way and let go after three days of failing.
Example. An agency hands a client site back and the client repoints the domain to another host; three days later the site is back on its Simple Host address and the agency's dashboard shows no domain.
- Who
- Anyone who let a domain expire, moved DNS elsewhere, or inherited a site whose domain no longer points here.
- Where
- The email arrives at your account address; the Domain panel shows the last error and when the domain will be released.
- Limits
- While the issuer is still letting go of a released domain, connecting it again answers "domain releasing"; try again shortly. A free name the site lets go is not released; it stays with the site and redirects.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Follows custom domains.
Disconnect a domainDetaches the domain and stops serving your site from it, so the site's own address serves again and the domain is free for another site.
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. Your agent confirms with you first, then removes exactly the domain you name.
Example. A product team retires beta.acme.dev after launch and connects the same domain to the new docs site.
- Who
- Anyone moving a domain to a different site, or retiring one.
- Where
- Disconnect under Domain in the site's Manage menu on your sites page.
- Limits
- The DNS records at your registrar (address and TXT) are not removed: take them out yourself, or the domain will point at nothing. Disconnecting drops only the domain named; if the site's domain changed in the meantime the request is refused and you are told.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Follows custom domains.
www and the bare domain togetherConnect brand.com and www.brand.com answers too (or the other way round); the partner redirects to the name you chose, on one certificate.
Connecting brand.com or www.brand.com also sets up the other name as a redirect-only host: a permanent redirect to the chosen name, both on one certificate. The TXT record on the chosen name covers both; the answer adds the partner's record (an A record for a bare domain, a CNAME for www). If the partner is not ready when the chosen name goes live, the chosen name goes live alone and the status says why; the service asks again, at most every 6 hours, once the partner points here.
Example. A restaurant connects osteria-lina.com; guests who type www.osteria-lina.com from an old menu land on the same page.
- Who
- Anyone whose visitors type the domain either way.
- Where
- Offered when you connect a domain; the records to add are shown with the rest.
- Limits
- The partner only redirects; it never serves a second copy of the site. It is set up only if it points here, nothing else on this server answers it, and it is not connected to a site of its own. A partner that another site has bound, in any account, is neither offered nor asked for. A partner that later becomes a site of its own is taken off the redirect first.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Follows custom domains.
One wildcard for every site you ownConnect *.<suffix> once and every site of your account answers at <label>.<suffix>, including sites you make later.
Connect *.trips.example.com once, with a wildcard DNS record and a TXT record at _simple-host.<suffix>. Every site named <label> then answers at <label>.trips.example.com, with no per-site step. An optional site prefix maps voucher-meera to meera.voucher.example.com. By default the family address becomes each site's main address: the site's own address and old links redirect there, and sign-in, saved data, private lists, analytics, the report form, passcodes, offline, rename, delete, and restore all work there as on a custom domain. A site with its own custom domain or free name keeps that as its main address; the same account may put a custom domain under its own family.
Example. A travel agency connects *.quotes.chhotabreak.com once; every new quote site it publishes is live at <client>.quotes.chhotabreak.com the moment it exists.
- Who
- Agencies and businesses that make many sites under one brand: a quote per client, a page per property, a portal per customer.
- Where
- Ask your AI app to connect
*.<suffix>(the connect-a-domain skill covers it), or your sites page. - Limits
- The family answers site labels only; the bare suffix itself is not routed to your home page or showcase, and the wildcard certificate does not cover the apex. Nothing is served until both records are seen; a pending family is dropped after 24 hours. Several accounts may wait on one name; the first to prove it wins and the others are emailed. A verified family is exclusive: no other account can connect it, an overlapping family, or a custom domain under it. The label
wwwnever names a site. The wildcard certificate is set up by the operator; until then the status says waiting for the operator. If it fails every check for a day, the account is emailed. After three days the domain is disconnected and must be connected again with the TXT record.simple-hack.appand the service's own zones are refused as suffixes.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
Hosted Simple Host only; Enterprise has no custom domains by decision, and Simple Hack team sites live on the event's hosts.
Storage and saved data
Back to the mapWhere a site keeps what visitors send and what the owner changes from chat, with rules for who may read, add, edit, and delete.
Three kinds of site storageEvery site gets key-value namespaces, its own SQLite database, and file buckets, so pages can save and read without a server.
The owner's AI app creates a storage resource on the site and gives it a name: a key-value namespace for settings and small documents, a SQLite database with tables for records, or a file bucket for uploads. SQLite/KV use row rules and file buckets use presets to say who may read, add, edit, and delete. Pages on the site read and write through auth.js; the owner's app reads and writes everything through the connector. The three kinds are opt-in and start owner-only, and a resource can inherit the site's passcode. Saves can also tell the owner's agent through a webhook, covered under Notifications.
Example. A restaurant keeps its menu and prices in a public key-value namespace, so the owner says "raise the lunch special to 14" in chat and the page shows it on the next load.
- Who
- Anyone whose site takes bookings, orders, form entries, uploads, or content the owner changes from chat.
- Where
- Ask your AI app. The Storage panel beneath each site on your sites page lists every resource, its policy, and how much space it uses.
- Limits
- KV and SQLite share 10,000,000 bytes per site and files have a separate 10,000,000 bytes, with 1,000,000 bytes per upload. Visitors never send SQL. Deployed website files are counted separately.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack team sites and event websites use the same three kinds under one 1,000,000-byte pool; Enterprise runs them on its own engine, where tables are declared columns stored as Postgres rows and there is no per-site SQL.
Row rules and file-bucket accessSQLite and key-value data use rules for who may read and change each row. File buckets keep presets.
Policies name read, add, edit, delete or all. Permissive policies combine with OR; restrictive policies narrow them with AND. Without an applicable permissive policy, access is denied. A table may replace its resource default with its own set. Use visitor_id == auth.id or owner for personal reads; sign-in alone shares rows. Owner tools retain their SQL console; pages use fixed row routes. File buckets retain presets such as wall for shared photos and records for author-only reads.
Example. A tutor keeps requests readable only by the owner and homework readable only by its author or owner. Each table has its own rules.
- Who
- Anyone deciding what visitors may see and change on a site: a form only the owner reads, records each person sees alone, a wall anyone reads.
- Where
- Your AI app saves rules with storage_set_resource. The Storage panel shows the policies and lets the owner edit their JSON; file buckets keep their preset control.
- Limits
- Edit and delete require identity guards and read visibility of the stored row. A failed check rolls back. Existing SQLite/KV presets work until the announced switch. A UNIQUE conflict can reveal a hidden row; KV add attempts can reveal an existing key.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack supplies trusted team, organiser, stage and deadline facts; its own gates still apply. Self-hosted servers may still have accepting new rules off; follow their tool descriptions.
Pages read and write table rows without SQLA page lists, adds, edits, and deletes rows through fixed routes the server builds, so a visitor can never run a query of their own.
A page asks for rows with up to three equality filters plus an order, a direction, a limit, and a cursor for the next page. It adds a row by sending column values. The server validates the table and columns against the real schema, assigns row IDs, refuses caller-supplied primary keys, and stamps visitor identity and timestamps. Edits and deletes require stored-row read visibility and the operation rules; hidden and missing rows answer identically. Visitors see a mine mark on each entry instead of other people's ids. A linked row must point at a parent the visitor may read, and a change that would write another table through a trigger or cascade is refused. Owner tools still run full SQL, within a time limit.
Example. A clinic's booking page lists appointments where the status is open, ordered by date, and shows each patient only their own rows.
- Who
- Anyone whose site shows records to visitors: orders, bookings, requests, entries in a directory.
- Where
- Your page's own code through
auth.js. Your AI app runs the owner's queries and schema changes. - Limits
- 100 rows per page by default, at most 500. At most 100 columns on a visitor route. Use
id INTEGER PRIMARY KEYso the server assigns ids. A duplicate in a unique column answers a generic conflict, so use opaque ids rather than emails as unique keys. Visitor queries stop after 1 second and visitor writes after 2 seconds; owner operations get 5 seconds.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise builds the same row routes over declared tables on Postgres.
The owner on their own siteSign in on your own site as a visitor and you get owner rights over its storage data, so an admin page on the site works without a key.
When the site's owner signs in through visitor sign-in on one of the site's own addresses (the site host, a family address, or its own domain), the storage routes treat them as the owner: SQLite/KV rules receive auth.role == owner and grant only what those rules allow; file buckets retain their preset rights. The admin recipe is an owner page that lists all orders and sets a status. Settings, deploys, domains, passcodes, named viewers, keys, versions, and deleting the site stay with the owner's key or connector. A page the owner opens while signed in refuses to be framed by another site, and a framed page or a preview of an earlier version never gets owner rights.
Example. A florist opens /admin on her own shop site, signs in with her usual email code, and marks today's orders as delivered.
- Who
- Owners who want to confirm bookings, set an order's status, or approve posts from a page on the site rather than from chat.
- Where
- Sign in on the site itself. Ask your AI app for the
adminrecipe to add the page. - Limits
- Owner-on-site rights cover storage data only, under the saved rules or file-bucket preset; they do not apply on the person address or in framed pages and previews.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
On Simple Hack an approved team member signed in on the team site has these rights while the team may still change it, and an organiser on the event website until the event ends; on Enterprise the owner or a team member signed in on the site's own host has them.
Page recipes for everyday jobsReady pages with their storage setup for booking, forms, menus, client portals, records, an admin page, a gallery, and comments.
Each recipe holds the owner setup (which resource to create, with which row rules or file-bucket preset) and a complete page. Topics: booking (a customer signs in when they book and sees their bookings and status; also reservation, appointment, quote, waitlist, contact, and menu), inbox (a form only the owner reads, sent without sign-in), public (a menu the owner keeps), portal (a private page per client opened to that client's email), records (each person's records: a cart, sign-in at checkout, my orders, the owner's view), admin (an owner page listing all orders with a status), gallery (visitors upload photos everyone sees), wall, board, personal, private, and comments (anyone posts after a spam check). Every recipe uses visitor sign-in and a storage resource; none uses an API key. The connector also warns when a new page uses saved data without auth.js or names a resource the site lacks.
Example. A hair salon asks for a booking page; the AI app follows the booking recipe, so each client sees their own appointments and the owner confirms them from chat.
- Who
- Anyone asking their AI app for a working business page rather than a mock-up, and the AI app itself.
- Where
- Ask your AI app, or read any recipe at
simple-host.app/recipes/<topic>. - Limits
- Recipes are starting points; the AI app adapts the page. The
commentsrecipe is offered only where the spam check is on.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Simple Hack serves the same recipes with a note on who the owner is there, and points comments and guestbook requests to wall.
Each person's recordsPeople add records and see only their own status and history, while the owner sees and updates all of them.
The table uses author-or-owner read rules: each signed-in person reads their own rows, signed-in people add, and the owner reads and changes everything. A status column and a linked table of change rows give each record a history: in the worked example orders has order_changes, and bookings use bookings and booking_changes linked by booking_id. A customer adds a change row (a note, a cancellation request); the owner updates the status. The page reads the records and their history separately. A linked row must point at a parent the person may read, so a catalogue of products lives in a table with public read rules.
Example. A print shop takes orders on its site; each customer sees their own orders and whether they are printed or shipped, and the owner sets the status from chat or the admin page.
- Who
- Anyone taking 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, or a waitlist with "my place in line".
- Where
- Ask your AI app for the
recordsrecipe. The owner reads and updates all records from chat, from an owner page on the site, or in the Storage panel on your sites page. - Limits
- Author-tracked tables carry a
visitor_idcolumn the server stamps. Populated tables with trusted authorship can adopt author-based read rules; a legacy database whose pages could write SQL must be empty before rules namevisitor_id. Linked change rows need declared foreign keys. Anonymous visitors are asked to sign in.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise has the records preset on its own engine; the linked change-history rows of the worked example are Simple Host and small box only.
Comments without sign-in, spam-checked Off by defaultAnyone can post a comment, review, or question without signing in, after a Cloudflare Turnstile check, and the owner moderates.
Checked add rules: anyone reads, anyone adds after a spam check, and only the owner edits and deletes. When a page saves, the check opens in a small frame served from Simple Host's own address, and the page resends the save with the token. The server verifies the token with Cloudflare before saving, and the visitor's IP address is never sent to Cloudflare. On a SQLite table, a restrictive read requiring owner or approved_at is not null holds posts. Stamping applies only when effective rules reference TEXT approved_at; an unused leftover column is ordinary data. The owner signed in on their own site posts without the check. The recipe comments also answers to guestbook.
Example. A photographer's blog takes comments from readers without accounts; two spam posts a day never arrive because they fail the check.
- Who
- Anyone running a blog, a product page with reviews, a Q&A page, or a visitor book who wants posts without making people sign in.
- Where
- Ask your AI app for recipe topic comments. It saves the checked add and optional approval rules; the owner can edit the rules in the Storage panel.
- Limits
- Works on key-value and SQLite resources, not file buckets. A checked post is at most 4,000 bytes with at most 2 links, 10 posts per 30 seconds per address, and 60 per site, on top of the usual storage limits. It needs Cloudflare Turnstile keys, so it is on at simple-host.app and off until a self-hosted box adds its keys.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Simple Hack leaves it out on purpose because a team's owner rights end at its submission deadline, so nobody would remain to moderate; Hack sends guestbooks to wall, where people sign in to post.
Who sent each recordThe owner turns the id on a record into the email its sender signed in with, for people who signed in on that site.
A visitor's saves carry an opaque id: a column on every table with own reads, and, in the owner's listings only, on key-value entries and uploaded files. The owner asks for the emails behind 1 to 100 ids and gets each person's sign-in address, with a found mark. The server records who signed in on which site itself, so an owner can only resolve people who signed in on that very site, never an account with no link to it. Emails are never stored in the site's data and never reach a visitor, so a later change of read policy cannot expose them.
Example. A caterer asks "who placed order 12?" and the AI app reads the order's id, looks up the email, and drafts the confirmation.
- Who
- Owners who need to reach the person behind an order, a booking, or a support request.
- Where
- Ask your AI app. The lookup is owner-only.
- Limits
- 1 to 100 ids per lookup. Only people who signed in on that site as visitors resolve; others answer not found.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Enterprise does not need the lookup because every writer is a company identity, so the owner sees the username on each entry directly.
Add a record for one signed-in visitorThe owner adds a row on a records or personal table for one visitor who has already signed in, instead of waiting for them to add it.
The row's visitor_id is set to that visitor, so only they (and the owner) see it, exactly as if they had added it themselves; a second column, written_by, is marked owner so it never looks like the visitor's own, in their own reads and anywhere else the row's columns show. The visitor must have signed in on that site at least once already; naming anyone else answers not found, with no email-only binding before a first sign-in. The owner's own subscriptions are not notified. The same check runs whether the owner uses their key, the connector, or is signed in on the site's own address; a pick list shows only people with saved data here or named-viewer status, never everyone who has signed in.
Example. A gym coach picks a client from the list, assigns this week's program, and replies to their check-in message; the client's own page shows both, marked as from the coach.
- Who
- A coach who assigns a client's program, a tutor replying to a student, or any owner who works directly with many signed-in people one at a time.
- Where
- Ask your AI app, or get_page_recipe topic people for one page with the owner's view and the client's.
- Limits
- SQLite tables whose permissive read alternatives require author or owner, with at least one author alternative. KV and files are not covered. The visitor must already have signed in on this site.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
The pick list and resolving a person by email are Host only (named viewers and storage_visitor_emails are not a Simple Hack concept); on Simple Hack the owner names the visitor by their reference instead. Enterprise is a later port.
SQL errors that say what to fixEvery refused query, statement, or schema change carries a stable code and a message with the cause and the fix.
A refusal names the word SQLite stopped at, a second statement in one call, a mismatch between placeholders and values, a feature that is not available (PRAGMA, ATTACH, temporary or virtual tables, transactions), the route a statement belongs on, a missing table or column, a UNIQUE, NOT NULL, CHECK, or FOREIGN KEY failure naming the column, a visitor statement refused by the read rule, a timeout, or an oversized value. The owner also sees the real table and column names; visitors get the rule without names. The connector passes the message through with no generic hint. When a site name matches nothing, the answer lists the account's sites and spots an address passed as a site name.
Example. An AI app inserts into bookings without a date; the answer says NOT NULL failed on starts_at, and the app fixes the insert on the next call.
- Who
- The AI app writing a site's queries, and the owner reading what it reports.
- Where
- Automatic in every storage answer your AI app gets.
- Limits
- No message holds a file path, and visitors never see table or column lists.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise answers with the same intent in the words of its own engine (declared tables rather than SQLite SQL).
Schema setup that can be run againThe owner's setup for a table, view, or trigger can be rerun safely, so a recipe's setup is repeatable.
The owner's schema route takes CREATE TABLE, CREATE VIEW, and CREATE TRIGGER statements. With IF NOT EXISTS, a statement for something that already exists is accepted and changes nothing, so a recipe's owner setup can be run twice. A new table made through this route in a database with own reads receives its visitor_id column and an index, and a schema change that would remove that column rolls back. Saving a per-table rule for a table that does not exist yet gives a warning, and a new table that lands on a wider database default gets a note.
Example. A bakery's AI app reruns the records setup after adding a column; the existing orders table is left alone and only the change applies.
- Who
- The AI app setting up or changing a site's tables.
- Where
- Ask your AI app. Schema changes are owner-only.
- Limits
CREATE INDEX IF NOT EXISTSon an index that already exists is still refused. Table names in per-table rules match without regard to case.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise has no per-site SQL; the owner declares columns instead.
File buckets for uploadsA bucket holds files visitors upload or the owner stores, with the same presets and a download link that checks rights each time.
A bucket is a storage resource like the others. Pages upload through auth.js and the owner uploads from chat. Whether a save is an add or an edit is decided by whether the path exists, so an add-only setting stops visitors overwriting each other's files. Under own reads each person lists their own files and the owner lists all, with the uploader's id. A download link rechecks the caller's rights when it is used. The gallery recipe shows visitors uploading photos everyone sees, and the photo pages shrink pictures in the browser before upload.
Example. An architecture studio's client portal lets each client upload reference photos to their own folder and download the drawings the studio stored for them.
- Who
- Anyone collecting photos for a gallery, documents for a client portal, or attachments on a request.
- Where
- Ask your AI app, or the
galleryrecipe. The Storage panel beneath the site on your sites page shows the bucket's usage. - Limits
- 1,000,000 bytes per upload. 1,000 files per bucket, counting empty ones. A path has at most 16 segments. Files share the site's separate 10,000,000-byte file allowance.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
On Simple Hack files come out of the team's single 1,000,000-byte pool and team file links recheck membership; on Enterprise files are bucket objects counted in the owner's quota.
Storage limits and usageEach site has 10,000,000 bytes for key-value and SQLite, a separate 10,000,000 bytes for files, and 1,000,000 bytes per upload.
Key-value and SQLite data share one allowance per site and files have their own. Usage shows used, limit, and remaining bytes for each, with a breakdown by kind. Key-value usage counts the key and the stored value. Visitor writes are rate limited per site and address and per signed-in person; reads are not, so a public gallery of 150 photos loads without using write allowance. Owner tools are exempt from the visitor limits. Writes during a deploy wait up to 2 seconds and then answer busy with a retry time.
Example. A small shop with a few hundred orders a month uses well under a tenth of its table allowance; product photos count against the separate file allowance.
- Who
- Anyone planning how much a site will hold, and anyone whose site is filling up.
- Where
- Ask your AI app how much a site uses, or open the Storage panel beneath the site on your sites page.
- Limits
- 10,000,000 bytes of key-value and SQLite per site, 10,000,000 bytes of files per site, 1,000,000 bytes per upload. The allowance started at 1,000,000 bytes pooled per site and was raised for Simple Host on 10 October 2026. Deployed website files, SQLite's write-ahead log, and the older saved data are counted separately. A write that would pass the allowance is refused.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack keeps one 1,000,000-byte pool per team or event website across all three kinds, with its own per-upload cap; Enterprise sets the same values as settings per installation.
Safe simultaneous updates Existing sites onlyA page adds one to a number, adds an item to a list, or removes one without reading the whole box first, so two people at once both count.
Instead of replacing the document, a page sends a short list of moves and the server applies them in order. Two visitors doing it at the same instant both count. Numbers stay exact: adding a whole number adds exactly, and whole numbers of any size match in remove-where. A whole-document write can carry the version it read, and is refused if someone wrote first. A retried write with the same key is saved once for a signed-in writer.
Example. A sports club's older sign-up page adds one to the attendance count as each member confirms, and the count is right even when a dozen confirm in the same minute.
- Who
- Anyone with a headcount, a vote, a comment thread, or anything else several people touch at once.
- Where
- Used by your page's own code.
- Limits
- Five moves are supported (set, add-to-a-number, add-to-a-list, remove, and remove-where) up to 100 in one request. Anything cleverer has to be worked out in the page.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Enterprise writes the document whole, last-write-wins or with a version check, and has no move list.
Live numbers without a refresh Existing sites onlyA page keeps checking the box cheaply, so a count or a comment thread updates itself while people are looking at it.
The page asks again every few seconds with the version it already has. When nothing changed, the answer is empty and costs almost nothing; when something changed, the page gets the new document and redraws.
Example. An older fundraising page shows the running total of pledges and ticks up while donors watch.
- Who
- Anything with a live figure on it: an RSVP headcount, a signup counter, a discussion.
- Where
- Your page's own code: a conditional request returns nothing when the box has not changed.
- Limits
- It is polling, with a few seconds of lag, and there is no push. Reads are rate limited per site and address.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
The store is public, on purpose Existing sites onlyPages and shared data are public; Each person's records, private Submissions, and Personal records have their own read rules.
Anyone who can open the site can read the shared document and every public list. Personal details belong in a private collection, a Submissions name, a Personal record, or, on a current site, a storage resource with a read rule.
Example. A neighbourhood association's older notice board keeps the meeting dates public and the members' contact details in a private collection.
- Who
- Everyone using the store. It shapes what you should and should not collect.
- Where
- Not a setting: it is how the store works.
- Limits
- Anything a page can read, a visitor can read. Reading it takes a page in a browser: pasting the address into a terminal is refused, which slows casual copying and gives no privacy.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Enterprise sites are opened by signed-in colleagues only, so the document is read by them and not by the public.
Who is allowed to write Existing sites onlyEvery save from a page needs a signed-in visitor, so a passer-by cannot fill the store with junk; your agent saves with your key.
On a site's own address a write needs a signed-in visitor or the owner's API key; connector tokens act as the owner. Reading never requires either. Another account's key gets a site not found answer and writes nothing. On the old shared content address sites.simple-host.app reads stay open and writes need the key or the connector, because sign-in is never offered there, and a site with its own domain takes no writes on its shared address at all.
Example. A yoga studio's older class list takes a save only from a member who signed in, while the teacher's AI app updates the timetable with her key.
- Who
- Anyone collecting entries in public.
- Where
- Not a screen: it is applied when a page tries to save. Visitors sign in on the site's own address; your agent sends your API key.
- Limits
- Signing in stops strangers writing anonymously, but any signed-in visitor can still save. Anything that must stay private goes in a private collection.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
On Enterprise every viewer is signed in with the company and may write, keys included.
Use the store from a site hosted elsewhere Existing sites onlyA page hosted on another service can use one of your sites here as its backend once you have allowed that page's address.
The owner's agent adds the other page's exact address to the site's allowed list. From then on that page's saves and reads are accepted as if they came from the site itself. There is no button for it; your AI agent does it for you.
Example. A consultancy's brochure site on another host keeps its enquiry counter on an older Simple Host site after allowing the brochure's address.
- Who
- People whose site already lives on another host but who want a form or a counter without running a server.
- Where
- No screen. Ask your agent to allow the address.
- Limits
- Up to 20 addresses per site, and you have to name each one exactly.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Save what a form collects Existing sites onlyEach submission is added to a named list, one row per entry, separate from the shared box so it can grow well past it.
A collection is where form entries go: RSVPs, signups, orders, messages. Adding stays fast no matter how long the list gets. Visitors append; in Submissions each visitor can see, change, and withdraw their own, and on a Shared board anyone signed in edits items. You can delete any entry, or empty the whole list, from your page or through your agent. A retried save with the same key is stored once for a signed-in writer.
Example. A language school's older enrolment form adds each application to an applications list that the office reviews every morning.
- Who
- Anyone with a form: an event page, a waitlist, a contact form, a survey.
- Where
- Your page's own code saves to it.
- Limits
- Up to 64 KB per entry (each new entry is at most 16 KB in declared Submissions, and a declared Submissions name holds at most 10,000 live entries). Entries in a public list cannot be edited. Entries added without the owner's key are limited to 30 a minute per address.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Enterprise keeps per-site saved state as its only older data store; collections were never built there.
Read the entries back on the page Existing sites onlyA page reads its own entries, newest first, so a sign-up list or a public wall can show what has come in.
The page asks for the list and gets the newest entries first, a page at a time, with a cursor for the next page. Who sent each entry is left out of every read but the owner's.
Example. A running club's older results page lists the finishers members entered, newest first.
- Who
- Anyone who wants the results visible rather than hidden behind a login.
- Where
- Your page's own code. AI-built sites are told to include a second page for exactly this.
- Limits
- 200 entries at a time maximum, 50 by default. Anything a page can read, a visitor can read.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
See what a site has collected Existing sites onlyEvery list on a site, public or private, with its entry count, when the last one arrived, and a table of the entries themselves.
Each list shows a public or private badge, View items, a spreadsheet, and a More menu with the privacy switch, Settings, History, and Recently deleted. You can delete any entry (spam in a comment list, a test entry), correct an entry in a private list, or clear a whole list after typing its name. The owner's view adds a sent by column. Your agent can do the same.
Example. A dentist checks the older appointment-request list on Monday, deletes two spam entries, and corrects a typo in a patient's phone number.
- Who
- You, checking whether anyone actually filled the form in, or cleaning up after spam.
- Where
- Lists beneath the site on your sites page. Your agent can do the same.
- Limits
- Shows the 50 most recent entries in the table view. A deleted entry stays in Recently deleted for 30 days, then is gone for good. Entries in a public list can be deleted but not edited.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Download everything as a spreadsheet Existing sites onlyOne button gives you the whole collection as a CSV file you can open in any spreadsheet.
Press Download spreadsheet next to the list and a CSV of every live entry arrives. The owner's export adds a last column with who sent each entry. Cells that look like formulas are made safe for spreadsheet programs.
Example. A conference organiser downloads the older speaker-application list and sorts it by track in a spreadsheet.
- Who
- Anyone who has to actually use the entries: a sign-up list to check off, a mailing list to import.
- Where
- Download spreadsheet next to the list on your sites page.
- Limits
- A snapshot at the moment you press it. No filtering or date range; you get the whole list.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Private collections Existing sites onlyA collection can be made private: only signed-in visitors submit, you read them all, and each visitor sees and changes only their own.
Only signed-in visitors can submit, from the site's own address, never by API key. Each entry is stamped with the visitor's verified email and the time. You read them all and may edit them; each visitor sees, changes, and withdraws only their own. A list made public again keeps its submitters' emails private: who sent what is shown to the owner alone.
Example. A physiotherapist's older intake form stores each patient's details in a private collection that only she reads.
- Who
- Anyone collecting personal details: orders, RSVPs, sign-ups.
- Where
- Make private next to the list on your sites page, or choose Submissions under the list's Settings, or ask your agent. Visitors submit on the site's own address; you read the entries on your sites page, on an owner page on the site, or as a CSV.
- Limits
- Making a private collection public again shows everything already in it, so the page and your agent ask first. The site needs an address of its own.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Four kinds of saved data Existing sites onlyEach data name is one kind, and the kind decides who reads and who changes what: Page info, Submissions, Personal, or Shared board.
Page info: you write, everyone reads. Submissions: visitors send; private to you by default, and public only without who sent them; each visitor lists, changes, and withdraws their own, and brings back what they withdrew for 10 minutes; a name can take one entry per person. Personal: one private record per signed-in visitor that follows them to any device; only that visitor reads or writes it, and you see how many people have a record and the total size from 3 people up. Shared board: a list a group edits item by item with a version check, and only you empty it. A name nobody declared is Shared, as before: anyone reads it and signed-in visitors save to it.
Example. A music teacher's older site keeps the term dates as Page info, lesson requests as Submissions, and each student's practice log as a Personal record.
- Who
- Anyone building a form, a menu, a habit tracker, or a group list without writing access rules.
- Where
- Your AI app declares each name when it builds the site; you see and change the kind under Settings next to each name on your sites page.
- Limits
- A Page info document is at most 1 MB, and a site declares at most 20 Page info names. Each new entry is at most 16 KB, a name holds at most 10,000 live entries, and a site declares at most 50 Submissions names. A personal record is at most 64 KB, and a name holds records for at most 1,000 people. A board item is at most 16 KB, and a board holds at most 2,000 live items. A site declares at most 20 Personal names, and declares at most 20 Shared board names. All but Page info need the site on an address of its own. A site's own pages can read a visitor's Personal record, so it is as private as the site's pages are trustworthy.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Who may save here, and Block Existing sites onlyChoose whether anyone who signs in may save on a site, or only listed emails and whole domains, and block one person with a click.
A site setting that covers every visitor write on the site: page data, lists, and Submissions. Anyone who signs in may save (the default), or only listed emails and whole @domains. Either way a block list applies, filled from Block next to any entry. A block and the one-per-person rule match the person's address with a +tag dropped, and Block by entry uses only the address the server stamped.
Example. A company's older internal survey site lists @acme.example so only staff can save, and the owner blocks a leaver's address.
- Who
- Anyone whose form is for a club, a class, or a company, and anyone dealing with a troublemaker.
- Where
- Who may save here under the site's data on your sites page, and Block next to an entry. Your AI app can do both.
- Limits
- There are at most 500 emails and domains in total. You always may save. A blocked person can still withdraw what they already sent.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Email me when something arrives Existing sites onlyNew Submissions can email you once a day, soon after each arrives, or not at all, and every email has a link that stops them.
Once a day is the default for private Submissions and off is the default for public ones. The email goes to the site owner's address with a stop link that opens a confirmation page. Each email is sent once even across servers, and an entry saved while a digest was being sent goes into the next one.
Example. A florist with an older order form gets one email each morning saying how many orders came in overnight.
- Who
- Anyone taking orders, RSVPs, or sign-ups who will not check the page every day.
- Where
- Email me under the name's Settings on your sites page, or ask your AI app.
- Limits
- Soon after they arrive means at most one email per name every 10 minutes, counting what came in. The email carries counts and the list's name, not the entries. A failed send is not retried.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
History, Restore, and Delete for good Existing sites onlyEvery change to saved data is kept for 30 days with who made it, so you can undo one change, put a document back, or restore entries.
Every write to the shared document and every edit, delete, clear, and restore in a list is recorded with who made it (their account and the address they signed in with) and when. Open History to see the document before any change, undo one change, or restore a version; a restore is itself a change. Open Recently deleted to bring back entries one by one or all at once. On a Shared board, Restore all names a window from 15 minutes to 30 days so it brings back what went since then, never what people deleted on purpose before. Delete forever removes an entry and its history at once, for a person who asks to be erased or a flood of spam, and Clear history removes every earlier version of a site's data after you type the site's name. Each visitor also has a 30-day history of their own Personal record.
Example. A bakery's older menu document is overwritten by mistake; the owner opens History, views Friday's version, and restores it.
- Who
- Anyone whose page data was overwritten, or who deleted the wrong entry.
- Where
- History and Recently deleted under the site's data on your sites page, or ask your AI app.
- Limits
- Every change is kept for 30 days: the owner restores any of it. A deleted entry stays in Recently deleted for 30 days, then is gone for good. Past 20 MB of history per site, the oldest versions are thinned, always keeping each day's first full copy and the record of who deleted what. Live entries are never touched by Delete forever, and Recently deleted does not count toward the site's cap.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Enterprise keeps the last 20 writes of a site's saved document and the owner or team restores one; there is no Recently deleted for lists.
Sign-in and access
Back to the mapHow owners and visitors sign in, the keys an AI agent uses, and who may open a site.
Sign in with an emailed codeType your email, get a six-digit code, type it back. No password, and your first code creates the account.
Enter your email in the sign-in card and press Continue. A six-digit code arrives; paste or type it and the card signs you in as soon as the sixth digit is in. Your first code creates the account, with no separate sign-up step. The same card is used on the home page, on the connector's consent page, on Simple Hack, and on the shared sign-in page a site sends visitors to.
Example. A consultant publishes a client document from their AI app, then signs in on simple-host.app with a code to see the address and manage the site.
- Who
- Anyone starting out, and any visitor who needs to sign in to post on a site.
- Where
- The sign-in box on the home page.
- Limits
- The code expires after 15 minutes and you get three tries before you have to ask for a new one. Resend is available after 30 seconds. Codes are limited per email address and per IP, so a burst of requests from one place is refused for a while. A server that cannot send email cannot offer codes.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise signs people in with the company's identity provider only; a small box needs outgoing email set up, and may turn codes off in favour of company sign-in.
Sign in by tapping the link in the emailThe same email carries a link. Tapping it signs you in without typing the code at all.
Ask for a code as usual. The email that brings the code also carries a link. Open it in the browser you asked from and you land signed in, with no code to copy. If the link is opened in a different browser, the card says so and offers the code instead.
Example. A shop owner on their phone taps the link in the email and lands on their sites page without switching between the mail app and the browser.
- Who
- Phone users, mostly: it saves copying digits between apps.
- Where
- The email itself. You land on your sites page already signed in.
- Limits
- Same 15-minute expiry, and the link only works once. It signs in the account on the sign-in page it was asked from; a visitor signing in on a site types the code.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise has no emailed codes or links; a small box needs outgoing email set up.
Sign in with GoogleOne tap instead of the email round-trip. It is the same account as the email sign-in when the addresses match.
Continue with Google is the first button on the sign-in card. Google confirms who you are and you come back signed in. When the Google address matches an account that signs in by email, it is the same account, so you will not end up with two. A page on your site offers the same button through the hosted sign-in helper; that sign-in only ever makes a visitor session, never an account key.
Example. A visitor booking a table on a restaurant's site taps Continue with Google and the booking is saved under their name without an email round-trip.
- Who
- Site visitors saving something on a site, and owners who would rather not wait for mail.
- Where
- Under the email box on the home page, and on your site, on the site's own address, through the hosted sign-in helper.
- Limits
- Google is the provider today on simple-host.app. GitHub is wired but not switched on. Self-hosted installs can add their company's identity provider as another button. Linked Google sign-ins are listed under Sign-in on your sites page with Unlink.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Enterprise uses the company's identity provider instead; a small box needs its own Google OAuth client set up before the button appears.
Choose your address at sign-upWhen a sign-in would create a new account, you pick your address first, checked while you type.
When an emailed code, link, or Google sign-in would create a new account, the card asks "Choose your address" first. It is prefilled with the address you would have been given and checked while you type, so a taken or reserved name is named under the field before you press Continue. Closing the question creates nothing, and the code still works if you come back. An AI agent registering an account can propose an address the same way.
Example. A freelance designer signs up and types their studio name as the address so every client site lives under studio.simple-host.app from the first publish.
- Who
- Anyone making their first account, and agents registering one for a person.
- Where
- The sign-in card, the first time a sign-in would create an account.
- Limits
- A taken or reserved address is refused without using up your code. The same check runs when you change the address later under Your address.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Enterprise names come from the company directory; Simple Hack accounts have no personal address to pick.
Your handleEvery account gets a short public name. It is part of every address you publish and the address of your public profile.
Your handle is the middle of every site address, site.handle.simple-host.app, and the address of your public page at simple-host.app/handle. You pick it at sign-up, or it is made from your email. Your address on your sites page shows it with Change; the new name is checked while you type and confirmed before it is saved, and a refused save names the problem under the field without signing you out.
Example. An agency changes its handle after a rebrand; every client site's old address redirects to the new one and the agency's public page moves with it.
- Who
- Everyone with an account; it is how visitors tell your sites apart from anyone else's.
- Where
- In every site address, and at the top of your sites page. Your address on your sites page shows it, with Change.
- Limits
- Before you have published anything the handle is free to change. Once you have published, it can change once every 30 days: the old handle is kept as an alias so every old address redirects to the new one, a certificate for the new address is requested, and what your pages kept in visitors' browsers starts fresh.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
On Enterprise a person's name comes from the company directory and an admin renames; Simple Hack has no personal sites.
A key for your AI agentA personal key that lets your coding agent publish and manage sites for you without you being at the keyboard.
Each sign-in gives the browser or agent a new key, and the Keys panel lets you mint more by hand. Each key has a name (typed, or where it came from, such as "dashboard sign-in" or "agent sign-in"), its last four characters, and when it was last used. A key is shown once at creation and stored only as a hash, so it can never be shown again. You revoke one at a time, or Sign out everywhere to replace them all.
Example. A developer mints a key named "laptop agent" and gives it to the coding agent that publishes their product's landing page and changelog.
- Who
- Anyone using a coding agent rather than clicking through screens.
- Where
- The Keys panel on your sites page: create a named key (tick Deploy only for a CI secret: it can publish, roll back and list sites and nothing else), see when each was last used and when it expires, revoke one, or Sign out everywhere.
- Limits
- Each sign-in adds a new key, and older keys keep working until revoked. A key unused for 180 days stops working. A key can also be given a fixed expiry when you create it. Keys are stored only as hashes, so a key cannot be shown again later. Treat it like a password. Minting, revoking, and signing out need one of the account's own keys; a connected app cannot do it, and the connector's only account tool,
who_am_i, is read-only. When a key stops working, the refusal says why: revoked or unknown, expired on its date, or unused too long, each telling you to create a new key.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise keys expire after a fixed lifetime, 90 days by default, and warn in the last 14 days.
Deploy-only keys and key expiryA key for CI that can publish, roll back, and list sites and nothing else, with an expiry you choose or an idle cut-off.
Tick Deploy only when you create a key in the Keys panel. That key may create, update, roll back and list sites, read their versions and files, and make preview links. Everything else is refused: deleting or renaming a site, domains, keys, saved data, storage, analytics, account settings, and connecting apps. The same rule applies on the API and through the connector. You can also give any panel-minted key a fixed expiry, from 1 to 3,650 days. The Keys list shows a Deploy only badge, last used, and the expiry or the date the key stops if it stays unused.
Example. A product team puts a deploy-only key in GitHub Actions so every merge publishes the docs site, while saved data and domains stay out of the pipeline's reach.
- Who
- Anyone putting a Simple Host key in a CI pipeline or a build server.
- Where
- The Keys panel on your sites page, and the deploy-from-CI notes in the website-deploy skill.
- Limits
- A key unused for 180 days stops working. The count runs from its last use. Expired keys stay listed, do not count toward the per-account key limit, and are deleted 30 days after they stopped. A deploy key never carries admin powers, even one an admin minted. Treat a deploy key like the site itself: it can ship code that runs when someone views the site.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise's CI scope is called publish and also writes saved data; its keys have a fixed lifetime (90 days by default) rather than an idle cut-off.
Sign out, or sign out everywhereSign out ends the key this browser holds. Sign out everywhere stops every key, app connection, and site sign-in at once.
Sign out in the header deletes the key this browser held and clears what the browser kept, and since 29 October 2026 it also ends the shared sign-in pass that carried you onto sites, and every site session that came from it. Sign out everywhere replaces every key on the account, disconnects every connected app, and ends every sign-in on your sites; the browser you pressed it in gets a fresh key. Each connected app can also be disconnected on its own from the connected-apps list.
Example. A founder gets a sign-in alert for a browser they do not recognise, presses Sign out everywhere, and reconnects their own AI app with the fresh key.
- Who
- Anyone who lost a laptop, shared a key by mistake or got a sign-in alert they did not expect.
- Where
- Sign out in the header, and Sign out everywhere in the Keys panel on your sites page.
- Limits
- Your agents need the new key afterwards, and apps you want to keep have to be connected again. No AI app can sign you out everywhere or rotate your keys for you; those actions need one of the account's own keys and have no connector tool.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
On Enterprise, Sign out everywhere ends every company session and, by default, every API key and connected app in one audited step.
Change your sign-in emailMove the account to another address with a code to the new address and one to the current one; both are needed.
Under Sign-in, enter the new address. A six-digit code goes to the new address and another to the current one, and both are needed. The account moves to the new address; your handle, sites, and connected apps stay. Every other key on the account is signed out (the one you used stays), and so is every sign-in on your sites. Linked Google sign-ins stay linked and are listed with Unlink.
Example. A contractor whose agency mailbox is closing moves their account to a personal address before the old one stops receiving mail.
- Who
- Anyone leaving a job address or a mailbox they no longer use.
- Where
- Sign-in on your sites page, or ask your AI app.
- Limits
- Codes are valid for 15 minutes, with three tries, and one change can be pending at a time. The old address gets a notice with a 7-day undo link: undoing puts the account back, signs everything out, and removes sign-ins and connected apps added since the change. An address another account signs in with is refused only after both codes are verified, so asking reveals no more than signing in does. Event and reviewer accounts keep their address. The change needs one of the account's own keys; a connected app cannot make it.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise refreshes the stored email from the company's identity provider at each sign-in; a small box with email sign-in turned off has no email to change.
An email after each sign-inAfter each sign-in or app connection you get one short email saying when, from which browser or app, with a Sign out everywhere link.
After each successful owner sign-in (code, link, or Google) and each app connected on the consent screen, one short email arrives: the time in UTC, the browser or app in a few words ("Chrome on macOS"), and a link to your sites page where Sign out everywhere and the alerts switch are. An app's self-declared name is quoted as "reported by the app" and cut to 40 characters.
Example. A small business owner sees "Chrome on Windows" in an alert when they only use a Mac, and signs out everywhere before anything is changed.
- Who
- Everyone; it is how you notice a sign-in that was not you.
- Where
- Your inbox. Turn it off or on under Sign-in on your sites page.
- Limits
- At most one per browser or app a day, and never for API key calls, event accounts, or the plugin reviewer account. It never contains your IP address or a location. Sending happens in the background, so a sign-in never waits on it.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
On Enterprise sign-ins go through the company's identity provider and its audit stream; a small box needs outgoing email set up.
Download your data, or delete your accountOne .zip of everything held about you, and a Delete my account that removes the account and all of it at once.
Download my data gives one .zip: a README, your account details (email, handle, display name, old handles, claimed names, custom domains, linked Google or GitHub sign-ins), your keys' names and last four characters (never the keys themselves), connected apps, what you sent to other people's sites while signed in, and every site with its saved data, including sites in Recently deleted. Delete my account removes the account and all of it in one step and sends one confirmation email.
Example. A consultant closing their practice downloads the archive of every client site and its submissions, then deletes the account.
- Who
- Anyone leaving, or checking what is kept about them.
- Where
- Your data on your sites page.
- Limits
- Deleting is for good and skips Recently deleted: every site (deleted ones included) with files, versions, saved data, lists, and analytics, keys, connected apps, sign-in identities, visitor sessions, and your entries on other people's private lists go. Entries you posted to public lists carry no link to you and stay. Your handle, old handles, and site names are retired and can never be reused by anyone; custom domains are unbound. You type your handle to confirm. Analytics are left out of the download (they hold no personal data). Refused while the account is suspended or holds a taken-down site, and for connected apps; the action needs one of your own keys.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
On Enterprise an admin exports or deletes a disabled person's data; the person does not do it themselves.
Visitors sign in on your siteSomeone reading one of your pages can sign in right there (Google or an emailed code) and the page can then save on their behalf.
A page loads the hosted sign-in helper (auth.js) and shows Sign in. The visitor signs in with Google, an emailed code, or on a self-hosted install their company account, and comes back to the page with a session for that site's address. Saves the page makes are then made as that visitor. Visitor sign-in is the only sign-in a page uses: account sign-in answers only on simple-host.app itself, so a page can never mint an account key for a shopper. The connector instructions, the skills, and the helper all say so in the same words.
Example. A clinic's booking page asks the visitor to sign in before saving the appointment, so the owner's bookings list shows who asked for what.
- Who
- Site authors collecting anything from visitors: a booking, a quote request, a client upload, a comment.
- Where
- On your published page, at the site's own address. The page loads the hosted sign-in helper (
auth.js) and that handles the rest. - Limits
- Every save from a page needs a signed-in visitor, and a sign-in covers that one site only. Your agent saves with your API key (or the connector) instead. A code request on an install with no mailer is refused with a plain message. The helper keeps what the visitor had typed for 15 minutes and restores it after the sign-in round trip (never passwords, files, card fields, or codes).
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
On Simple Hack, team and event sites sign visitors in the same way; on Enterprise the company session is handed to the site.
One sign-in across sitesA visitor signed in once on simple-host.app can continue onto any site with one tap, after saying yes to that site.
Pressing Sign in on a site sends the browser on a short trip through simple-host.app. A browser already signed in there continues straight back with a session for that site; otherwise the shared card offers email, Google, or company sign-in, and that creates a normal account. The first time a person reaches each site, a consent step asks whether to tell that site who they are, including when the owner named their email. Sites behind named viewers make the hop automatically; ordinary pages wait until the visitor presses Sign in. Custom domains follow the same path.
Example. A client who signed in to one agency's proposal site opens the agency's second proposal site and is through in one tap, after agreeing to share their identity with it.
- Who
- Visitors who use several Simple Host sites, and owners whose named viewers open more than one site.
- Where
- The Sign in button on any site, and the shared sign-in page on simple-host.app.
- Limits
- A passcode must be entered before the hop; offline or suspended sites refuse it. The shared sign-in lasts 30 days, or 14 days without use, and is bounded by the account key behind it. Signing out on a site or on simple-host.app ends the shared sign-in and every site session that came from it. No iframe or third-party cookie is used, and prefetches and background requests are refused. There is no list of sessions to review; Sign out everywhere ends them all.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxpartly
Simple Hack hops through simple-hack.app for team and event sites; Enterprise hands the company session to sites with the same consent; a small box without an account address keeps the older per-site sign-in.
Visitors can sign out againA visitor can end their sign-in from the page they signed in on, and that ends the shared sign-in too.
After signing in, a "Signed in as … Sign out" chip shows on the site. Sign out ends the session for that site and, through a one-time trip to simple-host.app, the shared sign-in behind it and every other site session that came from it. If the browser's shared sign-in does not match, simple-host.app asks for confirmation before signing out.
Example. A customer finishes a quote request on a shop's shared tablet and signs out so the next person cannot post under their name.
- Who
- Anyone on a shared or borrowed device.
- Where
- Offered by the sign-in helper on the page they signed in on.
- Limits
- Signing out on one site signs the browser out of every site that shared the sign-in. Pages already open may keep showing until they reload.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
One sign-in card everywhereEvery sign-in uses the same card, so the dashboard, the connector, Simple Hack, and site visitors see the same steps and the same words.
The card shows Continue with Google first, the company button where one is set up, "or", an Email box, and one Continue that signs in or creates the account. Then one code box that accepts a paste and signs in at the sixth digit, a 30-second resend, and Open Gmail for Gmail addresses. Errors appear under the box and come from one table on the server, so the card and the API say the same thing: the code was wrong (with tries left), used up, expired, or the link was opened in another browser.
Example. A judge joining a hackathon on Simple Hack and a shopper on a Simple Host store see the same card and the same error text when a code expires.
- Who
- Everyone who signs in anywhere on Simple Host or Simple Hack.
- Where
- The home page, the connector's consent page, Simple Hack sign-in and join links, and the shared sign-in page a site sends visitors to.
- Limits
- Open Gmail appears for @gmail.com and @googlemail.com only. The email form is hidden on installs where email sign-in is turned off.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise goes straight to the company's identity provider, so there is no card of choices; its problem and no-access pages share the card's look.
Company sign-in on self-hosted installs Off by defaultA self-hosted install can add its company's identity provider as a sign-in button next to Google, with the same rules Enterprise uses.
The operator gives the install the identity provider's details and a "Sign in with your company account" button (the label is configurable) appears wherever Google's does: the dashboard, the connector's consent page, and visitor sign-in on team and event sites. The install checks that the email is verified, that it belongs to an allowed domain where one is required, and that the identity is bound to the issuer, so a later change of provider can never land on an old account. A refusal shows a plain page naming the reason.
Example. A company running an internal hackathon on the standalone Simple Hack package lets staff sign in with their Microsoft work accounts and no one needs a code by email.
- Who
- Companies running Simple Host on their own server or Simple Hack's standalone package, whose people already have a work account.
- Where
- The sign-in card on a self-hosted install, once the operator has set it up; the operator's steps are in the setup guide.
- Limits
- simple-host.app and simple-hack.app do not offer it. A Google-based issuer needs an allowed-domain list, since a consumer Google account can carry any address. If the identity provider is unreachable, the sign-in says so instead of failing silently; the install still starts.
- Simple Hostno
- Simple Hackno
- Enterpriseyes
- Small boxyes
On Enterprise the company's identity provider is the only sign-in; on a small box or the standalone Simple Hack package it is an extra button beside email and Google.
Email sign-in can be turned off Off by defaultA self-hosted install with company sign-in can switch off emailed codes everywhere, so staff sign in with their work account only.
With company sign-in set up, the operator turns emailed codes off. The email box and its "or" divider disappear from every sign-in card: the dashboard, the connector, team-site visitors, and changing a sign-in email. Anyone who tries the old way is told that email sign-in is off on this server and to sign in with their company account.
Example. A company's internal Simple Host keeps every sign-in on its own identity provider, so leavers lose access the moment IT disables their account.
- Who
- Operators of a company install who want one identity for everyone.
- Where
- A setting on a self-hosted install; nothing to do on the screen.
- Limits
- Refused unless company sign-in is configured, since nothing else could sign anyone in. It only turns off the sign-in codes; the install can still send other email, such as Submissions digests, when outgoing email is set up.
- Simple Hostno
- Simple Hackno
- Enterpriseno
- Small boxyes
Enterprise has company sign-in only, so there is nothing to turn off; the standalone Simple Hack package has the same switch as a small box.
A passcode on a whole site Off by defaultPut one passcode on a site and every address of it shows an Enter the passcode page until someone types it.
Open Passcode on the site, type one or press Make one for me (six digits), then copy the link and the passcode to send. Every address of the site (its own address, a claimed free name, a custom domain) then answers a plain Enter the passcode page with no site title or preview image, and tells search engines to stay out. A right passcode unlocks that browser on that address until the passcode changes or you press Sign everyone out. You can show the passcode again later, change it, or remove it. Your AI app can set, read back, or remove it too, after asking you first; a code is shown on the screen, never in chat.
Example. An architect puts a passcode on a proposal site and sends the link and the code to the client's board; nobody who finds the link without the code gets past the gate.
- Who
- Owners sharing a draft, a pitch, a client proposal, or a price list with a group they can hand a code to.
- Where
- Passcode on the site, on your sites page; or ask your AI app.
- Limits
- A passcode keeps out people who don't have it: search engines, link previews, and anyone who finds or is forwarded the link without it. Anyone you give it to can open the site and pass it on. It is not a login, it doesn't tell you who visited, and it doesn't make saved data private per person. Changing it signs everyone out. Pages people already opened may stay in their browser. Simple Host can still read the site. A passcode is 6 to 128 characters with no format rules. Wrong tries are limited per address (5 in three minutes, then a 15-minute wait) and per site (60 a minute, then 15 minutes); visitors already in are not affected. A site has a passcode or named viewers, never both. Taking a site offline or a take-down wins over the passcode. There are no end dates; take the site offline or delete it instead. Preview links and your own key or connected app bypass it.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxpartly
Simple Hack refuses passcodes; a small box offers them when each site has its own address and a sealing key is set, and refuses them where every site shares one address; Enterprise has access levels tied to real identity instead.
Named viewers: who can open the siteOpen a whole site only to the people you name by email; everyone else meets a sign-in page, and the list is checked on every request.
In Manage on the site, open Who can open and choose Only me and the people I name. Add people by the email they sign in with, comma separated; the viewer limit is always shown. Each row says whether that person has signed in yet. Remove asks first, naming the email. Every address of the site then shows anyone not signed in the automatic sign-in hop; someone signed in who is neither you nor named sees "You do not have access" with Use another email and Sign out. Your AI app can grant, list, and revoke viewers after asking you.
Example. A consultancy opens a client's portal to three named people at the client; a fourth colleague who is forwarded the link sees a sign-in page and no content.
- Who
- Owners of client portals, internal tools, pitch decks, and documents for a known set of people.
- Where
- Your sites page, Manage, Who can open; or ask your AI app.
- Limits
- At most 50 named viewers per site. Emails are matched exactly after trimming and lower-casing, with no folding of dots or plus tags. A new name works on their next page view and a removed one is refused on their next request; a suspended account never gets in. The owner always gets in, and the owner's key, the connector, and preview links keep working. Saved data on the site is closed to anyone not named, and files open as a direct link only, never inside another site. A site has named viewers or a passcode, never both. Removing the last viewer leaves the site open only to you; switching back to Anyone with the link keeps the list for later.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxpartly
Not on Simple Hack; a small box offers it where each site has its own address and visitors can sign in; Enterprise's level specific names people or teams from the company directory, pending until first sign-in.
Sign-in refused from listed countriesSign-in and sign-up from a country on the operator's list are refused, new and existing accounts alike; reading sites is unaffected.
The check runs before a sign-in code is emailed and before a Google sign-in leaves for the provider. The country comes from the request's address, resolved with the local address database on this server, never an outside lookup. From a listed country every emailed-code and Google sign-in or sign-up attempt is refused with "Sign-in isn't available from your region." No country is named in the refusal.
Example. A traveller opening a client's site from a listed country can read every page; signing in to their own account waits until they are back.
- Who
- Everyone, as a fact about where accounts can be made and signed in to.
- Where
- Nothing to do on the screen; it applies on every sign-in and sign-up.
- Limits
- A new account and an existing one are refused alike. An existing API key keeps working from anywhere, because using a key is not a sign-in, and viewing any site is never affected. A country the database cannot resolve is always allowed, and accounts issued by the operator are not checked. The list is a setting: the hosted services set their own, and a self-hosted install has none until its operator fills it.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
A self-hosted install lists its own countries and has none by default; Enterprise has no public self-serve sign-up to block.
Sign in with a passwordOn your own install, use a username and password without an email service or company identity provider.
The operator enables password sign-in. People can create accounts, or the admin can create them and give each person a temporary password. At first sign-in they choose their own password.
Example. A company runs an internal hackathon without an email provider. The organiser creates accounts from the Users panel.
- Who
- People using a self-hosted install.
- Where
- The sign-in card and the admin Users panel.
- Limits
- Passwords need 8 to 256 characters. The operator can turn public account creation off.
- Simple Hostno
- Simple Hackno
- Enterpriseno
- Small boxyes
Available on self-hosted Host and Hack installs; off on the hosted services.
Notifications
Back to the mapA signed call to your receiver or your AI app the moment a visitor writes, and the emails Simple Host sends you.
A webhook when a visitor writesA receiver URL gets a signed POST for record.added, record.changed, file.uploaded, and (Simple Host only) the site events, for one site.
Under Notifications, add an HTTPS receiver address for one site, with an optional label, an optional filter to one storage resource, and an optional custom header for your receiver. Simple Host then POSTs a signed body when a visitor adds a record or KV key (record.added), edits or deletes one (record.changed), or uploads a file (file.uploaded). The body carries the event id, time, site, storage, kind, preset, and the visitor's id or null, plus the table and row or the KV key with its fields, or the file's path, size, and type; visitor-written fields are marked as untrusted. Signatures follow Standard Webhooks (HMAC-SHA256 over the body, timestamp, and id), with matching svix headers. The signing secret is shown once at creation.
Example. A tutoring business points a webhook at n8n so each new booking row posts a message to their team chat with the lesson time.
- Who
- Anyone who wants Zapier, n8n, Hermes, OpenClaw, or their own receiver to act on new entries or uploads instead of someone checking the page.
- Where
- Settings, Notifications on your sites page, or on the team and organiser website screens in Simple Hack, and the REST routes documented at /docs/guides/notifications/.
- Limits
- Up to 10 subscriptions per site, about 60 events a minute and 5,000 a day per site, 7 days of delivery history. Five retries over about 10 minutes; sustained failure suspends delivery and emails you once. Public HTTPS addresses only, no redirects, a 5-second timeout. The visitor's email is never in the payload; strings over 2 KB are cut and bodies over 16 KB drop fields and say which. Owner writes never trigger one, and neither do writes to legacy saved data. Offline or taken-down sites skip deliveries.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack offers it on team and organiser websites; Enterprise has its own engine with the same signatures and controls; Simple Hack and Enterprise have the three record events, and site events are Simple Host only; a small box needs its sealing key set, which the installer does by default.
Site events for your receiver or agentA signed call when a version goes live, a domain check changes, someone asks for access, or a visitor signs in for the first time.
Under Notifications, tick the site events next to the record events, or name them in the events list over REST or in MCP events/subscribe. site.deployed fires when a version goes live through a deploy or an active-version change (rollback, roll-forward, publishing a saved preview), with version, previous_version, and via. domain.status_changed fires when a domain check records a status different from the previous one (pending, active, error) or a long-failing domain is released, with domain, status, previous_status, reason, and cert. viewer.access_requested fires when a person signed in with an email that is not on a named-viewers list reaches the no-access page, once per person per site per day. visitor.signed_up fires on a person's first sign-in on the site. The last two carry the visitor's id only. The same signatures, retries, and delivery history apply.
Example. A bookkeeping firm runs a named-viewers client portal and points viewer.access_requested at their team chat; when a client signs in from a work address that is not on the list, they add it before the client has to call.
- Who
- Site owners who want to know that a publish landed, a domain broke or recovered, a client wants into a private site, or a new visitor arrived, without watching the dashboard.
- Where
- Settings, Notifications on your sites page, the events list of POST /v1/sites/{sitename}/notifications, or events/list and events/subscribe over MCP.
- Limits
- Simple Host only for now; Simple Hack keeps the three record events and Enterprise has not ported them. An event about the site's owner is never sent. Payloads never carry a visitor's email, IP address, or user agent, or visitor-written text, and have no storage, kind, preset, or untrusted keys; the domain event's reason, cut to 1,024 bytes, may name the addresses the domain points at. A subscription's storage filter narrows record and file events only. The same per-site caps and 7-day history apply. A brand-new site's first version has no subscription yet, so there is no event for it, and a save with publish=false emits nothing.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Simple Host and the small box emit site events; Simple Hack keeps the record events until its port, and Enterprise has not ported them.
Test, pause, rotate, and read delivery historyEach subscription has a test send, pause and resume, secret rotation, and a list of recent deliveries.
From Notifications, send a test to confirm the receiver and signature, pause a subscription while you change the receiver and resume it afterwards, rotate the signing secret (the new one is shown once), and read the recent deliveries newest first. Resuming also lifts a suspension. On Simple Hack the team and organiser website screens have the same controls.
Example. An agency rotates a webhook secret after a contractor leaves and watches the delivery list confirm the next booking arrived signed with the new one.
- Who
- Anyone wiring up a receiver and checking it works, or recovering after a receiver was down.
- Where
- Notifications on your sites page; on Simple Hack, the team or organiser website's Notifications screen.
- Limits
- Delivery history keeps 7 days and shows up to 200 entries. After a rotation the old and new secrets both sign for 24 hours; rotating again ends that grace period. Test sends work for your own unexpired subscriptions, not for ones an AI app made. Suspension happens after at least 100 attempts with more than 95 percent failing in an hour, or three days of continuous failure, with one email to you. The secret and custom header value are never shown again in lists.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
On Simple Hack these controls are on the website screens only; the connector there lists and removes subscriptions.
MCP Events for your AI agentA connected app subscribes with events/subscribe to the record events, and on Simple Host only the site events, with signed delivery.
Ask the app; it calls events/list, events/subscribe, and events/unsubscribe. The app supplies its own secret and answers a signed challenge before the subscription is active. list_notifications and remove_notification let you check or remove a subscription from chat. Refreshing renews the expiry and resumes delivery, and a cursor lets the app replay retained events and learn when some were dropped.
Example. A founder's connected assistant subscribes to their waitlist site and tells them in chat each morning how many sign-ups arrived overnight.
- Who
- An AI app you have connected that wants to tell you when a quote request, order, or sign-up arrives.
- Where
- Ask the app; it calls
events/list,events/subscribe, andevents/unsubscribe.list_notificationsandremove_notificationlet you check or remove a subscription from chat. - Limits
- Each connected app gets its own subscription, tied to its sign-in. Subscriptions expire after 7 days unless the app refreshes or holds a longer-lived sign-in; the shortest explicit expiry is 5 minutes. The list the app sees redacts receiver paths. On Simple Hack, new team subscriptions stop at the submission deadline, membership loss removes them, and organiser delivery stops when the event ends. Event accounts and team keys cannot subscribe. A deploy-only key cannot subscribe.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Site events are Simple Host only; Simple Hack and Enterprise have the three record events. On Simple Hack the connector offers list and remove only; Enterprise binds the subscription to the connector grant and rechecks membership before each delivery.
A push notification on your phone or computer Off by defaultApple and Google push to a subscribed device, as a third kind of the same notification: you choose which events push and to whom.
A push subscription is a row in the same notification engine as webhooks and MCP Events, with the device's endpoint and keys in place of a receiver URL. Both the owner and a signed-in visitor may subscribe their own device site-wide or to one optional resource; a visitor's device is always scoped to record/file events only, never a site-wide or site-level one, and the privacy boundary that keeps it from ever reaching another visitor's data is enforced in delivery itself, not by a required resource. Per-resource controls choose who it reaches (the owner, the row's owner, both, or none) and, optionally, one named column shown as the push text; the default text names no row content. A visitor's device is only ever reached by an event about their own row, key or file, and nothing ever pushes back to whoever made the write, so your own save never pushes to you.
Example. A gym coach gets a push the moment a client logs a workout; the client gets a push when the coach replies, without either seeing the other's other clients.
- Who
- A site owner who wants a push on their phone the moment someone writes, and a signed-in visitor who wants a push when the owner replies to their own entry.
- Where
- Ask your AI app, or turn push on from the page with
SH.push.subscribe()once signed in. - Limits
- Behind an account allowlist (
WEB_PUSH_ACCOUNTS) while it is being tried out; off everywhere until an account is named or the flag is set to every account. iPhone needs Add to Home Screen first, iOS 16.4 or later. Push endpoints are personal data: never sent to AgentCat or exports, and removed on sign-out, viewer removal, account or site deletion, or erasure.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Simple Hack and Enterprise have not ported web push.
The emails Simple Host sends youSign-in codes and alerts, email-change notices, a failing domain, idle-site warnings, Submissions digests, and one suspension notice.
Simple Host emails you for a fixed set of reasons: the six-digit code when you sign in; the code to a new sign-in address and the notice to the old one when you change it; one short alert after each sign-in or app connection (switchable); a confirmation when you delete your account; a notice when a custom domain has been failing for a day; a warning before an idle site is removed and a notice when it is; a digest of new Submissions when you have asked for one (daily, or soon after each arrives, at most one email per name every 10 minutes); and one email if a notification receiver is suspended after sustained failure.
Example. A bakery owner gets a daily digest of the day's order-form entries and a one-off notice when their domain's DNS record was removed by mistake.
- Who
- Every account owner; this is the full list of what arrives in your inbox from Simple Host.
- Where
- Your inbox. Sign-in alerts are switched under Sign-in on your sites page; Submissions digests under Email me on the list; idle-site notices can be answered by reply.
- Limits
- One-time links in these emails carry their token after a
#, so it never reaches a server log. Sign-in alerts arrive at most once per browser or app a day and never for API key calls. Idle-site notices reply to support@simple-host.app. There are no marketing emails on this list.
- Simple Hostyes
- Simple Hackpartly
- Enterprisepartly
- Small boxyes
Simple Hack sends the sign-in and account emails; idle-site warnings and Submissions digests belong to Simple Host sites. Enterprise sends no sign-in emails, since the company's identity provider signs people in. A small box needs outgoing email set up.
A stale-skill notice to agentsAn agent publishing with an older copy of the skill gets a short notice in the reply saying a newer one exists.
The skill tells the API which version it is. When that version is older than the current one, API answers that are JSON objects carry a _notice field and an X-Skill-Notice header saying so. A plain API call that names no skill version gets nothing.
Example. A developer's agent publishes a client site with a skill from two months ago; the notice in the reply prompts it to fetch the current one before the next change.
- Who
- People whose AI agent uses the website-deploy skill, so it keeps up with changes without them noticing.
- Where
- In the API reply your agent reads; there is nothing to set up.
- Limits
- This is the only in-band notice Simple Host sends. Answers that are arrays stay bare, so lists never gain an extra element.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Notification secrets sealed at restWebhook signing secrets and custom header values are encrypted in the database, and the dashboard never shows them again.
Each subscription's signing secret, its previous secret during a rotation, and any custom header value are sealed with AES-256-GCM under a key the operator holds, bound to the row they belong to. Lists never return them; create and rotate show the signing secret once. On a server without the key, new subscriptions are refused, while existing ones can still be removed.
Example. A SaaS team puts an Authorization header on their webhook so their receiver can trust the call; the header value is stored sealed and never shown in the list.
- Who
- Anyone who cares what a copy of the database would reveal about their receivers.
- Where
- Nothing to do on the screen; it applies to every subscription.
- Limits
- Without the key, new subscriptions are refused; existing plaintext subscriptions keep delivering until a configured key lets the start-up sweep seal them. The sweep runs for at most 10 seconds at each start and skips rows it could not lock. Rotating a secret the server cannot read ends the previous secret's grace period.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise seals with its own separately named key; the standalone Simple Hack package and the small-box installer set the key by default.
Agents and MCP
Back to the mapHow an AI app or coding agent connects to Simple Host, what it may call, and what it is told while it works.
Simple Host in your chat appAdd Simple Host to Claude, ChatGPT, Claude Code or any AI app once with the one MCP address, then sign in and it can manage your sites.
Get started shows one address in a copy box filled from your own origin. Claude: Settings, Connectors, Add custom connector, paste it, Connect, sign in, Allow. ChatGPT: turn on Developer mode under Apps & Connectors, Create, paste the address as the MCP server URL, choose OAuth. Claude Code: claude mcp add --transport http simple-host <address>, then /mcp, Authenticate. Every other AI app pastes the same address. Each connected app is listed with the device it was connected from and when it was last used. A connected app's sign-in expires after 90 days without use.
Example. A consultant asks Claude to publish a one-page proposal for a client, then asks ChatGPT the next week to change the price table on the same site.
- Who
- Anyone who builds in a chat app rather than a terminal.
- Where
- Get started gives the one address to add (
https://simple-host.app/mcp); the dashboard's Connect your AI app card gives it again. Settings, Connected apps on your sites page lists them, with Disconnect. - Limits
- Works on the free plans of ChatGPT, Claude, and Grok. Sign out everywhere disconnects every app. Every app must use PKCE, so an app that expects a client secret cannot connect. Simple Hack uses
https://simple-hack.app/mcp; another server shows its own address, exact for its own origin.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise connects as a company's own custom connector, the company names the apps staff may connect, and sign-ins last 30 days.
Connected appsA list of every app signed in to your account, with where it was connected from and when it was last used, and a Disconnect button for each.
Each row names the app, the browser and system it was connected from (summarised as "Chrome on macOS", never the full browser string or an address), when it connected, and when it was last used. An app that read a shared site for you as a visitor also shows the last site it used. Disconnect ends that app's access at once; its upload and photo links stop working too.
Example. An agency owner sees a Codex connection from a laptop they no longer use and disconnects it without touching the Claude connection they use every day.
- Who
- Anyone who has added Simple Host to more than one app, or wants to check nothing unexpected is connected.
- Where
- Settings, Connected apps on your sites page.
- Limits
- Connections made before 27 September 2026 show no device. Sign out everywhere disconnects every app and every key in one step.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
On Enterprise the company names the apps its staff may connect.
Claude's plugin and connector directoriesHosted Get started links the plugin and directory steps alongside the MCP address; self-hosted shows only its address, no plugin mention.
The Claude plugin (Customize, Plugins, Discover) and connector directory listings for Simple Host and Simple Hack still exist, still work, and are still linked from hosted Get started, now alongside the MCP address in its own copy box, filled from the viewer's own origin; the ChatGPT plugin submission stays in review. (owner, 2026-11-05).
Example. A returning user who added the Claude plugin months ago keeps using it; someone new instead pastes the address Get started gives them.
- Who
- Anyone on Claude who wants the skills and the connection without a terminal.
- Where
- Hosted Get started links both; Claude's own connector and plugin directories also list Simple Host directly. A self-hosted instance's Get started links neither.
- Limits
- Only simple-host.app and simple-hack.app ever appeared in Claude's directories; a self-hosted instance never offered a plugin. This listing is not the onboarding path on either product's Get started page.
- Simple Hostyes
- Simple Hackpartly
- Enterprisepartly
- Small boxno
Simple Hack is in Claude's connector directory with its own toolkit; Enterprise ships its skills as a plugin download for its own instance.
The deploy skillTeaches your agent the whole job: sign you up, check a site, publish it, wire up saved data, and confirm the live page works.
The skill is a set of plain instructions your agent reads before it calls Simple Host. It covers sign-up, checking the files, publishing, setting up saved data and visitor sign-in, and opening the live page to confirm it works before saying it is done. It is served with this server's own addresses and limits written in, so an agent on another Simple Host server never reads simple-host.app's numbers.
Example. A bakery owner's coding agent reads the skill, publishes the menu site, adds a contact inbox, and opens the live page to check the form before reporting back.
- Who
- Anyone using a coding agent: this is the main way people use the service.
- Where
- Installed once from the Get started page, or from the setup panel on your sites page.
- Limits
- Your agent has to support skills. Chat apps without them (ChatGPT, Claude, Grok) add the Simple Host connector instead, from Get started.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack ships the same deploy skill in its toolkit; Enterprise has its own simple-host skill for its instance.
The planning skillHelps decide whether an idea fits here before any code is written, and says plainly when an idea needs a real server instead.
Your agent reads it when you describe an idea rather than a page. It maps the idea to what the service can do (saved data, visitor sign-in, uploads, passcodes) and explains who can read and write what. It then hands a brief to the deploy skill.
Example. A physiotherapist asks whether a booking page with a private client area is possible; the planning skill says yes, names the booking and portal presets, and hands over.
- Who
- Anyone starting something new and unsure it will work on a static site.
- Where
- Installed alongside the deploy skill.
- Limits
- It plans; it does not build. It hands over a brief for the deploy skill.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise has its own simple-host-builder skill.
The domain skillWalks your agent through connecting your own domain, tells you the two records to add, then checks the domain itself until it answers.
The agent attaches the domain to the site, relays the two records you add at your registrar (the address record and the TXT ownership record), and then opens your domain to see it answer. A free short name under simple-host.app needs no records at all. A reference inside the skill lists the steps for common registrars.
Example. A landscaping company asks their agent to put the site on their own domain; the agent names the two records, waits, and reports when the domain loads over HTTPS.
- Who
- Anyone attaching a domain, which is the step most likely to go wrong unattended.
- Where
- Installed alongside the other two.
- Limits
- It confirms by opening your domain rather than waiting on the badge.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Hack does not bundle the domain skill. Enterprise has no custom domains, so no domain skill.
A get-started page for whichever tool you usePick your AI and the page opens to the two or three steps that add Simple Host to it, with the address or command ready to copy.
One row per app: ChatGPT, Claude, Grok, GitHub Copilot, Meta Muse, Gemini, Mistral Vibe, Instinct, Claude Code, Codex, OpenClaw, and Hermes Agent, each checked against the live server. Chat apps get the connector address; coding agents get the one-line install. Meta Muse cannot register itself, so its row gives a short Client ID, meta-muse, that a phone keyboard cannot mangle.
Example. A photographer who uses Gemini opens the Gemini row, adds the custom app address, signs in, and asks for a portfolio page.
- Who
- Anyone arriving for the first time.
- Where
- Get started in the top navigation.
- Limits
- Works on the free plans of ChatGPT, Claude, and Grok; the coding-agent route needs a terminal. Manual installs are on the API page. Gemini's connected apps are available to personal Google accounts in the US.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Simple Hack's own Get started leads with running, joining, or judging an event; Enterprise shows the connect step on its dashboard's first run; another server shows its own connector address.
One line to installA single command installs the skills into your agent, on Mac, Linux, or Windows, with no accounts to link and nothing to clone.
Copy the command for your system from Get started and run it. It fetches the current skills and places them where your agent reads them. The same skills are published for the skills CLI as npx skills add vineetu/simple-host. The server tells an agent when its copy of the skills is older than the current one.
Example. A developer setting up Codex on a new laptop pastes one line and the deploy, planning, and domain skills are in place.
- Who
- Anyone with a terminal, and any agent that can run one command.
- Where
- Get started, and the setup panel on your sites page.
- Limits
- Some agents cache their skills: you may need to restart yours afterwards.
- Simple Hostyes
- Simple Hackpartly
- Enterprisepartly
- Small boxyes
Simple Hack installs its five skills through the skills CLI only; Enterprise ships its skills as a plugin download.
Guided setup for your specific toolsTick which tools you use and which operating system you are on, and it writes out the exact commands to run, with your key ready to copy.
The panel sits on your sites page and is visible only to you. Choose the tools and the system, and it prints the commands in order with your key filled in underneath, so nothing has to be typed by hand.
Example. A small studio adds Claude Code on a Windows machine for a second designer and copies the two commands the panel shows.
- Who
- Anyone setting up a second machine, or a tool that is not the obvious one.
- Where
- Set up your AI on your sites page, visible only to you.
- Limits
- Covers the tools listed there. Anything else uses the manual instructions on the API page.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Simple Hack has an events app instead of personal sites; Enterprise shows the connect step on its dashboard instead.
The connector's tool setMost apps see a short core of tools plus a finder that reaches the rest; ChatGPT, OpenAI, and Codex see every operation listed.
The connector has 58 website tools. Apps other than ChatGPT, OpenAI, and Codex are shown a core of 21 (19 building tools plus find_tools and run_tool); the agent asks find_tools for a job and calls what it returns through run_tool, and every tool still answers when called by name. ChatGPT, OpenAI, and Codex list every operation individually. read_site_file reads up to 10 files in one call and update_site can make a small find-and-replace edit without resending the whole file. The server's standing instructions stay under 2,000 characters in every edition.
Example. A clinic's agent asks for "who visited last week", finds site_analytics in one step, and runs it without the person naming the tool.
- Who
- Anyone whose chat app or agent works through the connector.
- Where
- Ask your AI app; the full list is on the API page.
- Limits
- A call with an argument the tool does not take gets the current schema back and asks you to refresh Simple Host in your app (ChatGPT keeps a connector's tool list from the day it was added). The 19 older saved-data tools removed on 10 October 2026 answer "no longer offered"; their pages keep working. There is no tool for changing your email, rotating your key, signing out everywhere, or deleting your account, by design;
who_am_iis the only account tool and it reads only.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack lists its full tool set on purpose, since one person is organiser, judge, and participant per event; Enterprise has its own 54 tools with the same core-of-20 finder.
Visitor tools for a shared siteYour AI app can read a site someone shared with you and add or change your own entries there, with only the rights a visitor has.
Three tools: visitor_read_site lists the sites shared with your email when no address is given, or reads one site's permitted data and page text; visitor_add_entry adds an entry; visitor_change_entry edits or deletes only your own entry where the site allows it. Each call gets a one-site visitor pass that ends when the call returns, and the site's viewers, passcode, and offline status are checked afresh each time. Other people's names, emails, and account IDs are left out; your own entries are marked mine. A site with a passcode takes it as an optional argument under the same lockout rules as the browser.
Example. A client asks Claude "what did the architect post in my portal this week" and gets the new entries without opening a browser.
- Who
- Anyone a site owner has shared a site with: a client reading a portal, a member filling a form, a judge reading a brief.
- Where
- Ask your AI app; the consent screen names visitor access when you connect.
- Limits
- You never gain owner powers this way, even on your own site. 200 write attempts per person and site per day across apps. Page text is cut at 256 KiB. Changes made through an app leave a marker naming the app in the site's data history. A passcoded page still needs the passcode to read page text.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Simple Hack keeps browser sign-in for visitors and offers no visitor tools; Enterprise has none yet.
Personal details stay out of tool resultsConnector results leave out emails, names, and account IDs unless the owner asks for one submitter by name.
who_am_i returns your email only when the agent asks for it. Visitors in saved data appear as opaque references scoped to one site, so a count of bookings or a read of entries never resolves anyone's email. Only an owner's request to identify one submitter calls storage_visitor_emails, with the references for that entry alone. Viewer changes return only what changed, and signed download and preview links carry no readable internal IDs. The same rules cover Simple Hack results.
Example. A tutor asks "how many sign-ups this week" and gets a number; later they ask "who booked Tuesday 4 pm" and the agent looks up that one person.
- Who
- Everyone whose details pass through a site: visitors, viewers, and the owner.
- Where
- Built into every connector call; nothing to switch on.
- Limits
- Site names, saved-data key names, and your own conversation text are ordinary data and are not hidden from your app.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise names colleagues by username because the caller manages that access.
Agents can find Simple Host on their ownThe homepage reads as markdown, standard discovery files describe the connector and API, and the hosted server is in the MCP registry.
Ask the homepage for text/markdown, or open /index.md or /llms.md, and you get the same content as the page in plain text; /llms.txt is a short linked quickstart with recipes. Standard well-known files describe the server: an MCP server card, an agent capability card with live tool descriptions, an agent resource document linking the skills index and the API specification, and an API catalog linking the OpenAPI files. The homepage carries Link headers to the markdown, the catalog, the sitemap, and OpenAPI, and the sitemap is dated from the build. The hosted server is listed on registry.modelcontextprotocol.io as app.simple-host/mcp, verified by DNS, and also answers at https://mcp.simple-host.app/mcp with public DNS records that point agents to it.
Example. A company's internal agent is told "find a place to publish this" and reads simple-host.app's server card and llms.txt without a human copying anything.
- Who
- Agents and crawlers arriving without a person's instructions, and people writing their own integrations.
- Where
/llms.txt,/index.md, and the/.well-known/files; nothing to set up.- Limits
- The sitemap lists the brand's own pages only, never anyone's site or handle. The registry listing and the
mcp.address exist for simple-host.app only; another server names itself in its own discovery files.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Simple Hack publishes its own branded cards; Enterprise and the small box serve their own cards for their own address, with no mcp. alias and no public registry listing.
Connector usage analyticsThe hosted service records which connector tools are called and how they went, with secrets, files, and visitor emails removed first.
On simple-host.app each completed tool call sends one event to AgentCat: the tool name, how long it took, whether it failed and the short error code, the app's name (Claude, ChatGPT, Codex, Cursor, or other), a keyed hash in place of the account, the tool's arguments and result (each cut at 8 KB), and the agent's stated intent (cut at 2,048 characters) when the app supplies one. Before sending, passcodes, keys, tokens, signed links, and file contents are replaced, and visitor emails become references. AgentCat removes personal identifiers again before storing. The privacy policy discloses it.
Example. The operator sees which tools agents reach for most and where calls fail, and tunes the tool set and its hints from that.
- Who
- The service's own operator, to see which tools agents reach for and where calls fail; it is not a feature anyone switches on for a site.
- Where
- On for simple-host.app only; disclosed on the Privacy page.
- Limits
- Off unless a project id is configured. Request headers, screen metadata, and the address you connect from are never sent. Site names, saved-data key names, and conversation text are sent. The passcode screen sends neither arguments nor results.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
Simple Hack, Enterprise, and self-hosted servers are not enrolled and send nothing.
A refused call says what to do nextWhen a tool call is refused, the agent gets the reason, a short code, and one recovery hint chosen for that code.
Every refusal carries the server's message, its code (for example site_exists, domain_taken, site_quota_reached, sign_in_required, key_expired), and one hint matched to that code; the HTTP status picks the hint only when there is no known code. The API returns the same codes, so a skill and a connector see the same thing. An unknown API path or wrong method gets a JSON answer with a link to this server's own reference. A signed-out connection gets the reconnect steps in the error itself.
Example. An agent tries to create studio and is told the name is taken, with the hint to pick another or reuse the existing site, instead of guessing.
- Who
- Anyone whose agent hits a taken name, a missing sign-in, a quota, or a suspended site mid-task.
- Where
- Your agent sees it; a good agent tells you in plain words.
- Limits
- Pages people visit still get HTML error pages, never JSON.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
The agent asks before anything irreversibleEvery skill and the connector tell the agent to ask you before a site goes online, before deleting, and before widening who sees data.
Before a new site goes online for the first time the agent asks once, naming the site, its address, and that anyone with the link can open it. It always asks before deleting a site or data, making private data public, changing who can see or save, connecting a domain, rolling back, or taking a site offline. Updates you asked for in the same conversation go ahead without a second question. The skills, llms.txt, and the connector's own instructions all say the same.
Example. An agent updating a restaurant's prices does it straight away, but asks before switching the reservations list from private to public.
- Who
- Anyone letting an agent work on their sites without watching every step.
- Where
- Built into the skills and the connector instructions.
- Limits
- Whether the question reaches you depends on your app following its instructions; the server itself does not block the call.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Out-of-date agents are told to updateIf your agent works from an old copy of the skill, the service tells it so as it works, rather than letting it fail later.
A skill names its version on each call. When that version is older than the current one, the answer carries a short notice asking the agent to refresh its skills, and a matching response header. A plain API call that names no skill gets nothing. It is the only notice the service puts into a response this way.
Example. A marketing agency's agent installed in spring publishes fine in autumn but is told to update, and the one-line install brings the current recipes.
- Who
- Anyone who installed the skills months ago and forgot.
- Where
- Your agent sees it and should mention it to you.
- Limits
- Whether you hear about it is up to your agent: nothing is shown on any screen.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise refuses an obsolete skill outright instead of warning.
Full API referenceRead task guides, search the docs, and browse this server’s API at /docs/.
Open Docs, choose a task guide, or search. Open API reference for the routes and schemas.
Example. A startup wires its own build pipeline to publish a release notes site from CI using the reference and a deploy-only key.
- Who
- Developers, and agents that prefer a specification to prose.
- Where
- /docs/ on this install; /docs/api/ for the API reference.
- Limits
- A few internal and download addresses are not listed there. Older saved-data endpoints that existing sites still use keep working but are no longer listed.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Owner dashboard
Back to the mapThe screens where you manage your sites yourself, and the screens your AI app can draw inside a chat.
Your sites pageAt simple-host.app/your-handle, one page manages every site: address, versions, domain, saved data, analytics, keys, and connected apps.
Each site card shows Open and Manage. Manage is one menu: List on my profile, offline, passcode, who can open, versions, storage, rename, domain, download, keep for good, then Delete last in red. Delete asks in a dialog that names how long Recently deleted keeps it; lowering kept versions asks you to type how many go; opening a storage preset to more readers asks first. Three tabs separate Sites, Analytics, and Settings. Sites opens by default with Your sites and Recently deleted when it has items. Analytics starts with totals and the range selector. Settings holds Your address with Home page, Your showcase, Sign-in, Password when available on a small box, Connected apps, Keys, Notifications, Address families when available, and Your data, with Delete account last. Empty Connected apps offers a Connect your AI app link. Tab and section links open the right panel; site-control links open Sites. All three tabs fit one row on phones. Sites sort by Recently updated by default, with Recently created, Name, and Most viewed (people, 30 days) as alternatives, remembered per browser. Every question is asked in the page itself, never in a browser pop-up, so an AI browsing agent can read and answer it.
Example. A design studio with twelve client sites searches the list, opens Manage on one, rolls it back a version, and checks the week's visitors on the Analytics tab.
- Who
- Every owner with a handle; signing in takes you here.
- Where
simple-host.app/your-handle; the header's Your sites link.- Limits
- Search appears from 10 sites. Classic lists and page data fold into one closed section.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Simple Hack's header shows Your events instead; Enterprise has its own dashboard whose Manage menu offers its own actions (viewers, uploaded files, activity, teams) with a 30-day Recently deleted window.
The page remembers who you areAfter one sign-in the browser remembers your handle, so Your sites opens your own page directly without a flash of the public view.
After you sign in, the browser keeps your handle. The header's Your sites link goes straight to your page, and /dashboard hops there without waiting. On your page a short "Loading your sites" state hides the public gallery until the server confirms you are the owner, then your controls appear. The page asks the server for your account and your sites once each, in parallel.
Example. A caterer opens simple-host.app on their phone between events and lands on their own sites in one tap.
- Who
- Anyone who returns to the dashboard often.
- Where
- Automatic after sign-in.
- Limits
- Anyone else, or a stale memory, gets the public view. A suspended account is sent to the main dashboard with the reason. If the server does not answer within 8 seconds the public view shows. Signing out forgets the handle.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Main dashboardThe older screen at /dashboard: sign in, start a new site, see your sites with a Manage link, and sign out everywhere.
Sign in with an email code, Google, or by pasting a key. An account with a handle is sent on to its sites page; reached with New site from there, this screen lists your sites with a Manage link back. It holds Sign out everywhere, which rotates your key and disconnects every app and every browser at once. Its site list sorts by Recently updated, Recently created, Most people, Most bots, Most traffic, or Name.
Example. After a laptop is lost, a shop owner signs in from another device and presses Sign out everywhere; every connected app has to sign in again.
- Who
- Anyone signing in, and accounts without a handle.
- Where
/dashboard, and New site from your sites page.- Limits
- Accounts without a handle, and the admin tab, keep the full set of controls here.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Enterprise's /dashboard is its own screen: keys, sites, teams, shared with me, usage, and Recently deleted, with the connect step on first run.
Add photosPick up to 30 photos from your device, name them, and save once; small copies go into the site with camera and location details removed.
Choose Add photos on a site, pick photos, give them names, and save once. Each photo is shrunk on your device to at most 1600 px and saved as WebP (usually under 300 KB) into images/ in a new version. Camera and location details are removed on your device before anything is uploaded. JPEG, PNG, WebP, AVIF, still GIF, BMP, HEIC, and TIFF are accepted. When you finish, copy the addresses or the ready-made message back into your chat. From a chat, your AI app can hand you a photo link that opens this page for one site without signing in.
Example. A cafe owner's agent publishes the menu, sends a photo link, and the owner adds twelve dish photos from their phone's camera roll in one go.
- Who
- Anyone whose page needs their own photos: a menu, a listing, a team page.
- Where
- Add photos on a site card or in its Manage menu, or a photo link from your chat.
- Limits
- 30 photos per save, 80 MB per input file, 50 megapixels, 20 seconds to decode each. Names use lowercase letters, digits, and hyphens, at most 60 characters; a repeat name gets
-2,-3, and so on. A photo link lasts 60 minutes and allows 10 saves; it stops working when you sign out or disconnect the app. When the server is busy it answers "Busy, try again in a moment" instead of queueing. After an uncertain save the page offers Check previous save rather than uploading twice.
- Simple Hostyes
- Simple Hackno
- Enterpriseyes
- Small boxyes
Enterprise has its own photo page with company sign-in and no photo link; Simple Hack keeps archive uploads only.
Page tools for a browsing agentYour sites page and Add photos offer browsing agents tools to list sites, open one, set List on my profile, and add photos.
Once the page confirms you are the signed-in owner, it registers tools with the browser's model context. On your sites page: list your sites, read a site's link, open a site, and set List on my profile (marked consequential, so a compliant agent asks before changing it). On Add photos: list your sites, choose the site for photos, and add photos through the page's own save, waiting for the real result.
Example. A consultant tells their browser agent "turn List on my profile off for the Q3 report site"; the agent asks once, then does it on the page.
- Who
- Anyone driving the dashboard with an AI browser agent rather than clicking.
- Where
- Automatic on your sites page and Add photos when you are signed in.
- Limits
- A signed-out visit, an admin on someone else's page, and a photo link register nothing. Add photos through the tool is capped at 30 photos with the same size limits as the picker. Your browser has to support WebMCP.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxyes
Screens inside the chat Off by defaultIn apps that support MCP Apps, Simple Host can draw a photo picker, a My sites list, a weekly dashboard, and a passcode screen in the chat.
Five screens. The photo picker opens when the agent calls for photos: pick, shrink, and save into images/ without leaving the chat. My sites lists and searches your sites; from it the dashboard shows weekly person visitors and the latest three inbox or records entries. The passcode screen shows, copies, sets, or generates a site passcode so the passcode itself never passes through the model; an app without screens gets a link that opens the Passcode dialog on your sites page instead. Screens follow the app's light or dark theme.
Example. A florist asks Claude for product photos on the shop page, picks eight from the picker in the chat, and the site updates in one version.
- Who
- Owners working in Claude or another app that renders MCP Apps screens.
- Where
- Inside the chat, in apps that render MCP Apps screens; turned on per account.
- Limits
- Off by default; each screen is enabled for everyone or for named accounts. The site preview card stays off in production because sites refuse framing. My sites shows fixed tiles, not live thumbnails. A passcode screen session lasts 10 minutes and is used once. Calls made through
run_toolget the plain photo link, never the picker. ChatGPT follows the same standard, so no extra metadata is needed.
- Simple Hostyes
- Simple Hackpartly
- Enterpriseyes
- Small boxyes
Simple Hack has its own screens (next entry) and no photo picker, preview, or passcode screen; Enterprise has the picker, My sites, and dashboard screens too; small-box installers forward the switches, default off.
Simple Hack screens inside the chat Off by defaultOn Simple Hack the same kind of screens show a team's sites and weekly dashboard, a judge's queue and scoring, and an organiser's overview.
My sites marks your selected team, lists your other current teams, and includes event websites you organise; a selected team's dashboard shows weekly person visitors, seven daily values, and the latest three inbox or records entries. The judge app is one screen with four views (accept the invite, queue, score, rubric), opened by one tool, and every judging action keeps its plain tool underneath. The organiser app has overview and stage, people and applications, and the judging dashboard, opened by its own tool and shown to organisers only.
Example. A judge at a weekend hackathon opens the queue in Claude, scores three teams against the rubric, and declares a conflict on a fourth.
- Who
- Participants, judges, and organisers working in an app that renders MCP Apps screens.
- Where
- Inside the chat on simple-hack.app connections, in apps that render MCP Apps screens; turned on per account.
- Limits
- Off by default; each screen is enabled for everyone or for named accounts. Listed only for a connection that declared screen support, and never for ChatGPT, OpenAI, or Codex. No photo picker or preview on Simple Hack. Custom event websites show entries but no visitor chart. The frame never selects a team or receives a key. The organiser app's teams, entries, results, and event page views are later phases.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
The self-hosted Simple Hack package with company sign-in gets My sites and the dashboard; the judge and organiser apps are hosted Simple Hack.
One theme that follows your systemEvery page follows your device's light or dark setting until you pick Match my system, Light, or Dark once in the header.
With nothing picked, pages follow your system setting and change live when it does. The header's theme button offers Match my system, Light, or Dark; the choice is kept once in the browser and applied to every page before it paints, other open tabs included. Chat screens follow the chat app's theme instead.
Example. A developer who works in dark mode opens the dashboard at night and the sign-in, sites, and analytics pages are all dark without a toggle.
- Who
- Everyone who opens any Simple Host page.
- Where
- The theme button in the header of any page.
- Limits
- Your published sites are untouched; they look however you built them. Your personal page and site addresses are separate origins, so they follow the system until you pick a theme there too.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise pages are light only, with no toggle, to sit inside a company's own look.
The product iconSimple Host's mark is a hand-drawn s.h monogram with a teal period on a cream tile; Simple Hack's is a red dot in an inked frame.
The same four icon files serve each product's own mark: the SVG favicon, a 32 px PNG for browsers that skip SVG, a multi-size .ico, and a 180 px touch icon. Every page links them with a shared cache key, so a new mark reaches browsers that cached the old one. The Claude and ChatGPT plugin icons carry the Simple Host mark.
Example. A client bookmarks their portal's management page and recognises the s.h tile in the bookmark bar.
- Who
- Everyone who sees a tab, a bookmark, a home-screen icon, or the plugin listing.
- Where
- Browser tabs, bookmarks, home screens, and the plugin directories.
- Limits
- Self-hosted and small-box installs carry the Simple Host mark, as they carry its header wordmark.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise serves the same Simple Host exports on its app host.
Showcase and home page
Back to the mapWhat opens at your handle's address: a public list of your sites you can pin, order, and caption, or one site you choose as home.
A public page listing your sitesYour handle has its own page showing your public sites, https://<handle>.simple-host.app/, so you can share one link instead of five.
The page lists your public sites, each linked at its own address, with your bio above them in the order you set. Old sites.simple-host.app/<handle> links redirect to it. If you chose a site as your home page, that site opens at the address instead.
Example. A photographer shares one link with a gallery; it lists her wedding portfolio, her price list, and a client proofing page.
- Who
- Anyone showing a body of work: a portfolio, a course, a set of demos.
- Where
- The link is shown to you on your sites page, under Your public showcase.
- Limits
- Only sites with List on my profile on appear. Sites with it off, sites with a passcode, offline sites, taken-down sites, deleted sites, and every site of a suspended account are left out, even when pinned.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Enterprise has an owner index page that needs company sign-in and shows the owner everything, others only listed sites; Simple Hack has no personal sites.
Pin, order, and a short bioPin the sites you want seen first, set the order of the rest, and write a plain-text bio that sits above them.
In Your showcase, save a short plain-text bio, pin projects and set their order. Pinned projects come first, then smaller order numbers, with creation time breaking ties. Sites with List on my profile off stay off the profile even when pinned. The page and the public feed use the same order. Connector set_bio and set_showcase_site; REST GET/PUT /v1/me/bio and GET/PUT /v1/sites/{site}/showcase.
Example. A product studio pins its two flagship apps, orders the client work beneath them, and writes one line about what it takes on.
- Who
- Anyone whose showcase is a first impression: a freelancer, a studio, a founder with several products.
- Where
- Your showcase on your sites page, or ask your AI app.
- Limits
- The bio is plain text and defaults to 280 characters; the operator can set it anywhere from 1 to 2000. Order numbers run from 0 to 1,000,000. Full owner sign-in or the connector only; deploy-only keys cannot change it.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
Simple Hack has no personal sites; Enterprise's owner index page needs company sign-in.
A live public feed of your sitesA custom home page can read your public showcase as JSON, with bio, titles, addresses, and the order you set, no key needed.
GET /v1/u/{handle}/showcase.json returns your bio and your public sites: name, title and description from the deployed page where visible, address, last update, pinned, and order. It needs no key, allows cross-origin reads from any page, and matches the showcase page exactly. A home page you chose can fetch it from the apex and render your projects live. The website-deploy skill has a short example.
Example. A founder's custom home page shows a card per product; when a new product site goes public it appears on the home page within half a minute.
- Who
- Anyone who builds their own home page and wants it to list their projects without editing it each time one ships.
- Where
- Ask your AI app to build the home page against the feed; the address is the one above.
- Limits
- Public sites only, the same filter as the showcase page. Cached for 30 seconds and rate-limited per owner and per reader address, with the public-read settings. Returns nothing for Simple Hack event accounts.
- Simple Hostyes
- Simple Hackno
- Enterprisepartly
- Small boxyes
On Enterprise the feed needs company sign-in and applies the owner index page's visibility rules.
Traffic and analytics
Back to the mapHow many people read each site, counted on the server from the web log, with crawlers and the service's own monitoring kept apart.
People, bots and monitoring counted apartEvery visit lands in one of three groups (People, Bots, Infra) and the groups are never added into one total.
The server reads the web server's log and sorts each page view into People, Bots, or Infra. The three figures sit side by side under each site and are never summed. A fourth figure, Earlier, is history from before the split; nothing new ever lands there.
Example. A consultancy's client-facing proposal page shows 40 people and 900 bots in a week, so the owner knows the proposal was read by about 40 humans, not 940.
- Who
- Anyone who has ever been briefly delighted by a traffic number that turned out to be crawlers.
- Where
- The numbers under each site on the main dashboard.
- Limits
- A crawler that hides itself well is counted as a person. The split errs that way on purpose: better to overstate people slightly than to hide real readers.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise keeps an in-app access log with daily views (bots split) and top pages for owners.
People is the audience numberWhen you want one figure for how a site is doing, it is People; everything else on the panel is context.
People is the first, highlighted figure under each site, and the only figure the Analytics tab uses. It is the count of page views by visitors the server classed as human.
Example. A restaurant owner checks the menu site after a local newspaper mention and reads the People figure for the week to see whether the mention brought readers.
- Who
- Everyone with a site they care about.
- Where
- The first, highlighted figure under each site on the main dashboard; the only figure used on the Analytics tab.
- Limits
- It counts page views. Clicks and scrolls are not counted. Images, stylesheets, and downloads are not counted as visits.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise keeps an in-app access log with daily views (bots split) and top pages for owners.
Your own visits are not countedOpening your own site from a device you use while signed in does not add to People; those visits are filed as yours.
When you use the dashboard or the owner app, or sign in on your site as yourself, the server remembers that device's hashed address for 30 days. Page views of your sites from it are filed as your own, in their own figure, instead of as People. They still count as activity, so a site you keep opening is never treated as idle.
Example. A bakery owner opens the menu page several times a day to check prices and photos. Those visits land under You, and People shows the customers who read the menu.
- Who
- Anyone who checks their own page often and wants People to mean other people.
- Where
- A You figure on the site's analytics page when there is any; views on the site list in the API, counted by people only; the connector says it in words in list_sites, get_site and site_analytics.
- Limits
- A visit from a device you never used while signed in still counts as a person. Other people behind the same address as a marked device are not counted while the mark lasts, which is 30 days from the last time you were seen there.
- Simple Hostyes
- Simple Hackpartly
- Enterpriseno
- Small boxyes
On Simple Hack a team site belongs to the event, so a member's visits are not the site owner's visits. Enterprise counts from its own in-app log (see PARITY). The small box has it when ANALYTICS_LOG is set.
The service's own monitoring is kept outThe service checks every site is up about twice a minute; those hits sit in their own Infra figure, out of the way.
Uptime checks hit every site roughly twice a minute, which is thousands of requests a day per site. They are classed as Infra and shown as a muted figure only when there is any. The hourly chart leaves Infra out entirely.
Example. A product page nobody has shared yet shows 'no visits yet' rather than a few thousand monitoring hits dressed up as an audience.
- Who
- Anyone comparing this month with last month and wondering why a dead site has traffic.
- Where
- The muted Infra figure on a site's numbers, shown only when there is any.
- Limits
- A site with only monitoring traffic is shown as 'no visits yet'. Infra is left out of the hourly chart entirely, because it would flatten everything real.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise counts from its own in-app access log and has no monitoring figure.
A real count of distinct visitorsThe visitor figure is how many different people came over the whole period; someone who visits on five days counts once.
Visitors are told apart by network address, hashed with a salt before it is stored. The figure for a period is the number of distinct addresses over that period, so it is never the daily figures added up.
Example. A pitch deck site sent to twelve investors shows 9 visitors over the month, which answers 'how many of them opened it' better than a page-view count would.
- Who
- Anyone judging reach rather than activity.
- Where
- Next to People under each site, and as the visitors total on the Analytics tab.
- Limits
- Visitors are told apart by network address, never by a tracking cookie. So an office on one connection reads as one person, and a phone moving from wi-fi to mobile reads as two. These are inherent and will not be fixed.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
The shape of the last monthA small line per site showing day-by-day readership, so a spike or a decline is visible at a glance.
Each site row on the Analytics tab carries a small line of daily People counts for the chosen period. It is drawn to show shape, so a launch spike or a slow decline reads without opening anything.
Example. An agency with eight client sites scans the lines on one screen and sees which client's launch week actually brought readers.
- Who
- Anyone checking whether something they shared landed.
- Where
- Next to each site on the Analytics tab of your sites page.
- Limits
- The line plots people only. It has no scale or hover figures: it shows shape only.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise shows daily views on its dashboard's Visitors view.
The last 24 hours, hour by hourA short bar chart of the last day, people stacked above bots, so you can see whether something is happening right now.
Under each site's numbers on the main dashboard a 24-bar strip shows the last day. People are stacked above bots in each hour. Figures update every few minutes.
Example. A founder posts a product page on a forum at lunch and watches the afternoon bars fill in.
- Who
- Anyone who has posted a link somewhere and wants to watch.
- Where
- The 24h strip under each site's numbers on the main dashboard.
- Limits
- Hours are in UTC, not your local time. Monitoring traffic is excluded from this chart.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Older traffic shown as EarlierTraffic recorded before 9 August 2026 predates the people-versus-bots split and is shown as its own Earlier figure.
Records from before 9 August 2026 are real and still shown, as an Earlier figure on the site's numbers. They are never guessed into the People or Bots columns. Hover the figure for the explanation.
Example. A portfolio site from spring 2026 shows a large Earlier figure and a smaller People figure; the owner compares People only against a site made in autumn.
- Who
- Anyone with a site older than that comparing it with a newer one.
- Where
- An Earlier figure on a site's numbers, shown only when there is any. Hover it for the explanation.
- Limits
- It can never be broken down: the original records are gone. Those months are also inflated by monitoring, which is exactly why they are kept separate.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
Only sites on simple-host.app have records from before 9 August 2026.
Numbers on every site cardEach site on the main dashboard carries its last-30-days figures and its 24-hour chart, so there is no separate report to open.
Every site card shows People, Bots, Infra (when any), Earlier (when any), visitors, and the 24-hour strip. The figures cover the last 30 days and load as you scroll.
Example. A small agency's owner opens the dashboard on Monday and reads last month's readership for every client site without clicking into any of them.
- Who
- Anyone scanning several sites at once.
- Where
- Under the site name on each card, main dashboard.
- Limits
- Fixed at 30 days here. They load as you scroll, so a card below the fold may be blank for a moment.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
The Analytics tabA dedicated screen with your totals across every site and one row per site, most-read first.
The Analytics tab on your sites page shows your People and visitors totals across every site for the chosen period, then one row per site with its figures, its daily line, and its top pages and referrers. Rows are ordered by People.
Example. A freelancer with a portfolio, a rate card, and three client pages reads one screen to see where the month's readers went.
- Who
- Anyone who wants the whole picture rather than site by site.
- Where
- The Analytics tab on your sites page.
- Limits
- This screen shows people only: bots, monitoring, and Earlier are not shown here at all. For those, use the site cards on the main dashboard.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise has a Visitors view on its dashboard with daily views and top pages.
Top pages and where visitors came fromFor each site, the pages people read most and the sites whose links brought them, for the period you chose.
Views by people are counted per page of the site (query string and fragment dropped, /index.html folded into /) and per referring domain, per day. The top 20 of each are listed under the site on the Analytics tab and on the site's full analytics page. Your AI app gets the same lists from the site_analytics tool.
Example. A product page gets 600 readers in a day; the referrers list shows news.ycombinator.com and the pages list shows which pricing page they went on to read.
- Who
- Anyone whose site suddenly got busy and wants to know which page, and where it was shared.
- Where
- Top pages and referrers under each site on the Analytics tab, and on that site's full analytics page.
- Limits
- People only, top 20 of each. A referrer is its domain (such as news.ycombinator.com), never the full address it came from; links from the site itself are not counted. A site keeps at most 200 pages and 100 referring domains a day; further new ones that day are counted as
(other), so random paths or referrer spam cannot grow the list. Page paths are kept to 200 bytes.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise lists the top 10 of each from its in-app access log; another site on the same install appears as *.<base>.
Choose the periodSwitch the whole Analytics tab between the last 7, 14, 30, or 90 days.
A selector at the top of the Analytics tab changes every total, row, line, and top-pages list at once. It opens on 30 days.
Example. A conference organiser compares the 7 days around ticket launch with the 90-day view to see whether interest held.
- Who
- Anyone checking a launch week against a normal one.
- Where
- The 7d, 14d, 30d, 90d selector on the Analytics tab. 30 days to start.
- Limits
- Days are UTC calendar days, so today's figure is a partial day. Around 13 months of history is kept at most.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Busiest sites firstYour sites are ordered by how many real people read them, so what is working is at the top of the list.
The Sort selector above the site list on the main dashboard orders sites by People in the last 30 days. You can also sort by bots, by all traffic, or by name. The Analytics tab is always ordered by People.
Example. A studio with twenty landing pages sees the three that bring readers at the top instead of whichever it made first.
- Who
- Anyone with more than a handful of sites.
- Where
- The Sort selector above the site list on the main dashboard. The Analytics tab is always ordered this way.
- Limits
- Sites with no traffic sort last, not alphabetically among the rest.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Nothing is added to your pagesThere is no tracking script, no tag to install, and no cookie banner to add; counting happens on the service's side.
The server reads its own web log (nginx or Caddy) and turns it into hourly and daily counts. A visitor's address is hashed with a salt before it is stored. Country comes from a local address database, so no visit is ever sent to an outside service.
Example. A health clinic's information site gets readership figures without adding a third-party tracker to pages its patients read.
- Who
- Everyone: you get the numbers without your visitors paying for them.
- Where
- Automatic for every site.
- Limits
- No pages-per-visit or sessions. Where visitors came from is shown by domain only. Figures update every few minutes, not instantly.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise counts from an in-app access log instead of the web server's log; there is no client script there either.
Where your readers arePeople, by country, for each site, so you can tell whether a site is reaching the place it was made for.
Open a site's full analytics page from its name on the main dashboard; the country table is at the bottom, ordered by people. Country is looked up on this server from a local address database, refreshed on a schedule.
Example. A Lisbon tour company checks that its English-language page is reaching the UK and Germany rather than only Portugal.
- Who
- Anyone with a site aimed at a city, a country, or a language.
- Where
- Open a site's full analytics from its name on the main dashboard; the country table is at the bottom.
- Limits
- Country only: no city, no map. Ordered by people; bots and infrastructure are shown separately. A visitor whose country cannot be resolved is shown as unknown.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise has no country breakdown; its sites are read inside a company.
Analytics for your AI appYour AI app can read a site's figures with the site_analytics tool, so you can ask how a site did without opening a screen.
Ask your AI app how a site is doing. The site_analytics tool returns the period's People, bots, and visitors, the daily series, the top 20 pages, and the top 20 referring domains for the number of days you name. The same figures are available to scripts through the analytics API in the reference, and a listing call gives the figures for every site at once.
Example. An agency asks its assistant every Friday for last week's readers across its client sites and pastes the answer into the client update.
- Who
- Anyone who manages sites from a chat app or an agent and wants the numbers there.
- Where
- Ask your AI app; also in the API reference for scripts.
- Limits
- People only in the top lists. Days are UTC calendar days. The daily chart series travels outside the conversation text so it does not swamp the chat; the app shows it where it can.
- Simple Hostyes
- Simple Hackyes
- Enterprisepartly
- Small boxyes
Enterprise offers the same through its own site_activity tool and dashboard.
Previews do not count as visitsA request that carries the _sh_preview=1 marker is left out of the visitor counts, so checking your own site does not inflate them.
The site preview inside the owner app adds _sh_preview=1 to its requests. The server still serves and logs them, and still counts them as traffic, but they are not counted as visitors.
Example. A designer reloads a client's draft page twenty times while checking spacing; the client's People figure stays at what real readers produced.
- Who
- Anyone who opens their own site to check it and does not want to count as a reader.
- Where
- Automatic in the owner app's site preview; add
_sh_preview=1to the address to use it by hand. - Limits
- Anyone can add the marker, so a visitor who wants to stay out of the count can; this is an accepted, low-impact limit. Traffic (bytes and requests) still counts, and later unmarked requests from the same visit can count as visits.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
On Simple Hack the owner-app preview is off; the marker itself still works on requests.
Admin and operations
Back to the mapWhat the operator can see and do, the rules every account and visitor meets, and how to run a copy of the software yourself.
The operator consoleOne signed-in page where the operator sees accounts, sites, and API traffic, and acts on any site or account.
The console has six tabs. Overview: accounts, new in 7 and 30 days, live sites, storage and disk used, the latest sign-ups with their source, the 10 biggest websites, and network use for the month (bytes in and out against the allowance, bytes served per website, split pages and API). Users: a searchable table with each person's sites and sign-up source, New key (replaces a participant's keys with one new key, shown once), Suspend or Re-enable, and Delete (the same erasure a person gets from Delete my account). Sites: every site in one sortable table (recently created, recently updated, size, most views by people in 30 days), 50 rows a page, with a menu per row for Open, Analytics, Versions, Data (lists, rows, CSV), Connect or Disconnect domain, Take down or Restore, and Delete. API: calls per day by kind, new accounts and sites per day with the change against the previous period, a world map shaded by API calls per country with the top 10 beside it, then today's calls, callers, errors, routes. Moderation: taken-down sites with Restore, an idle-site dry run (would warn, would remove), and a saved-data watch. Tools: issue participant accounts in bulk and download entries. The operator can read any site's analytics and download every site with its data as one archive. Every search box takes several words, all must match, and a -word hides rows that match it.
Example. An event organiser running their own box issues forty participant accounts before a hackathon, then watches the API tab fill as teams start publishing.
- Who
- Whoever runs the service: the operator of simple-host.app, an event organiser on their own box, or company IT.
- Where
- The operator's console, signed in with the admin key or as the admin user. It is not linked from public pages.
- Limits
- Only requests that match a real API route are counted; the server's own health checks are kept apart as 'from this server'. API calls are counted per country with no address stored; growth data is pruned at 400 days. The admin never reads a site's passcode; it can remove one for moderation. Wrong admin keys count against a rate limit, so 'Too many tries' is real.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise's admin page is for company IT: disable or enable a person, offboard by email, access requests, export, revoke a leaked key, and a 'This instance' panel (release, pending migrations, bucket check, limits in force). On the hosted hackathon instance the console also has an Events table.
Take-down and suspensionThe operator can take a site down or suspend an account, reversibly, with the reason shown and nothing deleted.
A taken-down site answers 'This site has been taken down' on every address it had (its site host, its person path, its claimed name, and its custom domain). The owner sees the reason on their dashboard. The owner's key can still read and export the site; deploys, renames, changes to List on my profile, and data writes are refused. A suspended person's key, connected apps, and visitor sessions stop working with the reason, sign-in is refused, and their sites go down. Nothing is deleted. Restore or re-enable reverses it; a site taken down on its own stays down when its owner is re-enabled.
Example. A page impersonating a bank is reported on a Sunday; the operator takes it down within the hour, the owner sees the reason, and nothing is lost if the appeal succeeds.
- Who
- Visitors and owners of a site the operator has acted on, and operators handling an abuse report.
- Where
- The take-down page a visitor sees; the reason on the owner's dashboard and site cards.
- Limits
- A suspended site keeps everything and is kept past the Recently deleted window. The take-down page loads nothing and carries no link. Appeals are read by a person within 30 days (see Terms, privacy, and support).
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise restricts a site to its owner with a reason instead; the owner cannot raise, rename, or move it, and only an admin's Lift restores it.
Report a pageAnyone can report a page on the service from a short form; the report goes to support by email and nothing is stored.
The form asks for the page's address, a reason from eight, optional details, and an optional email for a reply. It carries an emergency-services line and, for child sexual abuse material, says not to include the material. The report is emailed to the support contact with the reporter as the reply-to address. It is linked from the footer of every page (so the 404 page too), the home page, the terms, and the support page.
Example. A photographer finds their portfolio copied onto someone else's site and reports the address with the copyright reason; support replies from the mailbox.
- Who
- A visitor who finds a page that breaks the terms, and rights holders.
- Where
- Report a page in the site-wide footer, or /report.
- Limits
- Accepts only addresses on the service's own domain or a connected custom domain. Caps: address 2,048 characters, details 4,000, email 254. Five reports per address, then one every 10 minutes, and 60 an hour in all. Nothing is stored; the server log keeps only the reason and the host. The offline and take-down pages carry no link to it.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise runs inside a company and has no public report form.
Terms, privacy, and supportPlain terms, a privacy page, and a support page with one public address, support@simple-host.app, shared with Simple Hack.
The terms cover acceptable use (including terrorism, hate, self-harm, sexual services, search spam, and misinformation such as dangerous health claims, misleading voters, and manipulated media; satire, parody, and opinion are fine), named regulated goods, selling from a site (allowed; payment goes through a provider and the site owner is the seller), what the service and saved data are not for, children's and special-category data, trademark and likeness requests, legal-request channels, what evidence is kept, and a security-report line. Intimate images are removed within 48 hours of a valid request. Appeals are open for 30 days and a person reads each one and gives one answer. Adverse changes get 14 days' notice. The DMCA agent is registered (DMCA-1081064) with support@simple-host.app as the directory contact. The privacy page describes member emails, role-based judging access, private team results, and archive retention on Simple Hack, and the support page explains reconnecting an AI app for the right role and revoking connections with Sign out everywhere.
Example. A client asks an agency whether a Simple Host portal may sell workshop tickets; the terms answer yes, through a payment provider, with the agency's client as the seller.
- Who
- Everyone who publishes or reads a site here, and anyone with a legal request.
- Where
- /terms, /privacy.html, and /support, linked from every page's footer and from the plugin listings.
- Limits
- One support address for everything: support@simple-host.app. The terms were last updated 28 September 2026.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Simple Hack shares the same terms, privacy page, and support page. Enterprise has its own landing, docs, and install pages inside the company.
Sign-ups by sourceEach account records once, when it is made, where it came from: the website, which AI app, or an agent, never an address.
At creation the account gets a label: website (a sign-up from the site's own pages), the name of the AI app when the account was made on the connector's consent page, or agent with the agent's name when a tool created it. The method is recorded too (emailed code, Google, issued by an operator). A campaign tag or link carried in the same visit (?from= and utm_* values, the referring host, the landing time) is kept as detail; there is no attribution cookie and no cross-visit window. The operator's Overview groups sign-ups by source over the last week, the last 30 days, and all time, and each group opens to its accounts with a funnel (signed up, connected an AI, published a site, got visitors), search, and a CSV download.
Example. The operator sees that most accounts from a conference link connected an AI app within a day but published nothing, and follows up with the Get started page.
- Who
- The operator reading where new accounts come from; every account holder, as a matter of what is recorded about them.
- Where
- The latest sign-ups and Sign-ups by source on the operator's Overview; the Source column on Users.
- Limits
- A label only. Never an IP address. Accounts from before 29 September 2026 carry an inferred label. The agent name is cut to 40 characters and anything shaped like an address is dropped.
- Simple Hostyes
- Simple Hackyes
- Enterpriseno
- Small boxyes
Enterprise accounts come from the company's identity provider, so there is no outside link to credit.
Rate limits that tell you when to retryEvery limited request answers with RateLimit headers and an exact Retry-After, so a script knows the balance and the wait.
Limits are token buckets per address or per account. Responses carry RateLimit, RateLimit-Policy, RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset: the remaining balance after the request and the seconds until one more token is available. A refused request answers 429 with the code rate_limited and a real Retry-After. Unknown API paths and unsupported methods answer JSON with a code and a docs hint; website pages keep their HTML 404.
Example. A booking site's nightly export script reads RateLimit-Remaining and paces itself instead of guessing.
- Who
- Anyone writing a script or agent against the API, and the operator setting limits on their own copy.
- Where
- On every limited API response; the values in force are stated in the API reference.
- Limits
- Saved-data reads are limited per site and address, or per account for a signed-in key or connector. Items added to a list without the owner's key: 30 a minute per address. Uploads, sign-in, emails, and the connector have their own buckets. Every user-facing limit is a setting on your own copy.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise runs per-pod buckets plus shared counters across pods for sign-in, hand-off, key mint, and the connector, and reports the same headers.
Size caps, blocked files, and reserved namesPlain limits on what a site, a file, or an account can hold, with a stable error code when one is hit.
A site archive is capped at 25 MB; a few accounts have a higher cap by arrangement. A site's live saved data may grow to 50 MB; past that, only growth is refused, with the code site_full. Shared state is 1 MB, a list item 64 KB, and one update may carry at most 100 operations. An account may hold 100 sites. Uploads of blocked file types are refused. Handles and subdomain names that would collide with the service's own addresses are reserved, report among them. Every page carries the standard security headers, and the service's own pages run under a strict content security policy.
Example. A photographer's portfolio comes in at 160 MB; the error names the 100 MB cap, so they resize the images or use the photo flow, which stores small copies.
- Who
- Anyone publishing a large site or storing data, and anyone picking a name.
- Where
- The error message names the cap in force; the API reference lists them.
- Limits
- Caps are stated where they apply, and the served text follows the value in force on that server. The owner of a copy can raise or lower each one.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise caps sites and stored bytes per owner and shows usage on the dashboard.
Safe retries with an Idempotency-KeyA create call sent twice with the same Idempotency-Key returns the first answer for 24 hours, so a retried script makes one site.
Owner create calls (site archives and inline files, photos, domain bindings, named viewers, export links, version preview links, notification subscriptions, storage download links, and table row creates) accept an optional Idempotency-Key header. The same account, route, key, and body replay the original status and body, including errors, for 24 hours; concurrent duplicates wait for the first answer. List adds and state updates take the header too for signed-in callers.
Example. A deploy pipeline times out on the first publish and retries; the second call returns the same version instead of a duplicate.
- Who
- Anyone deploying from CI or an agent that may retry on a dropped connection.
- Where
- An optional header on create calls, in the API reference.
- Limits
- A different body under the same key answers 409
idempotency_key_reused. Replays are kept in memory on simple-host.app and are lost on a restart. Rate limits and sign-in still apply to a replay, and replaying a link does not renew its expiry. Anonymous writes ignore the header.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise keeps replays in its database across pods and answers 422 on a changed body.
Simple Host EnterpriseThe company edition: the same hosting installed into a company's own Kubernetes cluster, behind the company's sign-in.
Enterprise installs as a Helm chart into a cluster the company already runs, with its Postgres, an S3-compatible bucket for site files, cert-manager for certificates, and company OIDC for every sign-in. Agents connect over MCP with that same sign-in. Site files live in the bucket, so pods are stateless and can be replaced. The /enterprise page explains the product and quotes what it costs; /enterprise/architecture shows how the pieces fit; /enterprise/brief is a one-page summary for a decision maker.
Example. A 2,000-person company lets teams publish project pages and internal tools from Claude or ChatGPT, each page reachable only to colleagues who sign in with the company account.
- Who
- Companies that want their people to publish internal sites from their AI apps, behind their own sign-in.
- Where
- /enterprise, /enterprise/architecture, and /enterprise/brief on simple-host.app; Try it in your organization leads to the setup helper.
- Limits
- Enterprise is version 0.x and installs into an existing cluster; the helper does not create clusters or cloud accounts. There are no public sign-ups, no custom short names, and the admin page is built for company IT. Its uninstall guide covers export first, DNS records before the load balancer is released, the namespace, the certificate issuer made for it, the OIDC app, the bucket with its old versions, the database with its backups, and retained secrets.
- Simple Hostno
- Simple Hackno
- Enterpriseyes
- Small boxno
Described on simple-host.app; it runs inside the company's cluster.
Cost calculatorA page that works out what Simple Host Enterprise costs to run on AWS, Azure, Google Cloud, UpCloud, or Hetzner for your numbers.
Enter the people who sign in, the number of sites, and a traffic level (Light, Typical, Heavy, Very heavy, or your own page views and MB per view), plus average site size, saved data per site, and uploaded files. Four switches: you already have a Kubernetes cluster, you already have an ingress and load balancer, traffic stays inside the company network, and high availability. The page shows each provider's monthly total side by side, the cost per person, a bar split into cluster and nodes, database, storage, traffic, load balancer, and other, and the selected provider's line items with unit prices and a link to that provider's own calculator. An example for 2,000 people (6,000 sites) sits at the top with a Use these numbers button. How we size it lists every rule with its value for your inputs.
Example. An IT lead enters 400 people and Typical traffic on their existing Azure cluster and takes the monthly figure and the line items into a budget request.
- Who
- A company weighing Enterprise, and anyone sizing a cluster for it.
- Where
- /costs on simple-host.app, linked from the Enterprise pages and the setup helper.
- Limits
- List prices excluding tax, each with its source and the date it was checked; a price older than 45 days is flagged for review. Your bill may differ. UpCloud and Hetzner assume a k3s cluster you run yourself with Postgres on its own server. The page runs in your browser and sends nothing anywhere; its state is in the address, so a result can be shared as a link.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
A page on simple-host.app that describes the Enterprise edition's running cost.
Setup helperA page that asks a few questions and writes the install command and settings for a small box, or the Helm values and chart for Enterprise.
Choose Small box (one server with Docker Compose) or Enterprise (an existing Kubernetes cluster, Helm or plain Kubernetes YAML). Basic asks the essentials: for a small box the domain, the sites hostname, a certificate email, sign-in by emailed code or Google, the sender, and where it runs (UpCloud or a server you already have); for Enterprise the address, admins, OIDC issuer and client, the certificate issuer, SMTP, the bucket, Postgres, and the ingress controller's address range. Advanced then offers every other setting, area by area, with a one-line explanation and its default preselected. The output is a one-line install command pinned to a release and checked against its hash plus the settings lines to paste, or a Helm chart ZIP with values, a secret template, a README with lint and dry-run commands, and install commands. Each output comes with Set it up with your AI agent: one block to copy into the agent you use in a terminal, with every step and check in it.
Example. A design studio picks Small box, answers six questions, copies the install line to a fresh server, and has its own copy serving the studio's domain the same afternoon.
- Who
- Anyone about to run their own copy: a team on one server, or company IT with a cluster.
- Where
- /setup?product=small-box or /setup?product=enterprise, linked from Get started, the Enterprise pages, and Run your own.
- Limits
- Nothing is required to reach the files; missing answers stay defaults or marked blanks. The checks catch an obvious typo or anything that would break a file or command; no form choice is sent to a model. The helper never asks for a secret's value and sends nothing but requests for its own files. It does not create servers, clusters, or cloud accounts. UpCloud's smallest server (1 CPU, 1 GB, about $4 a month) is the recommended small box; the page offers a referral link for $25 of UpCloud credit, under UpCloud's terms.
- Simple Hostyes
- Simple Hackno
- Enterpriseno
- Small boxno
A page on simple-host.app that produces the setup for the small-box and Enterprise editions.
Run it on your own serverThe same software runs on a server of your own, from one install command, with every limit on this page as a setting.
One server, Docker Compose, and a one-line installer that pulls a pinned release: the app, Postgres, and Caddy for certificates. The setup helper asks a few questions and writes the command and the settings. Re-running the installer upgrades: it pulls the new release, applies the schema changes, then starts the new app; if a schema change fails the old app keeps running. The DigitalOcean 1-Click image runs the same installer on first login.
Example. A university hackathon club runs Simple Hack on a $4 server for its weekend event, with its own domain and its own limits.
- Who
- Teams and event organisers who want their own copy, with their own limits.
- Where
- Run your own, Set up, which opens /setup?product=small-box.
- Limits
- Every limit on this page is a setting there, read once at startup with range checks; a bad value stops the server, and the sign-in limits can be loosened at most 4 times the default. Pages, emails, and the API reference on your copy state the values in force. Your server, your certificates, and your backups are yours to run. Site files live on the server's own disk. When you shut an event box down, download entries and remove the DNS records before deleting the server.
- Simple Hostno
- Simple Hackpartly
- Enterpriseno
- Small boxyes
Simple Hack also runs on a server of your own with the same installer, keeping its own address.
Health checks and schema upgradesTwo health addresses for your monitoring, and schema changes that run once, in order, under a lock, before a new release starts.
/healthz answers when the process is up; /readyz also pings the database. The app logs its release and commit at startup and refuses to start if the database is missing a column, naming the command to run. Schema changes are files applied in order, each once in its own transaction, tracked in the database and guarded by an advisory lock, so two starts cannot race. The installer runs them on every run; simple-host version shows the release, commit, and the changes in the build without touching the database.
Example. A company's monitoring polls the readiness address every minute and pages the on-call person after two failures, the same way simple-host.app watches itself.
- Who
- Operators running their own copy and anyone wiring up uptime monitoring.
- Where
- The two health addresses on your server; the migrate and version commands in a shell on the box.
- Limits
- A small box has no metrics endpoint. The app never migrates on its own; a failed change leaves the old release running.
- Simple Hostyes
- Simple Hackyes
- Enterpriseyes
- Small boxyes
Enterprise runs schema changes in an init container and exposes /metrics on its own port, with startup warnings exported too.
Simple Hack
Back to the mapSimple Hack runs hackathons from sign-up to results, team sites included. It is the same software run as its own product.
Run an eventCreate a hackathon at simple-hack.app, move it through its stages with one button, add co-organisers, and delete it when done.
Sign in at https://simple-hack.app and create an event; it gets its own public page at <event>.simple-hack.app, a join link, a judge link, and a code of conduct. The Overview shows one forward button for the current stage (open, building, closed, judging, results, ended), worked out on the server so the website and your AI app agree; moving to Results also locks judging. You can invite co-organisers with one seven-day link that anyone can accept until you revoke it, rename teams, download participant, team, entry, and score CSVs, download every team site as an archive, and see storage use. Settings ends with Delete this event, which asks you to type the event's address name and then removes the public page, results, entries, scores, votes, member access, custom website, and storage for good. A standing demo event on simple-hack.app lets you try the participant and judge paths from https://simple-hack.app/watch.
Example. A university society creates its spring hackathon, adds two co-organisers, walks the Overview button from Open to Results over the weekend, and exports the results CSV for the prize ceremony.
- Who
- Organisers, from a single person running a weekend event to a team of co-organisers.
- Where
- simple-hack.app, Manage (Overview, People, Settings), or ask your AI app with the organiser role.
- Limits
- On simple-hack.app, three new events per account per day and five active events per organiser; admins and listed accounts have no limit. Self-hosted installs have no active-event limit by default. The event creator cannot be removed. There is no undo and no email after deleting an event, and the address stays reserved once anyone has joined. Moving a stage backwards asks for confirmation.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server; the weekly demo event is hosted only.
Registration, applications, tracks, and announcementsPeople join by link or apply from the public listing; organisers ask sign-up questions, set tracks and prizes, and post announcements.
Participants join with the event's link, or, for an event listed in Find a hackathon, apply from the listing or the event's public page without a link. Applications are on by default and every application waits for an organiser's decision in People, Applications; an applicant may add a city, country, age range, and gender, which stay with that event and are never shown to other organisers. Organisers can ask up to eight text questions at sign-up and require approval; pending and rejected applicants see their own status. Up to twelve tracks each carry a challenge and a prize, and each team picks one track before its deadline. Organisers publish sponsors, an FAQ, a schedule with time zones, and announcements, can edit or delete an announcement, and can email participants, send a receipt on a team's first complete entry, and show a public submission countdown. The schedule shows the real times on its own (event start and end, the entry deadline, the voting window, results), so they never drift, and a schedule row can ask the organiser for the next step when its time comes, for example “Kickoff is now. Open sign-up?” It never moves the stage itself. Participants see “Demos starts in 12 minutes” on their Home.
Example. A company running a public AI hackathon lists it in Find a hackathon, takes applications over two weeks, approves 80 people, and announces the final schedule by email the night before.
- Who
- Participants joining an event, and organisers deciding who gets in and keeping everyone informed.
- Where
- Find a hackathon and the event's public page for applicants; Manage (Settings, People, Content) for organisers; or ask your AI app.
- Limits
- Only listed events take applications; unlisted events are join-link only. Five applications per account and 30 per IP address each hour, 20 pending applications per account, and 500 pending applications per event. A rejected applicant can apply again only after withdrawing. Editing an announcement does not send a new email. Track names may repeat; removing a chosen track warns how many teams lose their choice.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server
TeamsFind teammates, ask to join or invite, run your team as its admin, lock it, share its link, and leave an event cleanly.
Solo participants see open teams with their track, room left, and members, ask to join, or list themselves with a short intro; team members invite listed people and accept or decline requests. Whoever creates a team is its first admin; admins approve requests, rename the team, edit its looking-for note, remove members, make other admins, lock or unlock the team, and roll a new team link (https://simple-hack.app/team/<code>), which anyone can preview before joining. Locking clears pending requests and invites and takes nobody new. Organisers can preview Fill teams, which places solo people into teams with room and then makes new teams, and apply it after confirmation. Anyone can leave an event from their Overview, Settings, or Home row menu, or through their AI app; before the team deadline an emptied team is deleted with its entry and site, and after it the team, its entry, its site, and its scores stay as they were. Any team member can message the organisers from Team; teammates and every organiser share the thread. Organiser Home shows unread team messages with Read and reply; opening the team clears the line for that organiser.
Example. A designer with no team lists herself with a one-line intro on Friday evening; a team of three invites her, their admin approves, and the organiser runs Fill teams on Saturday morning for everyone still solo.
- Who
- Participants forming and running teams, and organisers filling the gaps.
- Where
- The signed-in team step on the event page; Manage, Teams for organisers; or ask your AI app.
- Limits
- Team finding is private to approved participants and can be turned off per event, which hides the lists and stops new requests while codes still work. The looking-for note and solo intro are 120 characters. Team size defaults to 20 per event. Full teams cannot invite or accept, and a frozen team never takes a member back. The last admin cannot be removed until someone else is admin. A judge who leaves keeps their scores counting unless an organiser removes them; the event creator must name a successor before leaving. Team messages are 1 to 1000 characters, at most 10 per team per rolling hour, and stop after End. Organiser emails follow the Account preference, at most once per 15 minutes, when mail is set up.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server
Entry card, rules and submitEvery team hands in the same short summary card, organisers decide what a complete entry needs, and a team submits when it is ready.
The card asks for the problem, the solution in one line, who it is for, the track, tools and AI as tags, and what works today, plus show-your-work evidence: a video, the team website, a code link or a screenshot. Organisers pick a preset (AI build, Coding, Ideas and design) or set each line Required, Optional or Off, and the evidence lines also One of; before saving tighter rules they see which teams it affects. Saving a draft never checks anything. Submit does, on the server, the same way on the website and in the AI apps. Home shows a four-step checklist and a countdown to the team's own deadline. At the deadline a complete draft is submitted automatically; an incomplete one is still judged, marked Incomplete, and the organiser can exclude it by hand. At each of the event's own reminder times before the deadline (24 hours and 1 hour by default), teams whose entry isn't submitted get a reminder email naming what is missing. Published results show each shown team's card on the public page.
Example. An organiser picks the Coding preset, so a code link becomes required. A team fills its card, adds its repo and a video, presses Submit and sees the checklist on Home tick over.
- Who
- Teams finishing their entry before the deadline, and organisers who want every entry in the same shape for judges.
- Where
- Entry and Home for teams, Entries and the entry detail for organisers, in the Simple Hack app; hack_submit_entry and hack_set_entry_rules in the AI apps.
- Limits
- Rules can change only until entries close. Tighter rules never un-submit an entry. A team that never started an entry is not judged.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxno
Simple Hack only
JudgingA weighted rubric, judges spread openly, automatically, by hand, or by track panel, conflicts of interest, a lock, and published results.
The organiser sets a rubric of 1 to 10 criteria, each with a weight and a points scale, before judging opens; a new event starts with Idea, Execution, Design, and Demo at 25 percent each, scored 1 to 5. Judges are spread openly (everyone scores everyone), automatically (an even, conflict-aware spread), by manual assignment, or by panels per track. A judge or an organiser can declare a conflict of interest, which drops that pairing from queues and totals. Organisers, including co-organisers, can also judge under their own account, with the same conflicts and locks. The judge's queue puts the least-covered team first, the scoring screen opens the frozen team site and saves criteria as you go, and Save and next moves on. The organiser watches coverage on the dashboard, locks judging, then publishes: ties are flagged and can be resolved by hand, totals can be raw or normalised across judges, and public ranks and scores can each be hidden. After publication each team privately sees its total, rank, and the judges' comments without names.
Example. A corporate innovation day with 30 teams and 9 judges uses automatic assignment, a sponsor's engineer declares a conflict with the team he mentored, and the organiser publishes winners only.
- Who
- Judges scoring from a phone, and organisers running the rubric, assignments, and results.
- Where
- Manage, Judging for organisers; the judge link and Judge entries for judges; or ask your AI app with the judge role.
- Limits
- Scoring opens at Judging, which locks mode, judges per team, rubric and assignments and generates Automatic assignments. Returning to Entries closed pauses scoring and unlocks setup. Rubric weights must sum to 100; the rubric cannot change while judging is locked, and removing scored criteria or lowering points below saved scores asks for confirmation. Unlocking requires a reason, which is logged. Automatic assignment includes organisers only with include_organisers=true on the API. Public results never show individual judge scores or comments. Results CSV and scores CSV can be downloaded at any time.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server
People's choice voting and the directoryA public vote on the entry gallery with one vote per verified email, and a public directory where organisers list their events.
Once the entry gallery is open, an organiser opens voting with a start and end time and chooses who may vote: any signed-in account, approved event members, or approved participants only. Each verified email has one vote per event and can change it until voting closes; counts and the ranking appear on the public vote page only after the close. The public directory at Find a hackathon groups events as happening now, upcoming, or past; new events are unlisted until an organiser opts in, and listing is also what lets people apply without a join link.
Example. An accelerator demo day lets any signed-in person vote for a crowd favourite during the two-hour showcase and reveals the tally on stage at the close.
- Who
- Organisers who want a crowd prize, voters, and people looking for a hackathon to join.
- Where
- Manage, Judging (voting settings) and Settings (directory listing) for organisers; the event's public vote page and Find a hackathon for everyone.
- Limits
- Voting opens only after the gallery. A voter cannot vote for their own team, including through a
+tagemail alias, which shares the one vote. Narrowing who may vote removes votes that no longer qualify, after confirmation. Only live gallery entries can be chosen. Draft and taken-down events do not appear in the directory. The tally stays after team sites are removed.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server
Team sites and the event websiteEvery team gets a site at its own address, published from an AI app or a zip; organisers can swap the built-in event page for a custom one.
Each team's site lives at <team>.<event>.simple-hack.app. A team publishes it from the AI app they already use (the connector selects the team, then the ordinary site tools publish) or by uploading a zip of static files with index.html at the root from the team's Publish card; both show the published address and version. Team sites use the same KV, SQLite, and file storage presets as any Simple Host site, with page recipes for the setup code, and saves can notify through webhooks. The event's public page is built in; an organiser can instead publish a custom website to the event address, versioned, with the latest five versions shown, and switch back to the built-in page at any time. An organiser can take a team site down and restore it. After an event is archived, team sites stay up for 30 days; the organiser gets one email 14 days before they are removed, and the event page and results stay.
Example. A fintech team describes their prototype to Claude, which publishes the pitch page, demo, and a sign-up form to their team address; the organiser publishes a custom event site with the agenda and sponsor logos.
- Who
- Teams publishing their project, and organisers who want the event page to be their own.
- Where
- The team's Publish card on the event page, Manage, Page for organisers, or ask your AI app.
- Limits
- Team sites allow 25 MB of deployed files with two versions kept. Entries freeze at Judging, including for teams with extra time, so a frozen site cannot be changed. The team site's zip upload is rate limited per IP address and checks freezes and take-downs first. Write to support@simple-host.app for more time after the 30-day window.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server, where team sites live at team.event.your-domain and KV, SQLite, and files share a 1,000,000-byte allowance per site
The AI connector and skillsOne connection at https://simple-hack.app/mcp works for organiser, participant, and judge roles, with skills for each.
Connect your AI app to https://simple-hack.app/mcp once; the same personal connection lists the tools for every role and every event you are in, and the roles come from your membership, so an organiser who also judges needs nothing extra. Participants pick their team and then publish its site with the ordinary site tools. The event tools follow the same rules as the website, so membership, validation, and refusals match. Get started walks through five AI connector setups and offers a one-line install of the five-skill toolkit (run-hackathon, join-hackathon, judge-hackathon, and the site skills); the skill files are also downloadable. The role films on Watch include copyable prompts for creating an event, judging, and building a team site.
Example. An organiser asks ChatGPT to create the event, set a rubric, and generate assignments; a judge asks Claude for their queue and scores from the train; a team asks Grok to publish their pitch page.
- Who
- Anyone who would rather run, join, or judge an event from the AI app they already use.
- Where
- Get started at https://simple-hack.app/get-started, then your AI app.
- Limits
- Tools ask before destructive or outward actions (opening events, replacing scored rubrics, publishing results, emailing participants, deleting people, teams, or events). Simple Hack accounts have no personal site address. A self-hosted instance's connector and skills point at that instance's own domain.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxpartly
Available as the standalone Simple Hack package on one server, with its own Get started naming its own connector
Simple Hack inside a companyThe whole platform on one Docker server, or on your Kubernetes cluster with your own Postgres, with company sign-in.
Download the standalone package (ZIP or tar.gz) and run the install on one Linux server with Docker and 2 GB of RAM; it brings the app, PostgreSQL, and a Caddy web server, with a persistent settings file, volumes for the database, sites, and certificates, and an upgrade script. Event pages use event.your-domain and team sites team.event.your-domain. People sign in through the company's OpenID Connect provider (Okta, Google Workspace, Microsoft Entra, Keycloak) with email sign-in turned off, or with email sign-in and optional Google. On an internal address the installer can issue certificates from its own CA, from the company's ACME server, or use the company's certificate files, and trust the company root. The page at https://simple-hack.app/companies explains the setup with a 45-second film and the two one-line install commands; DigitalOcean and Coolify guides cover those paths. On Kubernetes, the Helm chart in deploy/kubernetes runs the same image as one pod with your Postgres, a persistent volume for the sites and a TLS-terminating load balancer in front; the pod builds the database schema itself on first start, event pages use event.your-domain and team sites event.your-domain/team/, and docs/kubernetes.md is the runbook.
Example. A bank's platform team installs Simple Hack on an internal VM behind Okta, runs a three-day hackathon for 80 engineers, and keeps every team site inside the network.
- Who
- Companies running internal hackathons on their own network, and anyone who wants their own instance.
- Where
- https://simple-hack.app/companies, the self-host page at /hackathons, and the standalone guide in the repository.
- Limits
- You need a server, your own domain with apex and wildcard DNS, and a verified email sender unless company sign-in replaces it. Back up the database and site files before upgrades. The standalone package is Docker Compose on one server; the Kubernetes chart runs one pod (its upload locks and rate limits are in-process), so it scales up, not out. Hosting costs are your provider's bill; the hosted service at simple-hack.app is free.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxyes
This feature is the standalone Simple Hack package itself (v0.8.13); the /companies page and its film are served by simple-hack.app
Role films and the standing demoThree short drawn films show the organiser, judge, and participant paths, with a live demo event you can join or judge right away.
https://simple-hack.app/watch plays an Organizer, a Judge, and a Participant film, six scenes each, with narration on click, pause and restart, draggable scene marks, mute, and keyboard controls; captions sit under the picture on a phone. Each film comes with copyable prompts for your AI app. Below the films, the page shows join and judge links for a standing demo event, so you can try the participant or judge path without making an event of your own. The home page and the companies page open with click-to-play films of their own.
Example. A community organiser watches the organiser film, joins the demo as a judge to see the scoring screen on her phone, and then creates her own event.
- Who
- Anyone deciding whether to run or enter a hackathon on Simple Hack, before signing in.
- Where
- https://simple-hack.app/watch, linked from the Simple Hack home page.
- Limits
- The demo links appear only while the demo event is open or building and not taken down. The films and the demo exist on simple-hack.app only; a self-hosted instance does not serve them.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxno
Hosted only
Ask about this eventOrganisers can ask a small assistant on Home about their event; it answers in a line or two and links to where to act.
Press Ask on Home and type a question. The answer comes from the event's own settings and checklist, the app's screens and the docs, streams in as it is written, and links to the place to change things. When it isn't sure it says so and links the closest setting or docs page. It never changes the event. Chats stay in your browser, per event. Participants and judges don't have it.
Example. Two weeks before kickoff, an organiser asks "Is my setup done?" and gets "Not yet: choose what teams hand in" with a link to Settings, Entries.
- Who
- Organisers setting up an event who want to know what a setting means or what is left to do.
- Where
- Ask on the organiser's Home.
- Limits
- 30 questions per organiser per day and a monthly budget for the whole service on simple-hack.app. Self-hosted installs turn it on by setting an OpenAI-compatible endpoint (ASSISTANT_BASE_URL, ASSISTANT_MODEL, ASSISTANT_API_KEY); it is off until then. Text only.
- Simple Hostno
- Simple Hackyes
- Enterpriseno
- Small boxno
Simple Hack; self-hosted when an endpoint is set