monoki docs Install Source

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 adds it to a catalog everyone on your instance can browse. Each person picks what they actually use, arranges their own board, and tags it into their own groups.

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. Add an app once and everyone on the team can find it — including who to ask when it breaks — while each of them arranges their own home screen.

What it is not

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, the app catalog,
   │ (one file)  │   boards, groups, icon blobs, 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