Cryptographic Mandate Controls
Simple pricing. No surprises.
Free for developers. Enterprise pricing that scales with your mandate volume. Start a 14-day pilot on any paid plan with no commitment.
Developer
Build and test against the Yebo pipeline in dry-run mode (sandbox access by request). No credit card.
- ✓1,000 mandates per month
- ✓Sandbox gateway access
- ✓API keys from your dashboard (gateway enforcement coming soon)
- ✓MCP server (@yebo-auth/mcp-server, preview: authorization tools being updated to the current gateway API)
- ✓Standard policy packages
- ✓Community support
Starter
Production authorization for teams running AI in finance or operations.
- ✓Up to 50,000 mandates/mo
- ✓Standard policy packages
- ✓Audit log retention: period to be confirmed
- ✓YAC mandate generation
- ✓Stripe Connect and ACH payouts (coming soon)
- ✓Email support (48hr SLA)
Growth
Advanced controls and compliance for scaling enterprise AI operations.
- ✓Mandate volume and price agreed with sales
- ✓Custom policy configuration
- ✓Audit log retention: period to be confirmed
- ✓SOX evidence exports
- ✓All execution adapters (dry run today; live execution coming soon)
- ✓Priority 24/7 support
- ✓Integration engineering hours
Enterprise
Dedicated infrastructure, custom SLAs, and a dedicated solutions architect.
- ✓Unlimited mandates (tiered)
- ✓Dedicated infrastructure instance
- ✓Custom security SLAs
- ✓TAM + Solutions Architect
- ✓Compliance audit support
Usage-based pricing
Priced per mandate processed, with included mandates in each plan. Plan volumes and audit log retention periods are contract terms: automatic usage metering and retention enforcement are coming soon, so usage above your plan is reviewed with you.
What counts as a mandate?
One mandate = one authorization request through the Yebo pipeline. Preflight checks (POST /preflight) and verification calls do NOT count.
Why finance-systems teams pay for mandate controls
Your executives certify controls over every disbursement under Sections 302 and 906, including any that software initiates. The approval evidence behind those certifications usually lives in a vendor's logs, and it lasts only as long as the vendor relationship does.
Yebo's policy engine returns ALLOW, DENY or REQUIRE_APPROVAL before a payment runs, and fails closed. Every execution decision is recorded in the gateway's audit log, and every action it lets through gets a gateway-signed receipt (ECDSA P-256), exportable as an audit artifact and checkable offline against our published public keys with the open-source npm verifier, npx yebo-verify@0.2.0. Execution runs in dry-run mode today: Yebo issues signed dry-run receipts and no money moves. Live payment execution is coming soon.
Start with a 14-day pilot
One vendor disbursement workflow, one threshold, one approver group, run in dry-run mode so no money moves. You see exactly what Yebo blocks, approves, and escalates. No commitment.
Additional workflow types are supported post-pilot as your controls expand.
Enterprise contracts: hello@yebo.dev · Proposal within 48 hours