Service status ·A8 Core™ · The Operating System for Financial Accounts ·The account operating system · API-first
Company · Licensing

A8 Core is licensed to fit your deployment, not the other way round.

Choose where it runs. Choose how you pay. Both are decisions you can revisit.

Where it runs — three options

The same software and the same authorization evidence in all three. The difference is whose infrastructure it sits on.

1 · A8 Core Cloud (SaaS)

Runs on A8 Core’s Microsoft Azure infrastructure. You reach it over HTTPS through the API or the console. No infrastructure to operate, upgrades applied centrally. Recurring subscription, monthly or annual.

2 · Your Azure (BYOC)

You licence the software and deploy it inside your own Microsoft Azure tenancy. Your subscription, your network boundary, your data residency. Subscription or term licence.

3 · On-premises

Runs in your own data centre through Azure Local, Azure Arc or Azure Stack, so you keep Azure’s operating model on your own hardware. Subscription or perpetual licence with annual maintenance. No dependency on external connectivity for daily operation.

Choosing between them

Deployment model and commercial model are independent. Any meter below can be applied to any of the three, and moving between deployments does not require a different licence family.

How you pay — one default, others on request

The default meter is usage-based: billed on API calls and data volume, so cost tracks activity rather than headcount.

ModelBilled onAvailability
Usage-basedAPI calls and data volumeDefault
Per accountAccounts under administrationOn request
Per userNamed platform usersOn request
Flat-rateA fixed, agreed scopeOn request
Cost-plusBuild-to-order workOn request

If the default meter doesn’t fit your procurement, any model above can be applied to any deployment. Rates are quoted per engagement and are not published.

What you get either way

Every deployment is secured by B5 Secure™ and produces the same authorization evidence, whichever meter you’re on.

The same authorization model

Authentication, request signing, workload identity, user identity and authorization stay separate concerns. See A8 Core™ + B5 Secure™.

The same evidence

Each decision carries its caller, purpose, delegation in force and reason code. See Examination support.

The same API surface

One contract on api.a8core.io/v1. See the API reference.

The same account model

45 account types documented publicly, with the full catalogue under Account types.

Tell us where it needs to run.

Deployment, data residency and procurement constraints shape the licence. Start with those and the commercial model follows.

Scroll to Top