How the cost is structured

SaaS and On-Premise run on the same A3.Bank core. The exact cost depends on your portfolio, jurisdictions and delivery model, and we work that out before anything is signed.

SaaS

A3 cloud

One platform cluster serves several banks on isolated data schemas. A fast start with no infrastructure of your own.

Bank isolation: a separate data schema per bank inside a shared cluster
One software version, rolling updates and feature flags
Sign-in through standard OIDC and OAuth 2.1
Hosted in the target jurisdiction: data residency for Russia and Kazakhstan
Three ways to place a bank: a shared database, a separate schema or a dedicated database

Small and mid-size banks with no infrastructure of their own that need to launch quickly.

On-Premise

The bank's own infrastructure

The same core runs inside the bank's perimeter: on the customer's Kubernetes cluster or on dedicated servers.

A dedicated database for the bank, with no shared schemas
Updates controlled by the customer, an LTS line supported for at least 18 months
Connects to corporate LDAP, Active Directory, SAML or OIDC
An air-gapped mode with no internet access for banks with strict infrastructure-autonomy requirements
Ready Helm chart and docker-compose, Prometheus metrics and Grafana dashboards

Banks with data-localization and infrastructure-autonomy requirements, and large banks with their own IT.

What the quote is built from

There is no public price list: the cost of core banking software always tracks the scale and jurisdictions of a specific rollout.

Client base size

The number of clients served and active accounts.

Transaction volume

The number of payments, transfers and card operations per month.

Back-office users

The number of the bank's staff with access to core-system workstations.

For On-Premise, terms are set in a separate commercial contract based on the module set and jurisdictions involved.

Questions about payment and delivery

Why is there no public price list?

The cost of a banking core depends on the size of the client base, transaction volume, the number of back office users and the set of jurisdictions. We prepare a quote after a conversation about your portfolio and delivery model, before the contract is signed.

Do SaaS and On-Premise differ in features?

No. Both models run on one codebase with every module. They differ in where data is stored, how updates are rolled out and how the platform connects to the bank’s corporate infrastructure.

Can we start in the cloud and move to our own infrastructure later?

Yes. The platform places a bank in a shared database, in a separate schema or in a dedicated database, and backup and restore are done with the platform’s own tools.

How do updates work?

In the A3 cloud the bank receives updates as one version together with other clients. On-Premise, the bank decides when to update, and the long term support line is maintained for at least 18 months.

Let’s work out a quote for your bank

Tell us about your portfolio, jurisdictions and preferred delivery model, and we’ll prepare a quote and walk you through the product.

Request a quote