TAPPaaS

karakeep — Karakeep

Primary audience: TAPPaaS admin.

Karakeep (AGPL-3.0) keeps what you want to read or find again: links, notes and images. Each saved page is fetched, archived and indexed, so it stays readable and searchable when the original changes or disappears, and it can be tagged automatically by an AI model.

What you get

Capability Access from How
The web app: save, read, search, lists and tags home, netbird, internet https://karakeep.<domain> — Sign in with Authentik
The mobile apps (iOS, Android) and the browser extensions anywhere the same address and an API key made in the web app (Settings → API keys)
Page archives and screenshots — a headless Chromium fetches every saved link
Full-text search — Meilisearch, over titles, text and notes
Automatic tags — through the site's LiteLLM, when the AI stack is installed

How it is built

Choosing the AI model, and other settings

Settings of your own go in /var/lib/karakeep/local.env on the VM — one NAME=value per line, read last, so they win. For example:

INFERENCE_TEXT_MODEL=<a model LiteLLM serves>
INFERENCE_ENABLE_AUTO_SUMMARIZATION=true
MAX_ASSET_SIZE_MB=100

Then sudo systemctl restart karakeep. TAPPaaS never writes this file. The settings are Karakeep's own (environment variables).

What is not included

Requirements

Dependencies

Service Why
cluster:vm, templates:nixos the VM and its NixOS configuration
backup:vm the VM, its library and its index, backed up
network:proxy karakeep.<domain> through Caddy
network:rules the firewall rules for port 3000
identity:identity Sign in with Authentik
litellm:models (optional) AI tagging
logging:logs (optional) the VM's logs in Loki