Choose your country or region

Security

One bank’s data never touches another’s.

Your own database. Your own keys for secrets and documents. Two people on every big decision – and every action on record.

Separation

Not a row in someone else’s database.

Your customers’ data never shares a database with another bank. Inside yours, a second rule checks every query again.

Your bank also has its own encryption key for stored secrets and documents.

  • A separate database for every bank
  • A second database rule that limits every query to one bank
  • Another bank’s data answers “not found”
By default

Three rules we don’t bend.

Not settings a bank can forget to switch on. They’re how the platform is built.

Encrypted by default.

Each bank’s stored secrets and documents are sealed with that bank’s own key.

One bank. One database.

Your customers never share a database with another bank’s. Asking for theirs finds nothing.

Two people. Every big decision.

High-risk approvals and policy changes need a second person – never the one who asked.

Staff access

A password alone gets nobody in.

Staff sign in through your company’s single sign-on (SSO), and their roles follow your directory groups. Emergency admin accounts still work if SSO fails – and every use is recorded.

  • Single sign-on with SAML 2.0 or OpenID Connect
  • Staff accounts created and removed from your directory with SCIM 2.0
  • A second factor for every staff account, plus passkeys
Audit

If it happened, it’s on record.

Every sensitive action – a decision, a download, a setting change, a staff view of an account – is recorded with names and reasons.

Exports come with signed, chained manifests, so you can prove nothing changed after export.

  • Saved in the same step as the change it describes
  • The service itself can’t change or delete it
  • Export to your security monitoring, with signed files
Built for regulated work

Named controls. No adjectives.

Your risk team will ask what protects you. These are the answers – built in from the start.

Each bank in its own database

A request for another bank’s data finds nothing.

Two people for high-risk decisions

The same person can never approve twice.

A record nobody can edit

Saved with every change, with names and reasons.

Your company login for staff

Single sign-on, with accounts that follow your directory.

Two-step sign-in for all staff

Every staff account needs a second factor.

Exact money, every time

Sent twice by mistake, paid once.
Assurance

Evidence your security review can check.

Controls built in, tested before go-live and mapped to the standards your board asks about.

  • BuiltControls above: built and testedEvery control on this page runs today
  • BuiltInfrastructure defined as code for AWSReviewable, repeatable environments
  • Built with youIndependent penetration test before go-liveAn outside team tries to break in
  • Built with youBackup and restore drill before go-liveProven recovery, not just backups
  • Built with youCustomer-managed encryption keysYour keys, in your own key store
  • Built with youDedicated deployments for one bankYour own environment, nobody else’s
  • Built with youISO 27001 and SOC 2 control mappingFor your due diligence pack
Ask to see it

Not a promise. A response code.

Two of the controls on this page, as your IT team would see them.

Another bank’s data, not found.Asking for another bank’s account returns not found – never a hint it exists.
Sent twice, paid once.A retry after a timeout replays the first answer. Money moves once.
Questions

Security questions, answered straight.

Are you ISO 27001 or SOC 2 certified?
No. The controls are designed with those standards in mind, and mapping them is on our roadmap. We won’t claim a certificate until we hold one.
Is our whole database encrypted with our own key?
Your stored secrets and documents are, with your bank’s own key. In a shared environment the database itself uses that environment’s key. Planned dedicated deployments can use your key for the whole database.
Can your staff see our customers’ data?
Our operators sign in separately from your staff and manage banks, not customers. Time-limited, bank-approved support access is on the roadmap.
Where will our data be hosted?
On AWS, in a region agreed with your bank before deployment.
Pilot programme

Bring your security questionnaire.

We’ll walk your security team through the architecture, the controls and the open items.

  • Architecture walkthrough
  • Answers to your security questionnaire
  • A clear list of what is still in progress