Pricing for regulated AI execution
Pricing is scoped by the enforcement boundary: developer terminal, inference gateway, workflow runtime, or enterprise control plane.
Syndicate Code
- Evidence chain entry point for engineering teams operating in regulated environments.
- Policy-enforced execution at the developer terminal. Approval binding to parameters. HMAC-signed evidence ledger.
- Core provider coverage including OpenAI, Anthropic, Google, and self-hosted models.
- Gate recommended for end-to-end inference traceability.
Syndicate Gate
Multi-tenant hosted. Policy evaluation before inference. Database-enforced budget invariants. Pre-execution evidence. Starting from $7,500/month for production workloads. Volume pricing is scoped during technical review.
Starting scope
- One governed production environment.
- Core provider routing and request-time policy enforcement.
- Pre-execution evidence records and budget invariant reporting.
- Technical review to define volume, SLA, retention, and support terms.
Deploy in your own VPC. OIDC enterprise auth. BYOK credential management. ControlPlane Enterprise request events with enforcement evidence. Pricing is scoped against environment, control requirements, and support model.
Syndicate Claw
- Self-hosted. Pricing reflects deployment requirements and enforcement scope.
- Fail-closed policy engine. Approval binding to workflow state. Hash-chained append-only evidence ledger.
- v2.0.0: workflow engine, HITL approvals, namespaced memory, connectors, scheduled execution.
- Technical review required for production enforcement scope.
How production scope is priced
Each product addresses a different execution boundary. Production pricing depends on where AI agents touch client records, trade execution, KYC, AML, reportable transaction workflows, and the control evidence required before those actions run.
Enterprise Control Plane
Ready for deployment under defined enterprise infrastructure and operational assumptions. Provides fail-closed execution control, PostgreSQL-backed durable state, OIDC/JWT-authorized control paths, verifiable execution records, and security-gated build and release checks.
Deployment assumes customer-managed infrastructure, identity integration, and operator ownership of backup, observability, retention, database access controls, and network policy enforcement.