APAC region
Singapore
Application workloads
LedgerBillingReportingImports
Regional cache
Low-latency reads
Regional pub/sub
Async events
Regional workload 1
Platform architecture
Platform Architecture for Modern Accounting
A modern financial system of record engineered for transactional correctness, regional performance, and strict tenant boundaries—without compromising how globally distributed teams operate.
Memory-safe coreACID transactionsMulti-region data
Reference model
Global platform architecture
Ledger core
Regional
Workloads
Consistent
Data layer
Isolated
Tenants
Reference architecture
Globally accessible. Regionally contained.
Requests enter through a global control plane and are routed to the tenant's designated region. Each region carries its own application workloads, cache, and pub/sub, while financial data is committed to a strongly consistent multi-region relational layer.
Product users
Partners & APIs
AI agents
Global entry & control plane
Edge · load balancing · API gateway
IdentityTenant routingPolicy
EMEA region
European Union
Application workloads
LedgerBillingReportingImports
Regional cache
Low-latency reads
Regional pub/sub
Async events
Regional workload 2
Americas region
Iowa
Application workloads
LedgerBillingReportingImports
Regional cache
Low-latency reads
Regional pub/sub
Async events
Regional workload 3
Multi-region relational data layer
Strong consistency · ACID transactions · resilient placement
Tenant boundariesData localityMulti-region resilience
Strict tenant context Region-pinned processing Unified observability
Memory-safe compiled core
Core financial processing is engineered with a memory-safe, compiled architecture and zero-cost abstractions. This provides predictable performance without trading away low-level efficiency.
Strongly consistent financial data
The ledger is backed by an ACID-compatible, globally distributed relational data layer designed to preserve transactional correctness as data and workloads scale.
Strict tenant isolation
Tenant boundaries are enforced as an architectural invariant. Accounting data stays within its owning tenant context; cross-tenant joins are not part of the application data model.
API-first boundaries
Versioned APIs and explicit service boundaries support integrations and automation without requiring direct access to internal data stores.
Region-aware operation
The platform is designed for region-pinned processing and data residency, with deployment choices for organisations that need greater infrastructure control.
Accounting integrity by design
Double-entry controls, transactional updates, permissions, approvals, and traceable activity history are treated as platform concerns rather than optional add-ons.
System boundaries
Designed to keep responsibilities explicit
Ledger domain. Financial transactions are processed within a strongly consistent boundary so balanced postings and related state changes succeed or fail together.
Tenant domain. Every request is resolved inside an authenticated tenant context. Cross-domain data needs use explicit service interfaces, not cross-domain database joins.
Integration domain. External systems, developer applications, and AI agents connect through documented APIs, OAuth-based delegated access, and MCP resources.
Deployment boundary. The same product architecture supports NewLedger-managed cloud delivery and qualifying customer-controlled cloud environments.
Architecture FAQ
Questions About the Platform Model
What technology is NewLedger built with?
NewLedger does not publish vendor or implementation details of its private production stack. At a high level, it uses a memory-safe compiled core, zero-cost abstractions, and an ACID-compatible globally distributed relational data architecture.
How does NewLedger isolate customer data?
Tenant isolation is an architectural invariant. Data access remains within the owning tenant context, and cross-tenant database joins are prohibited by design.
Can NewLedger run in a customer-controlled environment?
Yes. In addition to the managed cloud service, bring-your-own-cloud deployment is available for qualifying organisations by agreement.
Delivery models