Pricing
Enterprise, quote-based. Start with one workflow.
Madison deploys inside your perimeter and is priced per engagement — there is no public self-serve tier or usage-metered public API. Engagements begin with a bounded design-partner pilot and expand from proof.
How engagements work
Three stages, priced to the scope you deploy.
| Stage | What it is | What it costs |
|---|---|---|
| Design-partner pilot | A bounded, below-tender pilot on one high-value workflow with a focused team, live in weeks. | Fixed-scope pilot fee, quoted per engagement. |
| Production rollout | The pilot workflow put into production, then expanded to more teams and workflows on the same deployment. | Annual enterprise license, scoped to teams, workflows, and deployment model. |
| Enterprise deployment | Bank-wide rollout across functions, with SI-led implementation and full governance controls. | Custom enterprise agreement. |
Pricing depends on deployment model, the number of teams and workflows, and integration scope. Bring your own LLM, so model inference runs on your existing provider contracts.
What's included
Every engagement, governed the same way.
- In-perimeter deployment (on-prem, VPC, or air-gapped)
- Human-in-the-loop approval and an exportable audit trail
- Security & compliance pack (SOC 2 Type II, ISO 27001, model-risk docs)
- Bring your own LLM — inference on your existing provider contracts
- Design-partner onboarding and scoping
SOC 2 Type IIISO 27001On-prem / VPC / air-gappedBYO-LLM
Get a quote for your bank.
Pricing is provided after a short scoping session. Machine-readable pricing is at /pricing.md.