Lif(e) Ov(erview) — your whole life, compressed into one overview. Like everything else here.
The easiest way to retrieve your own data — so AI agents can know you, and co-work with you.
One self-hosted Postgres holds your tasks, events, mood, notes, health and finances. Three interfaces sit on top: a web dashboard for you, a token-efficient CLI for your agents, and a plain HTTP API for everything else.
Look at where your life actually lives right now:
Wire an AI assistant to that pile and you’re maintaining a connector zoo — and the next agent starts from zero again. Lifov collapses the wiring: everything lands in one database you own, behind one interface any agent can use. Integrate once, every agent benefits.
An agent’s context is a budget. Lifov’s CLI spends it carefully: one line per record by default, full JSON only when asked — and every JSON response is wrapped in a versioned envelope that marks your content as data, not instructions.
No browser automation, no scraping, no per-app connector. If your agent can run a shell command, it already speaks Lifov.
Tasks live on a kanban board with real flow semantics — commitment points, WIP limits, discard reasons. You drag cards in the browser; agents move the same cards from the CLI, and every write records who did it, so AI actions stay visible and auditable.
The visualization stays light on purpose — status is one glance for you, one command for the agent. Delegation stops being a copy-paste ritual: put a card on the board, and your agent picks it up.
core = board · timeline · daily notes · CLI / API — that's the whole spine.
Every domain module docks on only if your life uses it. Enable what you need, ignore the rest — the core never grows heavier:
Every hard problem inside Lifov is delegated to something the crowd already battle-tested: Postgres for truth, Beancount + Fava for double-entry accounting, GarminDB for wearable sync, n8n for scheduling, Cloudflare for the edge. Each has years of production mileage and a community fixing edge cases I’d hit alone.
Wiring them together is admittedly more tedious than clicking “sign up” on a SaaS. That’s the trade: a bit of plumbing up front, collective intelligence forever — and every part stays replaceable. Lifov’s own code spends its budget on the one thing nobody ships for you: the schema of your life, and the agent interface on top of it.
Centralizing your whole life into one database is only a good idea if you are the one holding it. An all-in-one SaaS with this much of you inside is a honeypot with a subscription fee. So Lifov is self-hosted by design:
Lifov is also its own proof of method: one person as the requirements provider, a fleet of AI agents as the dev team. Specs live as cards on Lifov’s own board; dev agents implement them test-first in isolated worktrees; a separate reviewer agent adversarially grades every card; design calls are logged as architecture decision records I can veto. Guardrail hooks block the destructive stuff at the tool layer.