Skip to content
Ledger Rocket

Buyer guide / Deployment ownership

What changes operationally when we run a ledger in our own cloud?

Agree who owns the deployment and who performs each operating task. Cover upgrades, monitoring, access, backup and recovery testing, and incident response. Turn those responsibilities into a deployment acceptance plan.

Choose the operating model as well as the location

Running software in your cloud gives your team a different set of responsibilities from consuming a managed service. Identify the people who will respond to an alert, approve a change and restore service. Include the bank and processor integrations in that discussion, since a healthy ledger process and a healthy end-to-end money flow are different checks.

The Ledger Rocket approach

Ledger Rocket’s deployment offering includes managed service, customer-cloud and on-premises options. Use the deployment discussion to agree the supported target environment, service responsibilities and access arrangements. Validate that agreed configuration with the team that will operate it.

Work through these cases

  • Walk through the upgrade and incident-response responsibilities.
  • Agree the recovery objectives and demonstrate the corresponding recovery test.
  • Verify support access and the monitoring needed for the selected integrations.

Discuss your flow

Bring your hosting requirements and operating responsibility matrix. Use them to choose a deployment model and define the evidence required before handover.

Book a demo