The economics of owning your platform.
SBT uses the open-source software model: you own the deployed technology. Annual subscription covers updates, compliance patches, new integrations, and support. No per-transaction fees. No margin compression as you grow.
Own your technology. Subscribe to evolution.
Red Hat didn’t invent open-source software. Red Hat created an economics model: companies own the deployed software, and they subscribe to support, updates, and new capabilities. SBT uses the same model.
You deploy SBT. You own the deployed platform. Your bank controls the roadmap, the timeline, the architecture. The subscription covers what changes over time: platform updates, regulatory compliance patches, new integrations, and production support.
You Own
- The deployed platform
- Source code access
- All customizations
You Subscribe
- Platform updates
- Compliance patches
- New integrations
- Production support
You Control
- Your roadmap
- Your margin structure
- Your data
| Model | Ownership | Scaling Economics | Long-Term Cost | Risk |
|---|---|---|---|---|
| SBT (Own + Subscribe) | Bank owns | Fixed annual subscription | Lower as you grow | Vendor support risk |
| SaaS Banking Platforms | Vendor owns | Per-transaction or per-account fees | Higher as you grow | Margin compression, vendor lock-in |
| Consulting Engagement | Bank owns (custom build) | Variable (maintenance + new features) | Higher (custom engineering cost) | Technical debt, hiring risk |
| Legacy + Maintain | Bank owns (aging) | Variable (aging system becomes expensive) | Rapidly increasing | Technology obsolescence |
The 5-year math.
Total cost of ownership over a five-year horizon for a mid-size commercial bank.
Deploy SBT
5-year total
~$2M–$2.5M
Bank owns the platform. Can be extended or modified. No per-transaction fees.
Hire a System Integrator
5-year total
~$4.4M–$6.4M
Bank owns custom build. Technical debt accumulates. Difficult to find engineers who understand it.
Maintain Legacy Systems
5-year total
~$1.5M–$4.5M
Highly variable. Increasing operational risk. No modern capabilities.
Scales with your institution.
$10B+ assets
Large banks
SBT saves millions vs. a consulting project. A system integrator quotes $5–7M and 12–18 months. SBT costs a fraction of that and deploys in weeks.
$1–10B assets
Mid-size banks
Eliminates the risk of a multi-year integration project. A complete, modern platform without the organizational burden of managing an extended SI engagement.
$100M–$1B assets
Smaller banks
The value shifts to speed and completeness. SBT includes capabilities you’d never justify building in a consulting project. A platform that grows with you.
Launching new operations
Neo-banks & license-holders
The only rational option. A consulting project ($4–6M, 18+ months) is not realistic on a launch timeline. SBT gets you live in weeks at a fraction of the cost.
Model the network effect.
One bank with ten products active generates a certain revenue profile. Ten banks on the network generate ten times that, plus a network multiplier from inter-bank settlement fees. The franchise value is not one bank. It is the network.
Projected annual network revenue
$332.0M/yr
Revenue by product
Projections are illustrative and based on assumptions described in our economic model. Actual results may differ materially.
Settlement network effects.
Stablecoin banking is only valuable if multiple banks can settle directly. A single bank’s stablecoin infrastructure is isolated. A network of compatible banks is a settlement system. Every bank that deploys SBT becomes a node in that network.
1
deployment
Valuable infrastructure for a single institution.
10
deployments
Correspondent relationships. Direct settlement between banks.
100
deployments
A settlement network with real cost advantages over traditional correspondent banking.
Settlement infrastructure is table stakes. SBT runs the bank.
The market has validated stablecoin infrastructure as a multi-billion-dollar category. But settlement infrastructure is only one layer. The operational infrastructure a bank needs around those settlements — compliance procedures, KYB orchestration, client applications, payment hub, regulatory reporting — is the layer SBT provides. Settlement moves money. SBT runs the bank.
What’s included.
The annual subscription is not open-ended. It covers what changes over time.
Platform Updates
New features, bug fixes, performance improvements. Released quarterly.
Regulatory Compliance Patches
When regulatory requirements change, we release patches that update the operational layer. Deploy patches, not hire engineers.
New Payment Rail Integration
New local schemes, real-time payment networks, stablecoin settlement. Evaluated and scoped per request.
Production Support
24/7 support for production issues, escalation paths, dedicated support engineer for each deployment.
Security Patches
Quarterly security updates. Emergency patches for critical issues.
Compliance Library Updates
As new jurisdictions deploy SBT, the compliance library grows. Procedures are shared across the network.
Not included: feature development for custom requirements, custom integrations, and custom compliance procedures specific to a single bank. These are scoped separately.
Two worked examples showing cost breakdowns for large and smaller institutions.
Detailed example: $50B commercial bank.
A $50B commercial bank processes ~$2 trillion in annual transactions. The operational layer is mission-critical.
Cost of consulting project
Total: $7–10M, plus 2 years of execution risk
Cost of SBT
Year 1: $1.3M. Year 2–5: $300K/year. 5-year total: $2.5M.
Savings: $4–7M over 5 years
Elimination of multi-year SI risk, plus faster time to market. Zero vendor lock-in. Bank owns the platform.
Detailed example: $500M commercial bank.
A $500M commercial bank has limited engineering resources and operates on tighter margins.
Cost of consulting project
Total: $2.3–4.3M, plus 12–18 months of execution risk
Cost of SBT
Year 1: $800K. Year 2–5: $200K/year. 5-year total: $1.6M.
Savings: $700K–$2.7M over 5 years
Launch on a complete platform — client application, compliance tooling, payment orchestration, stablecoin infrastructure — that you would never justify building in-house.
How to engage with SBT.
SBT can be deployed with different engagement models depending on your situation. All models result in bank ownership of the deployed platform.
Preferred, Mambu banks
Direct Deployment
- You have a Mambu core system selected or operational
- SBT handles integration and platform configuration
- Your internal team handles onboarding, testing, go-live planning
Other core systems
Consulting Engagement
- You have a core system other than Mambu
- SBT and your technical team scope the integration
- Your team or a local SI executes integration
Optional
Managed Service Option
- SBT handles operations, monitoring, and maintenance post-launch
- Your bank focuses on customer operations
- All platform management and compliance updates handled
How fast can you deploy?
Select your core banking system to see estimated weeks to go-live with SBT.
Estimated time to go-live
8–12 weeks
Model this for your bank.
Pricing depends on bank size, core system, regulatory jurisdiction, and deployment scope. A 30-minute conversation with our team will clarify what SBT costs for your specific situation.