CallLint Team · design-partner beta
Keep local scanning free. Centralize the rest.
The CallLint CLI is free and stays free — scanning, verdicts, the Trust Gateway, and Continuous Guard all run locally and offline. What teams ask for next is not a bigger scanner: it's a shared place for policy, approvals, receipts, and drift evidence across repos and people. That is what CallLint Team is.
We are opening a small design-partner beta to build it with a handful of teams. It is not on sale yet — this page is where you tell us it should exist.
Free vs. Team — an explicit boundary
We will not move anything you have today behind a paywall. The line is simple: local, single-developer work is free forever; Team adds the shared, cross-repo, multi-person layer that only makes sense for an organization.
Free — local CLI, forever
- Scan MCP servers and agent tools — SAFE / REVIEW / BLOCK / UNKNOWN with evidence.
- Trust Gateway: prepare → approve → apply → verify, with reversible install plans.
- Continuous Guard on authority change; local decision receipts (sign/verify).
- CI gate and the GitHub Action, run from your own repo.
Team — the shared layer
- One org policy, versioned, that every repo's scan and CI pulls.
- Shared approvals and a private baseline — one place to say "this is allowed here."
- Durable decision receipts and drift evidence across repos, kept as an audit trail.
- Cross-repo inventory of what your agents can reach, and who approved it.
Price-range test
We are testing a single, flat plan — no usage billing, no per-seat creep:
What being a design partner means
- A short intake, then a 30-minute interview about how your team handles agent-tool and MCP risk today.
- Early access to the shared layer as we build it, and direct influence on what ships first.
- No obligation to buy. If the willingness is not there, we would rather learn that now.
Related: Home · For agents · MCP security · Agent tool risk