advapayResources
Back to ResourcesBack to Resources
Blog post

Open-source core banking: the hidden risks for regulated fintech companies

By Gustav Korobov, Chief Delivery Officer at AdvapayPublished: 13 November 2026Technology14 min read

For regulated fintech companies, choosing open-source core banking is a decision about long-term operational responsibility, not just license fees. The institution still needs reliable controls, security, support and evidence that its platform is fit for the services it plans to provide.

Comparison of community-supported open-source, ready-made and in-house core banking responsibilities.

Core banking choices shift delivery and maintenance responsibilities, not the institution's regulatory accountability.

Over more than ten years of delivering core banking projects, I have heard the same message again and again in our clients'' feedback on their dealings with regulators. Supervisors, particularly in Europe, look very closely at whether a financial institution''s IT systems have proper control mechanisms and reliable support in place, and whether the business depends on factors it cannot influence.

This is why the choice of core banking software matters well beyond the technology team. Open-source core banking can look attractive: access to source code, freedom to customize and no license or SaaS subscription fees. For startups preparing to apply for an Electronic Money Institution (EMI) or Payment Institution (PI) license, the appeal is easy to understand. But for a platform that underpins account management, transaction processing and financial accounting, the apparent cost saving should not be the deciding factor.

The discussion below focuses on self-managed, community-supported deployments. Open-source platforms with commercial maintenance and contractual support need to be assessed against their actual arrangements, rather than assumed to carry the same support risks.

01

Source code is not a production-ready platform

Open-source projects can be useful foundations for prototypes, internal tools or individual software components. However, access to source code is not the same as a complete core banking platform. Projects differ substantially in functionality, documentation, development maturity and ongoing maintenance.

Software that handles basic accounts and transactions may still lack the capabilities a financial institution needs in daily operations: comprehensive accounting, transaction reconciliation, audit trails, exception handling and administrative controls. In a ready-made core banking product, these are part of the established feature set.

02

Regulatory readiness is not built in

When applying for an EMI or PI license, a business must demonstrate that its governance, internal controls and technology infrastructure are appropriate for the services it plans to provide. The EBA Guidelines on authorization and registration under PSD2 (EBA/GL/2017/09) set out the information applicants must submit, including governance arrangements, internal control mechanisms and security-related documentation.

Since 17 January 2025, the Digital Operational Resilience Act (DORA) has applied EU-wide requirements for ICT risk management, incident management, resilience testing and ICT third-party risk to financial entities within its scope. The framework is also evolving: PSD3 and the Payment Services Regulation (PSR) form the package intended to replace PSD2. On 29 October 2026, the Council of the EU adopted its first-reading positions on PSD3 and the PSR. That legislative milestone is distinct from the new rules becoming applicable. A core banking platform therefore needs to keep pace with regulatory change, not only meet today''s requirements.

These rules are technology-neutral. Regulators do not prohibit open-source software, but the obligations are the same whether a platform is built in-house, assembled from open-source components or acquired from a vendor. Most general-purpose open-source projects are not designed around the requirements that apply to EMIs and PIs, so closing the gap falls to the institution. The resulting development, documentation and testing work adds cost and uncertainty to the licensing timeline.

03

Banking partners run their own due diligence

Regulators are not the only ones asking questions. Before providing safeguarding accounts, IBANs, access to payment schemes or other services, partner banks and payment providers carry out their own due diligence on a fintech company''s operations, including its technology, security, support arrangements and business continuity.

A self-assembled platform without a contractual support provider, documented controls and security evidence can make these reviews longer and harder to pass, delaying access to the infrastructure the business needs to launch.

04

Open-source licenses come with obligations

Free to use does not mean free of conditions. Permissive licenses such as Apache 2.0 or MIT impose relatively few obligations, while copyleft licenses such as the GPL or AGPL can require source code to be made available when their conditions are triggered. Distribution of covered software can trigger GPL source-code obligations; under the AGPL, users interacting remotely with a modified version over a network must also be offered access to its corresponding source code.

For a fintech company that has invested in proprietary functionality, this raises questions about intellectual property and confidentiality. The licenses of the core project and all its third-party dependencies should be reviewed by legal specialists before development begins.

05

Cybersecurity extends beyond the source code

