Task tracker · Wiki · Agents
Recorded inside the product, at the speed it actually moves. Sound on for the commentary.
In Kaiku, agents work in the tracker and the wiki the way the rest of the team does. Hand one an issue or call it in a comment, connect your own over MCP, and see every run on the issue it worked on. An agent proposes; a person approves. Tools written for the API most companies already run connect too.
30 days free. No card, no wallet, no sales call.
The MCP servers your agents already use for the incumbent tracker and its wiki work against Kaiku as they are — the compatibility is on the wire, not in a bridge that lags a version behind. Kaiku also ships an MCP server of its own, and records every agent run against the issue it worked on: tokens by kind, machine time, who asked. You find out what the automation actually cost while you can still do something about it.
A task tracker for AI agentsEvery project carries exactly one space, keyed like the project. You write Markdown; the wire carries the storage format the incumbent corporate wiki uses, so tools built for it read Kaiku without being told. Pages go out as Word documents, and the words inside an attached diagram are searchable — a drawing stops being a dead end.
The wiki beside the tasksOne request gives you the whole project as a zip: structured JSON, readable Markdown, and every attachment. It keeps working after a subscription lapses — a service that locks your data behind a payment is a service nobody should pick.
Kaiku speaks MCP two ways: through its own server, and through the ones your agents already have configured for the tracker and the wiki your company runs today. No account yet? Give your agent one address and ask it to sign you up.
{
"mcpServers": {
"kaiku": {
"type": "http",
"url": "https://app.kaiku.tech/mcp"
}
}
}claude mcp add \
--transport http \
kaiku https://app.kaiku.tech/mcpNo token and no form. The agent shows you the terms, asks for your email and a name for your company, and you read it the code from our email. It gets a token for the new workspace and reconnects with it.
{
"mcpServers": {
"kaiku": {
"type": "http",
"url": "https://<your-workspace>.kaiku.tech/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}Your workspace answers on its own address, and issues its own tokens from Settings. A read-only token cannot reach the MCP endpoint at all.
A company admin imports a project from the cloud version of a popular task manager: issues keep their keys, and their comments, files, custom fields, parents and links come with them. A check runs first and names what will not move — change history, sprints, logged time — before anything is written.
Kaiku Agents
Call one in a comment, the way you call a colleague — by name, in the thread where the question already is. It reads the issue, answers in the same thread, and says what it read to get there.
It never decides. A proposal is recorded as a question addressed to you, with no default answer, so the issue keeps who chose and what they chose — and silence chooses nothing.
Recorded inside the product, on a board made up for the camera. The answers are scripted; everything around them is the product. Sound on for the commentary.
Mini-CRM
Turn on the client book in a project and it reads as one: a row per client, the columns your business actually runs on, and the work for each client right under its row. Nothing leaves the tracker to get there — the board, search and your agents keep seeing the same issues.
Mini, because it is a table of clients with the work under each one — not a sales system with a deal pipeline, follow-up reminders or an email history.
Recorded inside the product, in a client book made up for the camera. Sound on for the commentary.
Case study · A repertory theatre
A dozen productions share one board, and each opening night has thirty pieces of work in front of it. The calendar shows when each of them ran and what each is waiting on — and it draws a bar only between days that were actually recorded, never from a start somebody guessed.
Read the caseWith a 90-second film from inside the product.
The ordinary things a tracker owes you, and a few it usually does not.
Kanban and scrum boards, drag between columns, sprints that start and close. A board bigger than a page says so rather than quietly showing you a prefix.
Your own fields are not only for clients. Any project can define them, search by them, colour its board cards by a list’s value, and mark a card with the field that matters.
Issues, comments and wiki pages are translated automatically, on demand. The language picker searches by what each language calls itself.
Several GitLab repositories per project, because a tracker project rarely lives in one. A repository that did not answer says so instead of pretending there is nothing there.
Stock and flow kept apart — what is open now never quietly takes the date range that created-per-day takes. Archived issues are still counted, because a shelf is not a delete.
Clear a board without losing anything, by hand or on a rule the project sets. Counted from when the task became done, not from when it was made.
Passkeys and Google sign-in, or a password if you prefer one. You cannot remove your last way in, which is the mistake that locks people out.
Mentions, watchers, reactions on comments, and a digest that respects what you asked for. Every timestamp keeps its exact value behind the friendly one.
One plan for one person, and a team plan with our AI or with your own AI key. It costs what it costs, per person who uses it.
Freefor 30 days
$19.99per month
$7per person / month
$6per person / month
+$12.99per seat / month
For the people who lean on the assistant all day. A seat is given to a named person and moves when they leave; its holder’s assistant is counted on its own, under the same fair use as Personal, instead of from the team’s shared allowance. Agents stay per call for everyone. Not on the own-key plan, and no yearly discount.
Pay by card, as a subscription you can cancel at any time and refunded in full within 14 days, or in USDT or USDC, each period prepaid. Card orders are processed by our reseller Paddle.com, the Merchant of Record. Personal can also be bought through the App Store or Google Play in the mobile app.
Anything written against the REST API of the tracker most companies already run — the same request shapes, status codes and error formats, including the MCP server your agent uses for it today. You give the tool your workspace address and your token, and it does not learn it is talking to something else. The same holds for the wiki. Write to us and we will tell you plainly whether the tool you have in mind is covered.
On your own subdomain — yourcompany.kaiku.tech. Your project keys are yours: your CRM has nothing to do with anyone else’s, and issue keys never collide across companies.
The workspace becomes read-only. Nothing is deleted, everything is still readable, and export keeps working so you can take your data with you. We keep it that way for 12 months and warn you well before anything is removed.
Yes. A card pays as a subscription that renews each month or year until you cancel it, which you can do at any time; a card payment is refunded in full if you ask within 14 days. The card orders are processed by our reseller Paddle.com. You can also pay in USDT or USDC, each period up front, and you will always get a warning before one runs out.
An issue or a wiki page — one each, counted together across the whole workspace rather than per project. Archived issues still count: a shelf is not a delete, and a limit you can dodge by archiving is not a limit. Past the included amount it is $20 a month per extra 20,000, charged to the workspace and not per person — a team of three with a large archive pays the same for volume as a team of thirty.
Nothing shuts off that day. You get 7 days to top up, and you keep writing the whole time. Going over is usually something you did not notice — an import, or an agent that filed three hundred issues overnight — and locking someone out of something they do not know about yet is a failure that looks like a fault.
A person with access to the workspace. Invite them and they count; remove them and they stop. Change the number mid-period and the difference is prorated rather than charged twice.
Yes. Send a request for a self-hosted installation to hello@kaiku.tech and we will come back to you with what it involves.
Two people, one project, everything switched on. If it does not fit, you have lost an afternoon and taken your data with you.
Create a workspace