Small self-hosted apps for the family: photos, notes, a calendar, contacts and health data, on your own server. Each one installs and runs on its own: if all you want is a photo app, install ioPix and you're done. Add another whenever you like, and it signs in with the same accounts.
ioPixphotos
ioNotesnotes
ioCalendarcalendar
ioContactscontacts
ioHealthhealth
ioSuitestart pageEvery app is a small web server with its own web app, its own database and its own installer, built the same way: FastAPI, a single-page app, light and dark, a real phone layout, installable on a home screen.
On its own: a complete photo app. Point it at a folder of photos.
On its own: your notes, searchable everywhere. It can even keep them in a SQLite file.
On its own: a family calendar every phone already speaks to.
On its own: one family address book on every device.
On its own: a fitness web app that needs no cloud service.
Optional: worth it once you run two or more apps. It finds them by itself.
There is no suite to install first and no central server to run. Each app is the whole product for what it does; the others only add to it.
Install ioPix with one command. It needs a MariaDB or MySQL server for its data and its accounts, and that's it: no start page, no other apps, nothing waiting for something you didn't install.
Months later, install ioCalendar and point it at the same account database. Everyone already has an account, and with a shared domain one sign-in covers both. Nothing about the first app changes.
Every installer ends with "Also install…?". Tick the others and they go in the same machine or container, each with its own database and port, without asking the shared questions twice. Or run the whole-suite Docker stack.
ioContacts + ioCalendar: a Birthdays calendar from your contacts, and the people on an event picked from them.ioPix + ioContacts: the face named in ioPix becomes the contact's photo, on every phone.ioSuite + any app: a tile with what matters today: the next events, photos from this day, last night's sleep.Any two apps: the same accounts, roles per app, one sign-in, one admin panel, the same Settings in every app.Every screenshot is the actual app, holding made-up data: the Parker family and their friends are invented.
Photos in the ioPix screenshots: Wikimedia Commons, StockSnap, Unsplash and the project owner's own, under the licenses listed here. The names are invented.
Tick what you want and copy the command. Each app's installer asks for its database, the shared account database and an admin, then starts the service. The requirements are short.
$ bash -c "$(curl -fsSL https://raw.githubusercontent.com/avandeputte/iopix/main/proxmox/ct/iopix.sh)"http://<host>:<port> and sign inEvery app has its own default port, so all of them fit on one host. The installer creates the admin you answered; with several apps it is the same admin everywhere, because the accounts live in one Shared ioSuite database.
Then put the apps behind your reverse proxy for HTTPS (Caddy, nginx, HAProxy or a Cloudflare Tunnel), and every app updates itself from Settings › Server.
The guide covers what every app shares, how to install one or several, and how to run them. Start here:
What a single app needs, what you gain by adding another, and what stays separate.
A MariaDB or MySQL server, and somewhere to run the app: Proxmox, Docker or any Linux or Mac.
"Also install…", one container with several apps, the whole-suite Docker stack.
One account for every app, a role per app, suite admins, app passwords, passwordless viewers.
One Access application for every app, the paths phones need, the optional edge check.
ioPix, ioNotes, ioCalendar and ioContacts are MCP servers: connect Claude or another assistant with an app password.