Publicly accessible code can be inspected, but that does not guarantee that vulnerabilities will be found or fixed promptly. An open-source platform typically depends on numerous third-party libraries and frameworks, and a vulnerability in any of them can affect the whole system.

Without a commercial maintenance provider, the institution is responsible for security across the entire stack: application code, dependencies, infrastructure, authentication, access management and updates. This requires continuous specialist involvement, not a one-time assessment. In a financial environment, even a small vulnerability can lead to unauthorized access, exposure of sensitive data or transaction disruption.

06

No guaranteed support when critical systems fail

Community-maintained projects generally provide no contractual commitments on response times, critical bug fixes or long-term maintenance. A community forum or public issue tracker is not a Service Level Agreement (SLA).

When payment processing fails, the institution may have no guaranteed access to the original developers and no certainty about when the issue will be resolved, while customers are affected and compliance concerns grow. It must therefore plan and budget for the expertise and staff needed to investigate incidents and restore operations on its own. The risk is even higher when a project has limited development activity or an inactive contributor community.

07

Key-person risk

A heavily customized open-source platform often depends on a small number of engineers who understand how it has been modified. If they leave, critical knowledge about the system, its customizations and its integrations can leave with them.

Without a vendor maintaining the product and its documentation, rebuilding that knowledge can be slow and expensive, and in the meantime the institution''s ability to resolve incidents or implement regulatory changes is reduced. This is exactly the kind of dependency regulators expect an institution to identify and manage.

08

The hidden costs of open-source core banking

The absence of license fees is only one part of the total cost of ownership. Deploying and running a self-managed open-source core banking platform involves ongoing expenditure on:

  • Initial development, configuration and customization
  • Dedicated engineering and DevOps resources
  • Infrastructure deployment, hosting and monitoring
  • Cybersecurity assessments and vulnerability management
  • Development of compliance-related functionality
  • Integration with banks, payment systems and third-party providers
  • Software maintenance, testing and version upgrades
  • Technical support and incident resolution

These costs continue after go-live. Extensive customization also makes future upgrades harder, as changes to the underlying project may conflict with in-house functionality. Over several years, a solution chosen to avoid license fees can turn into a costly internal technology program.

Gustav's perspective

The real comparison is not free versus paid software, but building and continuously maintaining a financial technology platform versus implementing a product already developed for this environment.

Gustav KorobovChief Delivery Officer at Advapay
09

Integrations add another layer of complexity

Core banking software relies on external infrastructure for IBANs, payments, foreign exchange, identity verification and other services. An open-source platform may offer APIs, but that is not the same as established connections with the providers a particular business needs.

Each new integration can become a separate project covering specifications, authentication, processing logic, error handling and reconciliation, and it must be maintained as providers update their services. A ready-made platform with existing integrations and provider connectivity reduces this work and shortens the path to launch.

10

Financial data integrity leaves little room for experimentation

Account balances, ledger entries, transaction statuses, fees, reversals and reconciliation records must remain consistent throughout the transaction lifecycle, including when payments fail, providers become unavailable or messages are processed more than once.

Incorrect handling of retries and duplicates, incomplete reversals, wrongly applied exchange rates or mismatches between internal accounting and external settlement data directly affect financial accuracy and the reliability of customer account information. A generic open-source project may offer basic transaction functionality without the accounting depth and exception management these scenarios require.

11

Scaling creates further demands

As a fintech business grows, its platform must handle higher transaction volumes, more currencies, new payment methods, new jurisdictions and additional partners. With a self-managed open-source solution, the organization carries the full burden of adapting the architecture, performance, databases and monitoring.

A system that looked inexpensive at launch may need significant restructuring, and resources intended for business growth end up being spent on maintaining the underlying infrastructure.

12

What about the risks of a ready-made platform?

A ready-made platform is not risk-free either. The most obvious concern is dependency on the vendor, which is precisely the kind of external dependency regulators expect institutions to manage and which DORA addresses through its ICT third-party risk requirements. The difference is that this risk can be identified, contractually defined and controlled. At Advapay, we address it in several ways:

  • Choice of deployment model. Macrobank core banking software is available as SaaS or under a software license. Under the license model, the platform is hosted by the client, on premises or in its own cloud, giving it full control over its infrastructure.
  • Contractual support. Our support commitments are set out in SLAs.
  • Continuous maintenance. We release updates on a regular basis, including security improvements.
  • Exit options. Where required, exit arrangements can be agreed, including the option to acquire the source code.

