Everyone gets email and a calendar. The photos land somewhere that belongs to you. You look after it; they just use it.
Ordinary things, working ordinarily — on hardware that belongs to your family.
Everyone gets a real mailbox. Kids get an address that is theirs, at a domain that is yours, with no advertising profile attached to it and no terms of service they had to accept at thirteen.
One calendar everybody can see, plus private ones. Reminder emails before things, and a morning summary of what today looks like — genuinely the most-used feature in a busy house.
Phones back up automatically to your own storage. Your children's faces are not a corpus, and there is no upload limit nudging you toward a subscription.
A shared folder for the household and a private one each. The really sensitive things can be encrypted so that even the server cannot read them.
This is the part every self-hosting project gets wrong. The administrator enjoys the server. Everyone else in the house just wants their mail to work on their phone, and they will not accept “it's a bit fiddly” as an answer.
So the family-facing experience is a normal app: install it, sign in, done. No VPN to connect first, no certificate warnings to click through, no explanation of what a port is. If it stops feeling normal, they go back to Gmail and you have lost.
You get an admin interface for the parts that need an adult: adding a family member, resetting a password, checking that backups ran. Everyone else never sees it.
A ten-year-old cannot weigh what it means for their photos, messages and location history to be somebody's asset for the next sixty years. Somebody has to make that call for them, and it is going to be you.
A family that runs its whole life through one provider's account is one automated flag away from losing the photos, the calendar and the shared documents at once. Your own server has no such switch.
Services get discontinued, acquired, or quietly made worse. A server in your house or on your VPS keeps doing exactly what it did last year, because nobody else has a say in it.
This is the buyer we built the paid install for.
You can self-install for free, and if that sounds like a good Saturday, please do — it is the same software either way.
But most people setting this up for a family do not want a project. For $39.99, once, we provision the server on your own Linode account, install everything, configure SSL and mail, and hand you the keys, including the root password. Your account, your bill, your server. Nothing recurring, and no login of ours sitting on your machine afterwards.
Then you add the family, they install the apps, and the whole thing stops being interesting — which is the goal.
Mail does not bounce — if you run the optional relay, inbound mail waits there until your server is reachable again. Everything else is offline until the machine is back, exactly like any other server. Scheduled backups to your own cloud bucket mean the worst case is restoring onto a new box, not losing anything.
No. They install an app and sign in. The only difference they will notice is that the address ends in your family's domain instead of gmail.com.
They use the Joinery app rather than the phone's built-in mail app — Joinery does not serve IMAP yet, so the built-in clients cannot connect. The Joinery apps are ordinary apps with notifications; for most families this is a non-event, but it is worth knowing before you move everyone.
Upgrades are one command or one click, every few weeks if you feel like it. Backups run on a schedule once configured. Realistically it is a few minutes a month, and nothing at all in the months you ignore it.
A small VPS and a domain name — the sort of monthly cost that disappears into the noise, and less than a family plan at a hosted privacy provider. The software is free for household use, permanently, and there is no subscription to us.
Free to set up yourself, or $39.99 to have it done this afternoon.