Skip to content

What killBottleneck is ​

killBottleneck is a goal map tool with an optional AI assistant, run entirely on your own server (or hosted by us — the app is the same, only the address differs). You draw what you want to achieve as a tree, decide who does each step and by when — and the app keeps telling you the one thing that matters on any given morning: what is blocking someone else, what is overdue, and what is due today.

The name is the point. A plan usually does not fail because nobody knows the goal — it fails because one step nobody is looking at holds up five others. The map makes that step visible; the Bottlenecks button in the map toolbar counts them for you.

One map = one project. The apex on top is what the map exists for; the goals below it have a status, a deadline and an assignee.

Where to find it ​

After signing in, the header offers the pages Projects (project cards and the My day panel), Tasks (your work across projects and the idea stash), Calendar, My map and Templates; administrators and managers also see Organization, and with AI switched on there is an Assistant button on the right. Settings live in the menu under the person icon top right — item by item in Account and settings.

The model in five words ​

Everything in the app hangs off a handful of concepts. They are worth reading once, because the rest of the documentation and the whole API use exactly these words (the full list is in the Glossary).

ConceptWhat it is
Project (map)One map. Its root node is the apex — the thing the whole map is for. Every project gets a number from the server (#12) that never changes; tell it to the assistant or type it into the Archive search.
Goal (node)A step in the map. It has a status (to do / in progress / done), optionally a deadline, a plan, an assignee, a colour, an icon and sub-goals.
TaskA goal that has an assignee or a deadline. It is not a separate object — it is the same node in the map, which also shows up on the Tasks page and in the My day of whoever has to do it. New work = a new goal in the map.
Idea stashA quick capture for things you do not want to structure yet (the Tasks page). An idea can be put into a project at any time — it is hung as a goal under the main goal of the chosen project.
OrganizationThe people on your instance: roles, the org structure with positions and deputies, shared calendars and the Organization view across projects.

Two consequences of that model are easy to miss:

  • A task cannot exist outside a map. If you just want to jot something down, it belongs in the idea stash, not among tasks. That is also why the older /v1/tasks API endpoints no longer exist (they return 410).
  • A plan is not a deadline. The plan says when you intend to work on a step (today to a week ahead) — that is how killBottleneck expresses priority. The deadline is an agreement with somebody else, and nobody moves it just to say "this one matters".

Who does a step: a person or an automation ​

Every goal records who performs it — a person, or an automation. That is what makes the map more than a drawing: a goal marked as automated can be wired to a webhook and actually run, report back, and move itself to done. Goals can also be marked "I would like this automated" so that whoever builds the automations has a queue to work from. Details in Automations and agents; the "when X → do Y" rules inside a map are in Automation rules.

My day ​

The home page and the Tasks page both show My day: a live, clickable breakdown of your work into overdue → overdue at others → today → within a week, computed from your data rather than stored anywhere. It exports as a portrait PNG for your phone — either full, or anonymous with names redacted, if you want to post it somewhere.

My day on the home page — one glance instead of opening five projects.

What works without AI ​

All of it. AI is off by default and the app is fully usable that way: the map editor, statuses and notes, comments on goals, sharing maps for reading or editing, public maps, export to image and PDF, tasks and My day, the calendar with events and reminders, the idea stash, time tracking with a client registry, automation rules and notifications.

With AI switched on you get the assistant on the side — a panel on the right you can tell "make a map out of these meeting notes", send a photo of the whiteboard, a voice note or a PDF, and ask to prepare a meeting or break down a project — plus the AI project summary on the dashboard and one line of morning encouragement in My day. What it can do is in AI assistant; how to switch it on, in Configuration → AI.

Your data stays put

With KB_AI_PROVIDER=none (the default) nothing ever leaves your server. With any other provider, map data is sent to the endpoint you configured — which may well be an Ollama instance on the same machine.

One instance, one team ​

An instance is a single team with three roles: Administrator (users, roles, organization name and logo, AI, default appearance), Manager (may invite new people and sees the Organization overview; on projects, like a member) and Member (their own projects and those they are invited to). On top of the role a person can carry two flags — AI manager (the agent registry, automation requests) and Structure manager (draws the org structure, names deputies). Details in Team and roles.

Next ​

Open source under the MIT license · © Tengo s.r.o.