Task tracker · Wiki · MCP
Kaiku speaks the Jira and Confluence APIs on the wire. Point any Jira-speaking tool at your workspace — including the Jira MCP your coding agent already runs — and it works unchanged. No adapter, no plugin, no rewrite.
30 days free. No card, no wallet, no sales call.
The Jira MCP and the Confluence MCP 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.
Every project carries exactly one space, keyed like the project. You write Markdown; the wire carries Confluence storage format, so Confluence-speaking tools read it. Pages go out as Word documents, and the words inside an attached diagram are searchable — a drawing stops being a dead end.
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.
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.
A project can define its own fields — Segment, Country, Provider — and read as a client book instead of a backlog. Editable in place, exportable as one .xlsx with your columns in your order.
Issues and comments translate on demand, cached so the second reader pays nothing. 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 paid plan. It costs what it costs, per person who uses it.
Freefor 30 days
$7per person / month
Paid in USDT or USDC. Periods are prepaid — crypto has no standing order, so nothing is ever taken from you without you doing it.
Yes. Kaiku serves the Jira Server/DC REST API — the same request shapes, status codes and error formats. You give the tool your workspace address and your token, and it does not learn that it is talking to something else. The same holds for the Confluence MCP against the wiki.
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.
Not today — payment is in USDT or USDC. Each period is paid 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.
Talk to us. The product runs as three containers and a Postgres, so it is not an unreasonable question.
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