Kaiku
ENES
Start free

Task tracker · Wiki · Agents

An agent-native tracker and wiki.

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.

Start a free monthSee the demo

30 days free. No card, no wallet, no sales call.

Solutions

Who it is for

The same tracker and wiki, put to different work. Start from the one that sounds like yours.

Teams that work with AI agents

Connect Claude Code, Cursor or any other MCP client, or call one of Kaiku’s own agents in a comment. Every run is recorded on the issue it worked on, and an agent proposes while a person approves.

A task tracker for AI agents

Legal and compliance teams

A register of requirements, the act opened at the article an issue cites, and a policy approved as an edition and marked read — so you can show what was reviewed, approved and brought to people, and when.

For legal and compliance teams

Teams that keep clients

A row per client, columns of your own, the work for each client under its row, and the whole book out as .xlsx. A table of clients — not a sales pipeline.

More about the CRM

Theatres and production teams

A dozen productions on one board, each opening night with its work in front of it, and a calendar that draws a bar only between days that were actually recorded.

Read the case

Teams that write things down

Every project carries its own wiki space. A page and the issue it documents point at each other, and a page goes out as a Word document.

The wiki beside the tasks

Product and engineering teams

Kanban and scrum boards, sprints and a backlog, merge requests on the issue — and tools written for the API most companies already run connect as they are.

A task tracker for software teams

Open source and open research

A project bound to its public repository, read by anybody by a link — board, issues, wiki — and outsiders let in to file issues. Its people take no seat, and a company of such projects is free.

A tracker for open source projects

Use cases

Watch it being used.

Each film is recorded inside the product, on data made up for the camera, and runs about a minute and a half.

Three things it does differently

Agents are the point, not a plugin

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 agents

A wiki that speaks the same protocol

Every 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 tasks

The data stays yours

One 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.

Point your agent at it.

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.

New here: just the address, and ask your agent to sign you up

{
  "mcpServers": {
    "kaiku": {
      "type": "http",
      "url": "https://app.kaiku.tech/mcp"
    }
  }
}
claude mcp add \
  --transport http \
  kaiku https://app.kaiku.tech/mcp

No 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.

Already have a workspace: its address and a token

