Perpetual vs SaaS vs Source-Code Banking Software: A 2026 Buyer's Guide
Summary
Banking software is sold in three main ways. SaaS rents you a hosted service: quick to start, low upfront cost, but fees recur and often scale with volume, and you depend on the vendor to keep operating. A perpetual licence gives you an indefinite right to use the software in your own environment for a one-time fee; it is not ownership of the intellectual property, and support and upgrades are usually a separate contract. A source-code licence adds the code itself, so your engineers can change and maintain it, at the highest upfront cost and with the greatest internal responsibility. None of the three is a banking licence. The right choice depends on your time horizon, engineering capacity, regulatory plan and exit requirements, and the contract wording matters more than the label.
Methodology and limitations
This guide explains licensing models in general terms and then describes how four white label banking software vendors publicly package their licences. Vendor information comes only from their own websites, reviewed on 11 October 2026. We did not see contracts, test software, audit security or obtain quotes for competitors. Where a term was not publicly stated, we say so. Prices and rights change; treat every vendor statement as a starting point for diligence, and have a lawyer review the final licence agreement.
For a feature-level comparison of the same vendors, read our SAMFCore vs Crassula vs SDK.finance vs Velmie comparison.
Three models, defined
SaaS (software as a service)
The vendor runs the platform and you pay a subscription, often with a platform fee plus charges per active user, account or transaction. You get a working environment quickly, the vendor handles hosting, patching and upgrades, and your team focuses on product and compliance. The trade-offs are recurring cost, limited control over the roadmap and release timing, data residency set by the vendor's infrastructure, and continuity risk if the relationship ends.
Perpetual usage licence
You pay once for a right to use a defined version and scope of the software indefinitely, usually deployed on your own servers or private cloud. "Perpetual" describes the duration of the right, not ownership. Updates, security patches and support normally require a separate maintenance agreement. If you stop paying for support, you can usually keep running the software you have, but you stop receiving new versions.
Source-code licence
You receive the source code and the right to modify and build it, under terms that may be annual or one-time. This gives the deepest control: your team can fix defects, add features and keep operating even if the vendor disappears. It also makes you responsible for code quality, secure development, dependency updates and merging any vendor releases. Some vendors market this as "source code ownership"; legally, the vendor usually still owns the IP unless the contract assigns it.
Decision matrix
The table summarises typical characteristics. Contracts vary, so use it to frame questions rather than as a guarantee of any vendor's terms.
| Criterion | SaaS / subscription | Perpetual usage licence | Source-code licence |
|---|---|---|---|
| Upfront cost | Low to moderate | High, one-time | Highest, one-time or annual |
| Recurring licence fees | Yes, for as long as you use it | Usually none for the licence itself | Annual or none, depending on term |
| Fees that grow with volume | Common (users, accounts, transactions) | Often excluded; confirm in contract | Often excluded; confirm in contract |
| Who hosts | Vendor | You or your chosen host | You or your chosen host |
| Time to first environment | Fastest | Depends on your infrastructure | Depends on your infrastructure and team |
| Customisation depth | Configuration and vendor roadmap | Configuration, APIs, vendor-built changes | Full code-level changes |
| Upgrades | Automatic, on vendor schedule | Under a separate support agreement | Your team merges vendor releases, if licensed |
| Continuity if vendor fails | Weak unless data export and transition terms exist | Software keeps running; escrow advisable | Strongest; you hold the code |
| IP ownership | Vendor | Vendor (usage right only) | Vendor, unless IP is expressly assigned |
| Internal engineering need | Low | Moderate (DevOps, integrations) | High (developers, security, QA) |
| Best fit | Fast pilots, small teams | Long-horizon operators wanting cost control | Institutions needing independence and deep change |
Licence vs IP ownership: what you actually buy
Intellectual property (copyright in the code, trade secrets, sometimes patents) stays with its owner unless a written assignment transfers it. A licence is permission to do specific things: run, copy for backup, modify, sublicense to affiliates, offer to end customers under your brand. A perpetual licence lasts indefinitely; a source-code licence adds the right to see and change the code. Neither, by itself, makes you the owner.
This matters in three situations. First, resale: if you sell your business, can the licence be assigned to the buyer or does a change of control need vendor consent? Second, derivative works: if your developers extend the code, does your company own those changes, and can you keep using them if the licence ends? Third, valuation: investors and acquirers will discount a platform whose rights can be terminated or whose transfer needs consent.
Vendors describe this differently. SAMFCore describes its perpetual licence as continuing rights to use the software for the licensee's own operations, with the licensee keeping ownership of its own data. SDK.finance uses the phrase "full source code ownership" for its source-code licence, and Velmie says source-code delivery secures "full IP and assets in your books". These are marketing descriptions; the legal position depends on the grant and assignment clauses of each contract, which we have not reviewed.
Source-code escrow
Escrow is a middle path between a usage licence and full source code. The vendor deposits source code, build instructions and documentation with an independent agent, and the agent releases it to you if defined events occur, such as insolvency, abandonment of the product or a material support failure. WIPO describes software escrow as a way to balance the vendor's interest in protecting its code with the licensee's interest in continuity.
Escrow is only as good as its details. Ask how often deposits are refreshed, whether the deposit is verified by building it, whether the release includes rights to modify and use contractors, and what happens to third-party components. SAMFCore states that its source code may be placed with an independent escrow provider for release on defined continuity events. Escrow terms for SDK.finance, Velmie and Crassula were not described on the pages we reviewed.
Upgrades, support and security
In SaaS, upgrades arrive automatically, which is convenient but means you accept the vendor's timetable. With perpetual and source-code licences, upgrades depend on a maintenance contract or your own team. Banking software handles money and personal data, so security patches are not optional: budget for them in every model.
Public examples: SAMFCore says updates, security maintenance and technical support run under a separate support agreement, and that there is no mandatory maintenance agreement for perpetual licensing. SDK.finance lists periods of bug and vulnerability fixes, updates and follow-up support as part of its source-code offer. When comparing, ask for: the support term, response and resolution times, how security advisories are communicated, the price of renewing support, and how long each version is supported before you must upgrade.
A source-code licence adds an engineering question: if your team modifies the core, every vendor upgrade must be merged. Keeping changes in extension points or separate services, rather than editing core modules, keeps upgrades manageable.
A five-year cost model
Licence fees are only part of the cost of running a white label banking platform. Over five years, integrations, regulated provider fees, hosting, staff and security work often exceed the licence itself. The template below lists the lines to price in every model. We deliberately leave out figures: competitor prices for these models were not published on the pages reviewed, and your integration and provider costs depend on your markets and volumes.
| Cost line | SaaS | Perpetual | Source code | Notes |
|---|---|---|---|---|
| Licence or subscription | Years 1–5 | Year 1 (one-time) | Year 1 or annual | Check volume tiers and indexation |
| Implementation and integration | Year 1 | Year 1 | Year 1 (often larger) | Banks/EMIs, card issuer, KYC, custody, FX |
| Hosting and infrastructure | Usually bundled | Years 1–5 | Years 1–5 | Include DR, backups, environments |
| Support, maintenance and upgrades | Usually bundled | Years 1–5 if contracted | Years 1–5 or in-house | Security patches are not optional |
| Internal engineering staff | Low | Moderate | High | Often the largest hidden cost |
| Security and compliance assurance | Shared | Yours | Yours | Pen tests, audits, certifications you pursue |
| Third-party provider fees | Years 1–5 | Years 1–5 | Years 1–5 | Same in all models; scale with volume |
| Customisation | Limited or quoted | Quoted per change | In-house | Ongoing product roadmap |
| Exit and migration reserve | Years 4–5 | Lower | Lowest | Data migration, parallel running |
Two points usually decide the comparison. First, volume sensitivity: if your plan involves growth in accounts or transactions, a fee that scales with volume can overtake a one-time licence within the five years. Second, staff: a source-code licence is only economical if you already have, or will hire, engineers to maintain it. For reference, SAMFCore publishes starting prices of CHF 80,000 per year (annual licence), CHF 325,000 one-time (perpetual) and CHF 620,000 (perpetual plus full source code); SDK.finance, Velmie and Crassula ask buyers to request a quote. Published starting prices are not an all-in cost. See also our banking platform cost guide and build vs buy analysis.
Lock-in and exit
Lock-in has three layers: the software, the data and the regulated partners. Source code reduces software lock-in, but you can still be locked in by proprietary data formats or by provider contracts that only work through one vendor's integration. In SaaS, exit risk is highest because the service stops when the contract ends.
Good exit terms include a documented data export in standard formats, a defined transition-assistance period at agreed rates, continued read-only access during migration, and clear deletion obligations. Test an export during the trial. For long-horizon operators, a perpetual licence plus escrow or source code means the platform can keep running while you plan any migration on your own timetable.
How four vendors package licences
Based on official pages reviewed on 11 October 2026. "Not publicly established" means we did not find the information, not that it is unavailable.
| Vendor | SaaS / hosted | Annual licence | Perpetual / lifetime | Source code | Public prices |
|---|---|---|---|---|---|
| SAMFCore | Not the focus; customer-controlled deployment | Yes (annual licence) | Yes (perpetual usage licence) | Yes, in Perpetual + Full Source Code and Enterprise Global | Starting prices published |
| SDK.finance | Yes (SaaS) | Yes (annual source-code option) | Yes (lifetime, one-time option) | Yes (source-code licence) | Quote |
| Velmie | Yes (cloud) | Not publicly established | Not publicly established | Yes (source-code delivery) | Quote |
| Crassula | Platform offered as a service, per its product pages | Not publicly established | Not publicly established | Not publicly established | Not publicly established |
SAMFCore
SAMFCore lists an annual licence, a perpetual licence, a "Perpetual + Full Source Code" package and an Enterprise Global package, deployed in customer-controlled environments with customer-selected providers. Under the perpetual model it states there are no transaction-volume software fees and no mandatory maintenance agreement; hosting, maintenance and provider costs are separate. Its perpetual licence page lists the costs not covered, such as hosting, card issuer and KYC provider fees. Disclosure applies: this site is operated by SAMFCore's company.
SDK.finance
SDK.finance offers SaaS and a source-code licence, with an annual option (lower initial expenditure) and a lifetime option (single one-time investment, no recurring licence fees). Its source-code explainer describes hosting the backend on your own infrastructure, on-premises or private cloud, and modifying and extending it through its API. It is a strong candidate for developer-led teams that want a financial core they can change.
Velmie
Velmie offers three deployment models: cloud, on-premises and source-code licence with full source-code delivery. That makes it one of the vendors where buyers can start hosted and keep a route to code-level control; pricing and licence duration are not published and need a quote.
Crassula
Crassula presents a white-label digital banking platform, banking and payment API, crypto and white-label apps, with developer documentation. We did not find public statements on perpetual licences, source-code access or pricing. Ask the vendor directly; absence from the website is not evidence that an option does not exist.
Software rights are not regulatory permissions
A software licence, however broad, does not authorise you to take deposits, issue e-money, issue cards or hold client crypto assets. In Switzerland, banking licences are granted by FINMA; EU e-money and payment-institution permissions are granted by national authorities; membership of a self-regulatory organisation (SRO) under the Swiss Anti-Money Laundering Act (AMLA) is a different status again, covering financial intermediaries, and is not a banking licence. Card issuing needs a licensed issuer or BIN sponsor, and custody needs a suitably authorised custodian.
This is why the regulatory plan should be settled before the licence model. If you will operate through licensed partners, check that the software already integrates them. If you are acquiring a company with existing memberships or provider relationships, confirm in due diligence what transfers and what needs re-approval. Our licensing requirements guide and due diligence guide cover this in more detail.
Buyer checklist: clauses to read before signing
- Grant clause: is it a usage licence, a source-code licence, or an IP assignment? Which entities and affiliates may use it?
- Term and termination: does the licence survive termination of support, a change of control, or a dispute?
- Scope: modules, environments, number of production instances, territories and white-label brands covered.
- Volume: confirm in writing whether any licence fee depends on users, accounts, transactions or revenue.
- Source code: which repositories, build scripts, documentation and third-party components are included?
- Modification and derivative works: who owns your changes, and may you use contractors?
- Escrow: agent, deposit frequency, verification testing and release triggers.
- Support and upgrades: duration, response times, security-patch commitments, renewal pricing and end-of-life policy.
- Data and exit: export formats, timelines, transition assistance and deletion certificates.
- Open-source and third-party licences embedded in the product, and who is responsible for their compliance.
- Warranties, liability caps, IP infringement indemnity and governing law.
- Regulated partners: which banks, EMIs, issuers, custodians and KYC providers are already integrated, and in which countries.
Score each vendor against your own weights for these items. A simple 1–5 scale per clause, weighted by importance to your business, is usually enough to make trade-offs visible.
Frequently asked questions
Does a perpetual software licence mean I own the software?
No. A perpetual licence normally grants an indefinite right to use the software within the contract scope; the vendor keeps the intellectual property. SAMFCore, for example, describes its perpetual licence as continuing usage rights, not a transfer of IP. Ownership of IP only moves under an explicit assignment clause.
Is SaaS always cheaper than a perpetual licence?
Not necessarily. SaaS usually has a lower upfront cost, but fees often recur and may scale with users or transactions. Perpetual licences cost more upfront but can avoid volume-linked licence fees. Compare a five-year total that includes hosting, support, upgrades, integrations and third-party provider fees.
Which vendors publicly offer source code for banking software?
In the official pages reviewed on 11 October 2026: SAMFCore offers full source code with its "Perpetual + Full Source Code" and Enterprise Global packages; SDK.finance offers a source-code licence with annual or lifetime options; Velmie lists source-code delivery alongside cloud and on-premises. Crassula licensing terms for source code were not publicly established; ask the vendor.
What is source-code escrow and do I need it?
Escrow places the source code with an independent agent who releases it to the licensee on defined events such as vendor insolvency or support failure. It is most useful if you hold usage rights without source code. Check the release triggers, how often deposits are updated and whether build instructions are included.
Do updates and support come with a perpetual licence?
Usually they are contracted separately. SAMFCore states that updates, security maintenance and support run under a separate support agreement and that no maintenance contract is mandatory. SDK.finance lists defined periods of fixes and updates in its source-code offer. Always check the length, scope and renewal price of support.
Does any software licence include a banking licence?
No. A software licence is a contract for technology. Banking licences (in Switzerland granted by FINMA), EU e-money or payment-institution permissions, and Swiss SRO membership under AMLA are separate regulatory statuses. Regulated services are provided by licensed banks, EMIs, card issuers and custodians.
How do I avoid vendor lock-in with banking software?
Negotiate data-export formats and timelines, documented APIs, a transition-assistance period, escrow or source-code rights, and licence terms that survive the end of support. Test a data export before signing. Lock-in also comes from regulated providers, so check those contracts as well.
Which licensing model should I choose?
Choose SaaS for speed and minimal operations, a perpetual licence for long-term cost control and private deployment, and source code when you need deep customisation or independence from the vendor roadmap and have engineers to maintain it. Many buyers combine a perpetual licence with escrow.
Next steps
Write down your five-year volume plan, engineering capacity and regulatory route first, then ask each shortlisted vendor for a draft licence agreement, support terms and a test environment. To compare features, read the four-vendor comparison; to understand the software category, see white label banking software. Vendor pages: SAMFCore licensing, SDK.finance pricing, Velmie delivery, Crassula.
Sources and further reading
Official pages reviewed on 11 October 2026.
SAMFCore
SDK.finance
- SDK.finance source code licence
- SDK.finance pricing and licensing options
- SDK.finance: how the source-code version works