lema · docs
Plans & usage
Two things are worth being plain about: what you can use for free, and what you pay for. Free is genuinely useful on its own. Beyond it, you pay for depth— more for you — or, soon, for breadth— your whole team in one shared record. Never for the number of repos you connect, and never a charge you can’t see coming.
Free today
The public commons is free and needs no account. Ask whether an approach was already ruled out in a covered project — React, Kubernetes, Rust, Vue, Go, and Ethereum EIPs— and lema answers from that project’s own recorded deliberation, with citations, or tells you plainly that there is no recorded ruling. It answers the cited whyfrom the record — not a search over the code. elizaOS is also in the commons for ask-why over its pull-request deliberation; it is not a fuse rulings corpus.
Absence is never dressed up as approval: “no recorded ruling” means we didn’t find one, not that you’re clear. Usage is rate-limited per client so the free door stays open for everyone.
The public record is also free to read and share directly: every public decision has a stable, no-signup permalink, and each indexed repo has a record page you reach by swapping github.com for lema.sh/gh. See Public record for the pages and the no-auth read API.
Plans
Free and Pro are live.Sign-in, repo connection, and self-serve billing work today: you upgrade from your account page, the fee is presented at checkout before you pay, and your plan flips the moment payment lands. Pricing grows along two axes — never by counting your repos:
- Depth (Pro)— everything for one person: the same product with the caps lifted for real daily use.
- Breadth (Team)— your whole team in one shared decision record, capturing and querying together. Not live yet — marked coming soon below, and nothing about it is a charge you can incur today.
- FreeliveFree
Solo
Access: The public commons (React, Kubernetes, Rust, Vue, Go, Ethereum EIPs, and elizaOS) and your own connected repos — recent history imported, the cut stated on the page.
Usage: 150 MCP queries, 50 decision captures, and 5 imports a day — plus 50 verify CI checks per repo each month.
- ProlivePrice at checkout
Solo — more depth
Access: Everything in Free, plus full-history backfill on imports and the caps lifted for real daily use.
Usage: 2,500 MCP queries, 500 decision captures, and 50 imports a day — plus 500 verify CI checks per repo each month.
- Teamcoming soonComing soon
Your whole team
Access: One shared decision record your teammates capture into and query together.
Usage: Higher allowances, plus team views over what has been decided.
We publish limits, not prices: the allowances above are the product; the fee is shown at checkout before you commit, billed monthly, cancel anytime — your plan runs to the end of the period you paid for, then reverts to Free. No free trial, and no charge that isn’t shown to you first.
How usage is counted
One question is one query — whether it checks your record, the commons, or both. Each plan carries a daily query allowance; the public commons is free up to a point, then metered, because answering still costs us to run. Verify CI checks meter differently — per repo, per month — because a repo’s pull-request volume, not your org’s size, is what drives them.
When you reach a limit, your agent gets a clear, structured signal it can act on — the allowance and when it resets — not a silent failure. You always know where you stand. We never charge per question beyond the allowance, and we never meter how many repos you connect.
Why we meter the commons
We would rather be upfront than surprise you. The public commons costs us to serve on every query, so it is free to a point and metered beyond — never free forever, and never silently throttled. Connecting your own repos is free on the Free plan; Pro is depth— higher daily allowances and full-history backfill — and Team (coming soon) is breadth. The commons is the open demonstration of the engine; the metered wall keeps that door open for everyone.