How ontoplano works

Ontoplano keeps a whole life in one app: the week drawn as blocks, and the todos, goals, habits, notes, bills, shopping and recipes that the week is made of. You can run your own copy — the server is this repository, and these pages describe what you would be running.

What the app is

How the pieces fit, and why.

• Using it with AI agents — pointing Claude, Codex or anything else that speaks MCP at your own instance
• Architecture — how a request travels, and where each kind of rule is allowed to live
• Deleting your data — the two ways to erase what is here, what each one leaves behind, and why neither can be taken back
• Ethos — what Ontoplano is for, and the rules it keeps while getting there
• The family plan — one subscription, up to five accounts, and the one form that sets it up
• On your phone — the Android app, the isolated instance, and the ways in for iPhone and desktop
• Permissions — the one scope system every way in shares — what each grant hands over, and which tools sit behind it
• Running it yourself — what it needs, four ways to start it, and where your data lives
• Tasks — the three tables a task can live in, and how one becomes another
• The wheel — the gesture that opens the rooms, which way round it goes, and how to reorder it
• Ways in — tokens, scopes, streams, webhooks and the calendar link — the whole outside surface

Reference

Every table, endpoint, permission and shortcut.

• Data model — every table and column, from the migration snapshot
• HTTP API — endpoints and the scope each one demands
• Services — the service layer, module by module
• Interfaces — the rooms, and what is inside each
• Pages and actions — every address, and the form actions behind it
• Configuration — config.toml, the environment, and per-account settings
• Keyboard — every shortcut, per page
• Tutorials — the guided tours, and the screens still without one

Running an instance

Installing it, backing it up, and the parts that live outside the app: Docker, backups, plans, plugins and the Android build are in docs/ beside this directory.

These pages are generated from the code they describe, and the build fails when the two disagree — what they say is what the app does.