Documentation
The full map of the documentation is on the left. Here is the shortest path to what you are most likely looking for.
I use the app (cloud or self-hosted)
Start with Your first map — from an empty account to a working map with tasks in ten minutes:
| I want to… | Go to |
|---|---|
| know what to do today | My day and the daily focus |
| use it on my phone | On your phone |
| change the look, or build my own | Your own skin |
| have the AI draft a map for me | The AI assistant |
| know what the trial includes and what comes after | The trial and plans |
| log in to my instance / find its address | Where do I log in |
| set up my team: invites, roles, AI | Team setup (admin) |
| connect my own code or an AI assistant | REST API · MCP server — works in the cloud too |
The details of every feature — maps, tasks, the idea stash, time tracking, automations, notifications, skins, teams, exports, public maps — live in the Features section in the left menu.
I install and run it myself
| I want to… | Go to |
|---|---|
| understand what the app actually does | What killBottleneck is |
| get it running in two commands | Quick start |
| install it properly on a server | Installation |
| change ports, AI, sign-in, limits | Configuration · Environment variables |
| put it behind a domain with HTTPS | HTTPS and a reverse proxy |
| be sure I can restore my data | Backup and restore |
| drive it from my own code | REST API |
| let an AI assistant work with my maps | MCP server |
| know what I may do with the code | License — fair-code |
| know who is behind it | About the project |
What this documentation covers
The Tutorials and Features sections apply to every deployment — the cloud and your own server run the same application. The Guide and Reference sections document the self-hosted product: how to install it, configure it, back it up, and how to talk to it from your own code or from an AI assistant. The documentation is written against the version in the repository, and the API reference is derived from the routes the server actually registers.
Language
The application interface is available in English and Czech. This documentation exists in both as well — switch in the top bar. The API and the MCP layer are English-only by design, so that integrators and AI assistants always get the same wording.
