Run NewLedger as a fully managed service or inside an approved customer-controlled cloud environment. The platform stays consistent; infrastructure governance and operating responsibility change.
Operating model
Select the infrastructure boundary
NewLedger
Managed cloud
NewLedger-operated environment
Customer cloud
Approved BYOC environment
Regional
Placement
Controlled
Operations
Coordinated
Delivery
Both models run the same NewLedger product architecture. The difference is where infrastructure governance sits and how platform operations are coordinated.
Managed cloud
NewLedger operating boundary
The shortest path to production. NewLedger operates the supported cloud environment and platform lifecycle.
Bring your own cloud
Shared operating boundary
Infrastructure governance stays with the customer; platform operations and the supported topology are coordinated with NewLedger.
The right model depends on which organisation must govern the cloud account, network boundary, release coordination, and day-two operations.
BYOC is not unmanaged software delivery. NewLedger and the customer agree the supported environment and operating model across four control areas.
Access model, privileged roles, SSO, and operational elevation.
Ingress, egress, private connectivity, and approved traffic paths.
Monitoring, alert routing, log access, and incident coordination.
Backups, recovery procedures, releases, and resilience testing.
BYOC is available to qualifying organisations. Supported providers, regions, topology, service levels, responsibilities, and commercials are confirmed by agreement.
Tell us about residency, networking, identity, audit, availability, and operational ownership. We’ll help define the appropriate delivery model.
Talk to the platform team