Solo
One human owner
For independent consultants, freelancers, and small studios running work with AI agents.
One human owner, unlimited AI agents, and every agent session billed to the right client. The Solo plan is $19 a month.
| Description | Amount |
|---|---|
| Requirements & planning (June 2026) Agent | $300 |
| Design & development (June 2026) Agent | $750 |
| Security & testing (June 2026) Agent | $450 |
Run /track-time-keito once in a repo and it is configured. From then on, every Claude Code, Codex, or Cursor session records itself against that client and project — one entry per session, hands off.
Agent entries land with source=agent and the tool that created them. Your discovery call and claude-code’s refactor never get confused, totalled, or billed as the same thing.
Human and agent rows arrive on the same invoice, clearly labelled and fully redacted. The client sees clean line items and a total, not your prompts.
Install once, authenticate once, and every agent session on your machine lands on the right client's invoice. No timers, no timesheets, no reconstructing the week from git history.
$ brew install osodevops/tap/keito $ keito auth login $ keito skill install
Per-repo defaults live in .keito/config.yml. Optional hooks in ~/.codex/hooks.json and ~/.claude/settings.json make tracking automatic.
The Solo plan is for operators who run a workforce of AI agents and bill clients for the throughput. One human seat covers you. The agents are included, however many you run.
You review, direct, and decide. The agents produce. Billing that only counts your keyboard hours undercharges for most of the work.
Per-seat pricing assumes workers are humans with logins. Yours are Claude Code, Codex, and Cursor sessions. On Solo, none of them count as seats.
Outcome pricing or hourly, the client asks the same question: what did I pay for? Agent-attributed entries answer it without a spreadsheet.
Solo is one human owner and unlimited AI agents. Pro adds human teammates and approvals. Business adds integrations, exports, and online invoice payments.
One human owner
For independent consultants, freelancers, and small studios running work with AI agents.
Team collaboration
For teams that need shared workspaces, approvals, and team-level project visibility.
Advanced operations
For organizations that need accounting integrations, exports, and stronger controls.
AI agents do not count as human seats on any plan.
Solo, Pro, and Business can use API keys for agent workflows.
Solo, Pro, and Business can use Stripe invoice payments. Business adds exports, Xero, and QuickBooks.
One person holds the workspace and the billing relationship. That is you. You can run as many AI agents as you like underneath that single human seat. The moment a second human needs to log in and work, you move to Pro.
They carry a source of agent and the name of the tool that created them, so a Claude Code entry and a Sion entry are never confused. They sort, total, and group separately, and you can show or hide the agent attribution on any invoice.
Solo includes 50,000 agent time entries a month. That is a working ceiling, not a hard stop. If you reach it we get in touch about Pro rather than cutting tracking off mid-session. Almost no solo operator comes close.
Yes. Add a human and you move to Pro. Everything you have tracked, invoiced, and configured stays exactly where it is. Nothing is migrated, re-keyed, or lost.
Yes. The slash command and the CLI work the same way in Claude Code, Codex, and Cursor, and Claude Desktop through MCP. The agent logs to the same workspace regardless of where it runs.
Whatever you choose. By default agent rows are labelled by tool and the task notes are redacted, so the client sees clean line items and a total. You can reveal more detail per client if you want to.
No. Keito records the time entry: client, project, task, duration, and source. It does not capture or store your prompts, your code, or the contents of the session. With redaction on, task notes never leave your machine.
You run keito auth login once on your machine. The CLI holds a scoped token, and the slash command uses it to post entries to your workspace. The agent never sees a password, and the token is tied to your single human owner.
Not on Solo. Solo is the hosted plan at app.keito.ai. If you have a self-hosting or data-residency requirement, talk to us about Business.
Not yet. They work nights and weekends, never ask for equity, and have shown no interest in organising. We will revisit the policy if that changes.
Every untracked agent session is work you delivered and never billed. Three commands from now, that stops.