For a regulated institution, this turns vendor dependency from an open question into a managed, documented risk, which is much harder to achieve with a community-supported project.

13

Comparing three approaches: open-source, ready-made and built from scratch

The table below summarizes typical differences between adapting a community-supported open-source project, implementing a ready-made platform and developing a system from scratch. Actual capabilities, costs and support arrangements depend on the specific solution and contractual agreements.

Three approaches to core banking

ConsiderationOpen-sourceReady-made software (e.g. Macrobank)Built from scratch
Upfront software costUsually no license fee, implementation costs applySaaS subscription or software license fee, depending on the modelSubstantial initial development investment
Time to technical launchPotentially 6-12 months* if major adaptations are neededFrom 3 months* for projects of standard complexityOften 12+ months* for a new platform
Product track recordVaries by projectLive client deployments and referencesNo established product track record at launch
Regulatory documentationOften assembled and adapted by the institutionTechnical and control documentation provided by the vendorDocumentation developed alongside the system
Budget predictabilityCustomisation effort can be difficult to estimateSoftware, implementation and support scoped and quoted upfrontDevelopment scope and expenditure can evolve
Core functionalityVaries, additional modules may be requiredEstablished features available within the productAll required features must be developed
IntegrationsAdditional development often neededExisting APIs and integrations with banks and payment providersConnections developed individually
Implementation resourcesInternal engineering or external specialistsVendor implementation team and delivery expertiseDedicated development and delivery team
Technical supportCommunity support, internally organized supportContractual support with SLA commitmentsInternally organized support
Security evidenceTesting and evidence depend on the implementationVendor security materials and test evidenceSecurity controls and testing built into the project
Maintenance & upgradesCustomisations can complicate updatesRegular product releases, including security updatesFull in-house release and upgrade program
ScalabilityDepends on architecture and modificationsEstablished architecture, capacity assessed for the client's volumesScalability must be designed, tested and validated
Deployment flexibilityOn-premises or cloud, depending on the projectVendor-hosted SaaS, or client-hosted cloud/on-premises under a licenseClient-managed cloud or on-premises
Licence obligationsOpen-source license terms (e.g. copyleft) must be reviewedDefined in the SaaS or software license agreementThird-party component licenses must be reviewed
Key-person and vendor dependencyDepends on internal team and key engineersVendor dependency managed through SLA, exit plan and source code optionsDepends on internal team and key engineers
ConsiderationUpfront software cost
Open-sourceUsually no license fee, implementation costs apply
Ready-made software (e.g. Macrobank)SaaS subscription or software license fee, depending on the model
Built from scratchSubstantial initial development investment
ConsiderationTime to technical launch
Open-sourcePotentially 6-12 months* if major adaptations are needed
Ready-made software (e.g. Macrobank)From 3 months* for projects of standard complexity
Built from scratchOften 12+ months* for a new platform
ConsiderationProduct track record
Open-sourceVaries by project
Ready-made software (e.g. Macrobank)Live client deployments and references
Built from scratchNo established product track record at launch
ConsiderationRegulatory documentation
Open-sourceOften assembled and adapted by the institution
Ready-made software (e.g. Macrobank)Technical and control documentation provided by the vendor
Built from scratchDocumentation developed alongside the system
ConsiderationBudget predictability
Open-sourceCustomisation effort can be difficult to estimate
Ready-made software (e.g. Macrobank)Software, implementation and support scoped and quoted upfront
Built from scratchDevelopment scope and expenditure can evolve
ConsiderationCore functionality
Open-sourceVaries, additional modules may be required
Ready-made software (e.g. Macrobank)Established features available within the product
Built from scratchAll required features must be developed
ConsiderationIntegrations
Open-sourceAdditional development often needed
Ready-made software (e.g. Macrobank)Existing APIs and integrations with banks and payment providers
Built from scratchConnections developed individually
ConsiderationImplementation resources
Open-sourceInternal engineering or external specialists
Ready-made software (e.g. Macrobank)Vendor implementation team and delivery expertise
Built from scratchDedicated development and delivery team
ConsiderationTechnical support
Open-sourceCommunity support, internally organized support
Ready-made software (e.g. Macrobank)Contractual support with SLA commitments
Built from scratchInternally organized support
ConsiderationSecurity evidence
Open-sourceTesting and evidence depend on the implementation
Ready-made software (e.g. Macrobank)Vendor security materials and test evidence
Built from scratchSecurity controls and testing built into the project
ConsiderationMaintenance & upgrades
Open-sourceCustomisations can complicate updates
Ready-made software (e.g. Macrobank)Regular product releases, including security updates
Built from scratchFull in-house release and upgrade program
ConsiderationScalability
Open-sourceDepends on architecture and modifications
Ready-made software (e.g. Macrobank)Established architecture, capacity assessed for the client's volumes
Built from scratchScalability must be designed, tested and validated
ConsiderationDeployment flexibility
Open-sourceOn-premises or cloud, depending on the project
Ready-made software (e.g. Macrobank)Vendor-hosted SaaS, or client-hosted cloud/on-premises under a license
Built from scratchClient-managed cloud or on-premises
ConsiderationLicence obligations
Open-sourceOpen-source license terms (e.g. copyleft) must be reviewed
Ready-made software (e.g. Macrobank)Defined in the SaaS or software license agreement
Built from scratchThird-party component licenses must be reviewed
ConsiderationKey-person and vendor dependency
Open-sourceDepends on internal team and key engineers
Ready-made software (e.g. Macrobank)Vendor dependency managed through SLA, exit plan and source code options
Built from scratchDepends on internal team and key engineers

