simple·host invite-only
Feature proposal

Let the right people in.
Nobody else.

Name the people who may open your page. They get an email, click once, and they're in. No passwords to invent, no accounts to manage, no database.

Designed, not built — this page explains what it would be

What's true today

Every site here is public. That's usually the point — but it means a site can collect things and never keep them. A signup form works; a page only your client should read doesn't.

Our own docs say so out loud: "fine for a party, not fine for anything you'd mind a stranger reading." Every site that gathers data ships with a small apology in the footer.

Today anyone with the link your page 🙂 the client you meant 🙂 a stranger with the URL 🤖 a crawler Invite-only only the addresses you name your page 🙂 ravi@client.com 🙂 sam@client.com 🚫 everyone else
Fig 1 · The whole feature in one picture. You keep a guest list; the platform checks it.

How it works, for the person using it

The invite is the feature. There's no separate "sign up" step, because the first email already proves who they are.

STEP 1 You add an address ravi@client.com STEP 2 Ravi gets mail "Alice shared a private page" STEP 3 He clicks one tap — or a 6-digit code DONE He's in for 30 days What nobody has to do ✕ invent a password ✕ confirm an account ✕ install anything ✕ write auth code You add an address. Everything else is the platform's job.
Fig 2 · Sharing, signing up and signing in collapse into a single action.

Why you get your own address

This is the one part that changes something visible, so it's worth being straight about.

Right now every site on the platform lives under one shared address — sites.simple-host.app/you/your-site/. To a browser, everything under that address is the same place. Browsers keep sign-ins apart by address and have no finer setting; a folder in the path means nothing to them. So while your site shares an address with everyone else's, a stranger's page could read your visitors' sessions.

There is no clever fix for that — it's how the web works. So you get your own address, and your sites live on it:

vineetu.simple-host.app/sites/your-site/

One address for everyone sites.simple-host.app/… yoursite someoneelse's a badactor can reach into your site's sign-ins one address · no walls inside it An address per person vineetu.simple-host.app/sites/… yoursite-1 yoursite-2 yours · only you put things here your own address everyoneelse blocked Your old link keeps working — it forwards to the new one.
Fig 3 · Browsers separate sign-ins by address, never by folder. The wall goes around you — the cheapest place to put it that still keeps other people out.

Two upsides fall out of this for free: the address is shorter and it's yours (vineetu.simple-host.app), and password-protecting a page stops requiring you to buy a domain — which is the rule today.

One honest limit. The wall goes around you, not around each site, so your own sites share an address with each other. In practice that's fine: you wrote all of them. It only matters if a site displays content that other people submit — then that site should have its own domain, which is already something you can connect.

And one thing that follows from all of this: an invite-only page is only ever reachable at one address. The old shared link doesn't quietly keep serving a private page on the side — it forwards. A locked door with a second unlocked entrance isn't locked.

One setting, three answers

Everything above collapses into a single question in the dashboard: who can open this site?

Who can open this site? Anyone public on the internet the default · today's behaviour One password everyone shares it fine for a group · no identity Only people I invite a list of addresses new · they sign in with email
Fig 4 · No new dashboard section — one existing question gains a third answer.

For the common case — "only these four people may read this" — you write no code at all. You flip the setting and list the addresses. For the rarer case where each person should see their own content, a site can also store a private note per person.

What we'd deliberately leave out

The temptation with sign-in is to build an account system. We shouldn't. Cut from the first version:

Left outWhy
Open sign-upInvite-only means only listed addresses are ever emailed — which removes the biggest abuse and spam problem before it exists.
Google / SSO buttonsEmail works for every address, including corporate ones. A Google button would show simple-host's name on someone else's business page. It comes later, as an extra way to prove the same address.
Bans, roles, profiles, exportsRemoving someone already ends their access. A site with twelve guests doesn't need a permissions system.
Visitor IP and device logsIt would mean holding more personal data about your visitors to render a screen nobody opens. Instead: "3 of the 4 people you invited have opened this."

What stays: the guest list, the page gate, a private note per person, and the ability for a visitor to delete themselves.

Found while designing this

Password-protected pages are not currently private. While mapping this out we checked a live site with a view password set. The page serves publicly to anyone with the link, while its data is locked away even from the owner — exactly backwards. The gate that was supposed to ask for the password was never switched on.

Separately, two sites owned by different people that happen to share a name also share one lock, so one person's password can open the other's page.

Both are fixed first, before any of this is built — they're the foundation invite-only stands on.

Being able to say "this page is private" and have it be true is the actual product here. That's worth getting right before adding anything on top.

The order it would ship in

First

Fix the lock

Make password-protection actually protect. Foundation for everything else.

Then

Private submissions

Form entries stop being readable by strangers. Small change, removes the apology in our docs.

Then

Your own address

A shorter URL, and privacy without buying a domain. Useful on its own.

Then

Invite-only

The guest list, the email sign-in, the private note per person.

Each step is worth shipping by itself, which is the main reason to do them in this order — nothing sits half-finished waiting on the step after it.