One-off cost, not recurring
A perpetual licence is a fixed one-off software cost from CHF 295,000 for one licensed legal entity. Access does not depend on renewing an indefinite SaaS subscription.
Mambu alternative
Self-Hosted Core Banking Alternative to Mambu
A perpetual-licence, self-hosted financial-services platform for institutions that want ownership of their core software instead of a cloud-only SaaS subscription.
Mambu is a cloud-native, composable core-banking platform delivered as SaaS on provider-managed infrastructure. SAMFCore takes a different approach: a modular financial-services platform—accounts, payments, cards, crypto, compliance and back-office—designed for self-hosted deployment, with a perpetual software licence from CHF 295,000 and optional full source code.
Comparison based on publicly available Mambu information and current SAMFCore product documentation. Features and commercial terms may change.
Quick answer
What is a self-hosted alternative to Mambu?
A self-hosted alternative to Mambu is a core banking and financial-services platform the institution deploys within its own or appointed infrastructure, rather than renting it as cloud-only SaaS. SAMFCore is such an alternative: a modular platform with a perpetual licence, optional full source code, customer-controlled deployment and no SAMFCore per-user or per-transaction-volume software fees.
Perpetual licensing
How SAMFCore’s Perpetual Licensing Differs from SaaS Subscriptions
Cloud-only SaaS banking platforms charge a recurring subscription—often scaled by users, accounts or transaction volume. A SAMFCore perpetual licence is a fixed one-off software cost with continuing usage rights and no volume-based software fees.
No volume-based software fees
Under the perpetual model there are no SAMFCore per-user or per-transaction-volume software fees. Customer, account and transaction growth does not increase the SAMFCore software licence cost.
Source-code ownership option
Full source code is available with a qualifying perpetual licence, so the institution can review, maintain and extend the platform with its own or appointed developers within the agreed licence scope.
Vendor independence
Perpetual rights reduce dependency on a single SaaS vendor’s renewal, pricing and roadmap decisions.
Self-hosted control
The perpetual model pairs with self-hosted deployment on customer-controlled infrastructure, supporting data sovereignty and operational resilience.
Predictable long-term cost
The five-year SAMFCore software cost is the one-off licence plus any optional support—not a function of transaction volume that grows month after month.
Perpetual licence vs SaaS subscription: the core difference
A SaaS subscription keeps the software access conditional on an active, recurring payment that can rise as the business grows. A SAMFCore perpetual licence is a one-off cost from CHF 295,000 that gives the licensed entity continuing usage rights under the applicable licence. Under the perpetual model there are no SAMFCore per-user or per-transaction-volume software fees, so growth in customers, accounts and payments does not re-price the core software layer. Optional support and source-code packages change the total; third-party infrastructure and provider costs remain separate in both models.
Modular architecture
How SAMFCore’s Modular Architecture Differs from Cloud-Only SaaS Banking
Cloud-only SaaS banking runs on the provider’s managed infrastructure, with the provider controlling hosting, updates and the release schedule. SAMFCore is a modular platform designed for self-hosted deployment and customer-selected providers, with accounts, payments, cards, crypto, compliance and back-office working in one connected environment under a single perpetual licence.
One platform, multiple modules
Accounts and ledger, payments, debit cards, crypto and digital assets, KYC/KYB and compliance, CRM and back-office, reporting and white-label brands operate in one connected environment under a single perpetual licence.
Self-hosted deployment
Deploy within infrastructure the institution controls—private cloud or on-premise where the deployment supports it—rather than depending on a cloud-only SaaS provider’s hosting.
Perpetual, not subscription
A one-off perpetual licence from CHF 295,000 gives continuing usage rights; there is no SAMFCore per-user or per-transaction-volume software fee, so growth does not re-price the core software layer.
Optional full source code
Qualifying licences include full source code, enabling internal or appointed-developer maintenance and independent review within the agreed licence scope.
Fiat and crypto together
Traditional financial operations and digital-asset workflows—including fiat-to-crypto and crypto-to-fiat—run in the same platform, using customer-selected providers where required.
Customer-designed security boundary
The institution controls isolation, logging, encryption, testing and incident response around its own environment and security operations centre.
SAMFCore is the software and integration layer. It does not itself provide regulated banking, EMI licensing, custody, card issuing, KYC databases or AML screening—these remain with customer-selected external providers and the institution’s own regulatory permissions. Card issuing, BIN sponsorship, custody, exchange and screening remain with customer-selected providers.
Side by side
Self-Hosted SAMFCore vs Cloud-Only SaaS Banking
A direct comparison of the operating, commercial and architectural differences between a self-hosted perpetual-licence platform and a cloud-only SaaS banking model.
Dimension
Cloud-only SaaS (e.g. Mambu)
Self-hosted SAMFCore
Deployment model
Cloud-only SaaS on provider-managed infrastructure.
Self-hosted on customer-controlled or appointed-provider infrastructure.
Software rights
Continuing access under an active subscription.
Perpetual continuing usage rights under the applicable licence.
Source code
Not publicly presented as a standard purchase option.
Optional full source code with a qualifying perpetual licence.
Pricing model
Recurring subscription, often with volume or per-user components.
One-off perpetual licence from CHF 295,000; no SAMFCore per-user or per-transaction-volume software fees.
Transaction-volume software fees
Can scale with users, accounts or transaction volume.
No SAMFCore transaction-volume software fee under the perpetual model.
Architecture
Cloud-native composable banking on the provider’s platform.
Modular: accounts, payments, cards, crypto, compliance and back-office in one environment.
Provider choice
Provider ecosystem and partner integrations.
Customer-selected providers integrated through the API framework.
Maintenance
Provider-managed updates and patching.
Perpetual source-code customers may maintain via Swiss AMF, their own team or appointed developers.
Data and security boundary
Provider-managed tenant isolation and operations.
Customer-designed isolation, logging, encryption and testing.
Deployment model
Cloud-only SaaS (e.g. Mambu)
Cloud-only SaaS on provider-managed infrastructure.
Self-hosted SAMFCore
Self-hosted on customer-controlled or appointed-provider infrastructure.
Software rights
Cloud-only SaaS (e.g. Mambu)
Continuing access under an active subscription.
Self-hosted SAMFCore
Perpetual continuing usage rights under the applicable licence.
Source code
Cloud-only SaaS (e.g. Mambu)
Not publicly presented as a standard purchase option.
Self-hosted SAMFCore
Optional full source code with a qualifying perpetual licence.
Pricing model
Cloud-only SaaS (e.g. Mambu)
Recurring subscription, often with volume or per-user components.
Self-hosted SAMFCore
One-off perpetual licence from CHF 295,000; no SAMFCore per-user or per-transaction-volume software fees.
Transaction-volume software fees
Cloud-only SaaS (e.g. Mambu)
Can scale with users, accounts or transaction volume.
Self-hosted SAMFCore
No SAMFCore transaction-volume software fee under the perpetual model.
Architecture
Cloud-only SaaS (e.g. Mambu)
Cloud-native composable banking on the provider’s platform.
Self-hosted SAMFCore
Modular: accounts, payments, cards, crypto, compliance and back-office in one environment.
Provider choice
Cloud-only SaaS (e.g. Mambu)
Provider ecosystem and partner integrations.
Self-hosted SAMFCore
Customer-selected providers integrated through the API framework.
Maintenance
Cloud-only SaaS (e.g. Mambu)
Provider-managed updates and patching.
Self-hosted SAMFCore
Perpetual source-code customers may maintain via Swiss AMF, their own team or appointed developers.
Data and security boundary
Cloud-only SaaS (e.g. Mambu)
Provider-managed tenant isolation and operations.
Self-hosted SAMFCore
Customer-designed isolation, logging, encryption and testing.
For a balanced view of the security responsibilities involved in self-hosting, read the perpetual vs SaaS security guide.
For EMIs and financial institutions
Why EMIs and Financial Institutions Choose Self-Hosted Perpetual Licensing
E-money institutions, banks and other licensed financial-services providers often have specific requirements around data sovereignty, audit evidence, operational resilience and long-term technology control. Perpetual licensing and on-premise deployment are designed to address those requirements.
Permanent software rights
Continuing usage rights under the perpetual licence remain with the licensed entity; access does not depend on renewing a SaaS subscription.
On-premise and private-cloud control
EMIs and financial institutions can deploy within their own or appointed infrastructure, supporting data-residency, sovereignty and operational-resilience requirements subject to the agreed architecture.
Regulatory evidence and audit
Direct control of the environment can support infrastructure logs, access records, configuration evidence, penetration testing and disaster-recovery testing aligned to the institution’s control framework.
Source-code review and maintenance
Qualifying licences allow source-code review, independent maintenance and the use of internal or appointed developers within the agreed licence scope.
No volume-based software fees
Under the perpetual model there are no SAMFCore per-user or per-transaction-volume software fees, so customer and payment growth does not re-price the core software layer.
Resilience and vendor independence
Perpetual rights and source-code access can reduce dependency on a single software vendor’s renewal, pricing and roadmap decisions.
Self-hosting is strongest where the organisation has mature infrastructure, security and governance capabilities. On-premise deployment is available where the agreed architecture supports it.
Who Is a Self-Hosted Mambu Alternative Best Suited For?
There is no universal winner. The right fit depends on operating priorities, regulated activities, ownership requirements and the institution’s infrastructure maturity.
When cloud-only SaaS may be the better fit
- want a fully managed cloud-native core-banking platform
- have major deposits or lending requirements
- want the provider to manage continuous upgrades and patching
- do not require source-code ownership or on-premise control
When a self-hosted SAMFCore alternative may be the better fit
- already own or are building a licensed financial-services business
- want a self-hosted alternative to cloud-only SaaS banking software
- want perpetual software rights rather than an indefinite subscription
- want optional full source code
- want fiat and crypto functionality in the same platform
- want more control over infrastructure, security and development
- want a broader operational stack including compliance, back office and white-label brands
- want to select and integrate their own external providers
Own Your Core Banking Software
A perpetual SAMFCore licence from CHF 295,000, optional full source code and self-hosted deployment give a qualified institution continuing usage rights and direct control over its financial-services environment.
FAQ
Self-Hosted Mambu Alternative FAQ
Is SAMFCore a self-hosted alternative to Mambu?
Yes. SAMFCore can be deployed as a self-hosted platform within infrastructure controlled by the customer or its appointed provider, whereas Mambu is publicly positioned as cloud-native SaaS. With a perpetual licence and optional full source code, a self-hosted SAMFCore deployment gives a qualified institution continuing usage rights and direct control over the environment.
How much does a SAMFCore perpetual licence cost?
A SAMFCore perpetual software licence is a one-off cost from CHF 295,000 for one licensed legal entity. Under the perpetual model there are no SAMFCore per-user or per-transaction-volume software fees. Optional support and source-code packages change the total; current options are in the licence configurator.
How is perpetual licensing different from SaaS banking software?
A SaaS banking platform charges a recurring subscription, often scaled by users, accounts or transaction volume. A SAMFCore perpetual licence is a one-off cost with continuing usage rights and no SAMFCore volume-based software fees, so growth does not re-price the core software layer.
How is SAMFCore’s architecture different from cloud-only SaaS banking?
SAMFCore is a modular platform—accounts, payments, cards, crypto, compliance, back-office and white-label in one environment—designed for self-hosted deployment and customer-selected providers. Cloud-only SaaS banking runs on the provider’s managed infrastructure, with the provider controlling hosting, updates and the release schedule.
Does SAMFCore include source code?
Yes. Full source code is available with a qualifying perpetual licence, enabling internal or appointed-developer maintenance within the agreed licence scope.
Is SAMFCore suitable for EMIs and financial institutions?
Yes. EMIs, banks and licensed financial-services providers are a core SAMFCore use case, particularly where data sovereignty, audit evidence, operational resilience and long-term technology control matter. SAMFCore is the software layer; regulated banking, EMI licensing, custody, card issuing and KYC/AML screening remain with customer-selected providers and the institution’s own permissions.
Does SAMFCore replace Mambu’s deposits and lending?
Not directly. Mambu has deep traditional core-banking capabilities including configurable deposits and lending. SAMFCore provides account and ledger functionality within a broader platform and is not positioned as a primary lending product. The right choice depends on the institution’s priorities.
Is self-hosting right for every institution?
No. Self-hosting is strongest where the organisation has mature infrastructure, security and governance capabilities. Institutions that want a fully managed platform and do not require source-code ownership may prefer cloud-only SaaS. Read the perpetual vs SaaS security guide for a balanced view.
Comparison methodology
Last reviewed: September 2026
Based on Mambu’s publicly available product information reviewed in September 2026 and current SAMFCore product documentation. Mambu may change its products and commercial terms. Buyers should verify current requirements directly with each provider.
Mambu is a trademark of its respective owner. References are for identification and factual comparison only; no affiliation or endorsement is implied.
Evaluating a self-hosted Mambu alternative?
See whether SAMFCore’s perpetual licensing, optional source code and self-hosted deployment fit your institution’s operating model.