*Indicative planning estimates for technical implementation only, not market benchmarks or licensing timelines; actual schedules depend on scope, integrations and team capacity.

Regulatory responsibility stays with the institution

  • Important: Prior use in a regulatory application does not mean that a regulator has approved or certified the software. The financial institution retains regulatory responsibility under every model. Features, documentation and supplier commitments must be confirmed for the chosen product.

Conclusion: looking beyond the initial cost

The absence of license fees can make open-source core banking look attractive, but for regulated fintech companies the decision has to cover much more: regulatory requirements, partner due diligence, license obligations, cybersecurity, technical support, key-person risk, integrations and long-term scalability.

What our clients consistently hear from regulators is that a financial institution must stay in control of its critical systems and must not depend on factors it cannot influence. Overlooking this at the outset can lead to unforeseen costs, security issues, operational disruption and difficulties in meeting regulatory obligations as the business grows.

Common questions about open-source core banking

Do regulators prohibit open-source core banking software?

The rules discussed here are technology-neutral. A regulated institution must demonstrate appropriate governance, controls, security and operational resilience regardless of whether its platform is open source, built in-house or supplied by a vendor.

Who retains regulatory responsibility when core banking is outsourced?

The financial institution retains regulatory responsibility under every model. Vendor documentation and contractual support can help it meet its obligations, but do not transfer those obligations or mean the software is regulator-approved.

What costs remain when there is no software license fee?

Development, customization, engineering, hosting, monitoring, security, compliance-related functionality, integrations, maintenance and incident response still need funding. Those costs continue after go-live.

How can a fintech manage dependency on a ready-made platform vendor?

Assess deployment options, contractual support commitments, maintenance arrangements and an exit plan. Where available and agreed, source-code acquisition can be part of the exit arrangements. Confirm the terms for the specific product and contract.

Gustav Korobov

Gustav Korobov

Chief Delivery Officer, Advapay

Gustav Korobov is Chief Delivery Officer at Advapay, responsible for delivering the Macrobank core banking platform into live, regulated operations - matching the right delivery model to each client and getting the platform, licensing, and banking access to launch together. He works with founders on the build-versus-buy decision and what it really costs.

Across Advapay''s 100+ licensing and platform projects, he has seen which choices keep a launch on schedule and on budget, and he focuses on turning a platform purchase into a working business rather than an isolated tool.

Platform deliveryBuild vs buy strategyFintech launch economics
View full author profile →

Discuss your core banking requirements

If you are currently comparing these approaches, our team can help you assess what your licensing plans and business model require.

Share

Share this resource

Send this page to a founder, operator, or colleague working through the same questions.

Keep up with Advapay

Get Advapay''s updates on fintech infrastructure, licensing and operational requirements.

Regulatory RadarAdvapay Digest

No spam. No sales calls. Unsubscribe any time.