Deployment type

Banks have complete choice to deploy the Vault platform depending on their specific needs and strategic objectives. Our global team of delivery experts ensures that every deployment is executed to the highest standard.
Digital greenfield banks

We work with leading innovative banks and fintechs around the world to launch new, digital-first banks. Launching a digital bank on an old technology stack can be a painful experience. The front-end app may look good but the time taken to build and launch innovative product propositions is too slow and costly.

Building a digital bank on the Vault platform is a different experience: our smart contracts architecture allows banks to launch any product, and our API-first, microservices-based technology allows banks to integrate with any system.

We enable rapid speed-to-market through:

  • Pre-built integrations with best-in-class technology vendors
  • Pre-built banking products that can be launched as they are or tuned to meet customer needs
  • Our network of highly trained partners who can support banks anywhere in the world
Mox by Standard Chartered

Banks build new, cloud-native technology stacks alongside their existing core in coexistence deployments. Existing and back book products run on the old core, while new products are launched on the new Vault-enabled cloud-native stack. Often the new and old stacks share customer channels, which means the customer can start using products on the new stack without disrupting their user experience.

Deploying the Vault platform as a coexistence architecture allows banks to launch new products and features alongside existing product offerings (e.g. reward accounts) using our coexistence approach. This approach offers a seamless end-customer experience, in which the customer will never observe a changing of systems behind the scenes.

Our technology enables the simple routing of information, and ease of migration, between a mainframe and the Vault platform. Pluggable architecture in this approach allows for existing mainframe components to be replaced, over time, by modern platforms.

Once a bank has tested the Vault platform, they may choose to complete a full migration of all their customers.

The Vault platform cannot only be used to manage a bank's front book of products but the existing bank can also be migrated onto our platform. Complex back book products can be recreated, and our migration tooling de-risks the migration process and enables the migration of a customer's complete financial history.

Banks have migrated, or have committed to migrating, more than 289 million accounts onto Vault Platform.

The Vault platform enables full data migrations where a bank wants to move all its existing products, ledgers and account records from a legacy system to our core. Vault Platform is best placed to enable this, as 1) the Universal Product Engine can perfectly replicate the financial behaviour of all the bank's existing products, and 2) our migration APIs provide a rich set of functionality that allow seamless, gradual migrations, avoiding the need for the higher risk 'big bang' approaches.

Specifically, our migration tooling de-risks and minimises core banking migration timelines through a simple-to-use API entry-point architecture, which has been designed to performantly support common migration use cases and help banks of all shapes and sizes overcome their migration challenges. For example, configurable dependency fields enable banks to send legacy data to Vault Core in any order instead of in highly orchestrated sequential loads, which saves time and reduces the risk of manual error over migration events.
Read more
Arrow icon pointing down
Read less

Migration strategies

Banks can simulate and prove how migrated products will behave over a set period before migration through time-series testing. For example, by simulating a known past period on the legacy core, banks can prove that Vault Core is operating as their old core would have done, providing confidence to business stakeholders in the lead-up to a production migration event.

Our technology supports a variety of migration strategies and approaches, which can be changed at the flick-of-a-switch, allowing for account-by-account cutover at the most granular level. Tranched migrations are supported by dormancy flags which can keep data stable between data load and go-live. The real-time API event-driven architecture of Vault Core makes parallel run or 'production proving' migrations simpler to execute compared to batch-based legacy cores.

Migration partners

We have a selection of migration partners who have built tooling that integrates with Vault Core's migration APIs, providing pre-configured data transformation, quality and reconciliation capabilities that can save time and effort in migration programme delivery. Additionally, Vault Core is provided with a full suite of migration delivery processes, documentation, and access to internal migration experts who can advise banks on strategy and best practices.

Atom bank
Sign up to our newsletter
Thank you! You will now receive some incredible content in your inbox!
Oops! Something went wrong while submitting the form.
For information about how we use your data please read our privacy policy.