{
  "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.

The servers you already run
The MCP servers built for the incumbent corporate tracker and its wiki work against Kaiku unchanged, because the compatibility is on the wire rather than in a bridge that lags a version behind. Nothing to install, nothing to fork.
And one of our own
Issues and their children, comments and the threads they hang in, wiki pages, attachments by path, project fields, and questions put to one person and waiting on an answer. An agent can read and write the same things a person can, and no more than the token allows.
What the automation cost
Every agent run is recorded against the issue it worked on: tokens by kind, machine time, who asked. You find out what a week of automation actually cost while there is still something to do about it.
A task tracker for AI agents

Bring the work you already have.

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

It reads the issue and proposes. You decide.

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.

Your access, never its own
An agent is a role of your workspace, not an account: no password, no token, no access of its own. It runs as the person who called it, with the permissions they have at that moment, and is clamped to the issue’s project — a question about one project never ships the other nine to a model. Its tools are reads only; the comment it answers with is written by Kaiku, not by the model.
What it read, and what it cost
Every answer carries the issues and pages its tools actually returned, so the reasoning can be checked against its sources. Every call is a row — who called which role, on which issue, what came of it and what it cost — so the bill for the automation is visible while you can still do something about it.
How agents work

CRM

Some teams keep clients, not a backlog.

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.

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.

A row is a client
A client is an issue of its own type, so it comes with comments, files, history and watchers — and the same API and MCP as everything else. Open the row and the work on that client is underneath, filterable by tag.
Columns of your own
The project writes down the columns it needs, of six kinds: a list with colours, a country, a number, a date, a person, a line of text. A value that does not fit its column is refused on the spot, never quietly dropped.
Edited in the cell
The name, the owner and every column of your own change right in the table, instead of opening the card and coming back. It is the same write the card makes, so history, notifications and your agents all see it.
Out as a spreadsheet
One .xlsx with your columns in your order — the whole book, not the page on the screen. A number stays a number and a date stays a date, which a CSV opened in a spreadsheet never promises.
More about the CRM

Mathematics

Notes full of formulas, treated as mathematics.

A seminar’s notes, a course, a research group’s conspectuses: write the formulas in TeX as you always have. Kaiku draws them, finds them however they are typed, keeps the project’s definitions where the words are used, and plays the pictures that move right on the page.

Project terms come with a paid plan that includes AI. Formulas, their search and the scenes come with every plan, the trial included.

Recorded inside the product, on seminar notes made up for the camera. Sound on for the commentary.

Definitions where the word is
A project keeps its terms: a word, its forms, a short definition and the page that defines it. Wherever a page or an issue uses the word, it is marked, and pointing at it shows the definition and its source. Your agents ask the same list over MCP.
Formulas, however they are typed
π_1(S^1) finds a page that wrote \pi_1(S^1), and ω_g finds \omega_{g}: a TeX command and its glyph, a brace and none, are one symbol to the search, in pages and issues alike. The result shows the place where the formula stands.
A scene on the page
An anim block is a scene written as data in manim’s words — objects, steps, formulas — and the reader’s own browser plays it. There is no video to render or store; it plays on the phone too, and goes into Word and PDF as its last frame.
Copied as TeX
Copy a paragraph and its formulas come out as the TeX they were written in, not as a column of single letters — ready to paste into a paper or back into another page.
The wiki beside the tasks

What you get

The ordinary things a tracker owes you, and a few it usually does not.

Boards, sprints, backlog

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.

Fields on a board, too

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.

Read it in your language

Issues, comments and wiki pages are translated automatically, on demand. The language picker searches by what each language calls itself.

Merge requests on the issue

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.

Numbers that stay honest

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.

Archiving that is not deleting

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.

Sign in without a password

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.

The law the work rests on

Cite an act in an issue or a wiki page and it becomes a reference: marked where it was written, read from its official publisher, and listed with everything else that rests on it.

For legal and compliance teams

Notifications that say when

Mentions, watchers, reactions on comments, and a digest that respects what you asked for. Every timestamp keeps its exact value behind the friendly one.

Pricing

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.

Trial

Freefor 30 days

  • Up to 2 people
  • 1 project
  • 1 GB of attachments
  • Every feature, none held back
  • No card and no wallet to start
Start free

Personal

$19.99per month

  • One person, one seat
  • The assistant without a ceiling, under fair use
  • Up to 100 projects
  • 20,000 issues and wiki pages
  • 10 GB of attachments
  • Bought in the iOS and Android app, or here on the web
Start free

Team

$7per person / month

  • Everyone you invite, billed per person
  • Up to 100 projects
  • 20,000 issues and wiki pages
  • 20 GB of attachments
  • +$20/month per extra 20,000, per workspace
  • +$10/month per extra 100 GB of attachments, per workspace
  • AI included — or your own key
  • $5.25 per person / month when paid for a year
Start free, pay later

Team, own AI key

$6per person / month

  • Everything in Team
  • No built-in AI: agents, the assistant and translation run on your company’s own Anthropic or DeepSeek key
  • The provider bills you directly; switched-on agents are a fixed fee each
  • Switch between the two team plans at any time
Start free, pay later

AI Pro, on Team

+$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.

Legal acts, on Team

+$19per project / month

For a project whose work rests on legal acts: citations written in words are read by a model and offered for a person to accept, the acts cited are checked on their publishers’ sites once a week — a changed one keeps its earlier text, and whoever watches the issues and pages that cite it is told — and the project’s list of acts is taken as a spreadsheet. References by address and by number come with every plan. A team of three with one such project pays $40 a month; one person, $26. $14.25 per project when the plan is paid for a year. Included during the trial.

For legal and compliance teams

Schools and universities: when the workspace owner’s address is on a school’s domain — .edu, .edu.au, .ac.uk and the like — Team costs 25% less, $5.25 per person / month, and 30% less than the monthly price when paid for a year, $4.90. The packs and Legal acts are discounted too; AI Pro stays at its price. Nothing to apply for.

Open source: a project bound to a public GitHub or GitLab repository can be opened for anybody to read. People of your company who work only on such projects take no seat; the owner’s seat, the packs and the add-ons are paid as usual. A company whose every project is public is not made read-only when a period goes unpaid, and a new project has three days to be made public.

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.

Questions people actually ask

Which tools work with it, exactly?

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.

Where does my workspace live?

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.

What happens when I stop paying?

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. A workspace whose every project is a public open source project is the exception: it keeps working.

Can I pay by card?

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.

Is there a price for schools and universities?

Yes. If the workspace owner signed up with an address on a school’s domain — .edu, .edu.au, .ac.uk and similar — the team plans cost 25% less than the monthly price on a monthly plan and 30% less on a yearly one: $5.25 or $4.90 per person a month on Team. The packs and Legal acts are discounted the same way; AI Pro is not. There is nothing to apply for: the address decides, from the next period, and a period already paid keeps its price. It can be paid by card or in USDT or USDC. A price agreed with us separately stands instead of it.

Is it free for open source?

Partly, and by rule rather than by application. A project bound to a public repository on GitHub or GitLab can be made public: anybody reads its board, issues and wiki by a link, and people from outside can ask to take part. People of your company who work only on public projects take no seat. The owner and administrators always take one, as does anybody who is also on a closed project; storage, the packs, AI Pro and Legal acts cost what they cost everyone. If a project stops being public, its people are counted from the next period — the period already paid is not touched, and the owner is told the day it happens.

What counts towards the 20,000?

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.

What if I go over?

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.

What counts as a user?

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.

Can I self-host it?

Yes. Send a request for a self-hosted installation to hello@kaiku.tech and we will come back to you with what it involves.

Start with a month.

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