1 agent · 1 guarded surface · 1 approver
- Live-face gate: liveness + match + single-use
- One MCP or CLI integration
- 7-day audit trail
- Community support
- Slack / API approval routing
- SSO, SCIM, audit export
Money is just the clearest case. The same live-face gate guards anything an agent can’t undo: a wiped database, a deploy, a destructive command, a standing grant.
When a live face releases a payment, we take a modest rate on top of the rails. The payments wedge funds itself.
Every other irreversible action is covered by an always-on subscription, priced on how much you put under the gate, not how often it fires.
1 agent · 1 guarded surface · 1 approver
3 guarded surfaces · 1 approver (you)
Priced per approver · scales with your team’s control surface
Unlimited surfaces · priced on protected resources + seats
One surface = one thing an agent could do that you can’t take back. You pay for how many you cover, not how often the gate fires.
| Feature | Lookout | Solo | Crew | Fleet |
|---|---|---|---|---|
| Guarded surfaces | 1 | 3 | 15 + $8/ea | Unlimited |
| Enrolled approvers | 1 | 1 | Per seat | Unlimited |
| Live-face gate | ✓ | ✓ | ✓ | ✓ |
| Audit retention | 7 days | 90 days | 1 year | Configurable |
| Integrations | 1 | MCP·CLI·IDE | + Slack·API | + SIEM·on-prem |
| Money take-rate | 1.5% | 1.0% | 0.7% | Negotiated |
| Support | Community | Priority | SLA + contact |
Take-rate sits on top of the payment rails and falls as tiers rise. Higher tiers commit more in subscription and move more money. Surfaces, seats, and resources scale with your exposure; gated events never do.