Overview
monoki is a self-hosted home screen for the web apps you run yourself.
You paste a link. monoki's server reads the page, pulls out its title and its favicon, and puts it on a board as an icon. You arrange the icons the way you want them, group them into boards, and share a board with the people you run things with.
One Go binary, one SQLite file, no external services.
What it is for
If you self-host, you accumulate URLs: Grafana on one port, Home Assistant on
another, a NAS admin panel, a router, three different *.lan hostnames you can
never quite remember. Browser bookmarks handle this badly — they are a list of
text on one machine, and they are yours alone.
monoki is the alternative: a page of icons, reachable from any device on your network, that other people in the house or on the team can be given access to.
What it is not
- Not a browser bookmark manager. There is no extension, no sync protocol, no import of your entire browsing history. monoki is for the handful of apps you actually run.
- Not a dashboard. It does not poll your services, chart anything, or tell you whether they are up. It is a launcher.
- Not multi-tenant SaaS. There is no open sign-up. An admin creates accounts; see Users & roles.
How it works
you paste a link
│
▼
┌─────────────┐ fetches the page once,
│ monoki │──▶ server-side, and stores
│ (one bin) │ the title + icon bytes
└─────────────┘
│
▼
┌─────────────┐
│ monoki.db │ SQLite: users, groups, bookmarks,
│ (one file) │ icon blobs, sharing grants, audit log
└─────────────┘
The icon fetch happens on your server, not in the visitor's browser. That matters for two reasons: it works for apps on private addresses that a public favicon service could never reach, and opening your home screen makes zero third-party requests — nobody else learns what you run.
Where to go next
- Install — get a binary running.
- Quick start — first account, first board.
- Groups & sharing — the sharing model in full.
- Security — the threat model and its explicit limits.