Reference architectures
How we would design it
Worked designs for system types we are often asked about. Each covers the problem, the requirements, the components, the decisions we would make and why.
These are reference architectures and engineering scenarios. They are illustrative designs, not descriptions of client projects, and the outcomes listed are the intended results of the design rather than measured results.
Reference Architecture
AI Knowledge Platform
A retrieval-augmented platform that answers questions over enterprise documents and systems, with citations, permission-aware retrieval and full observability.
Reference Architecture
High-Performance Transaction Platform
A microservices platform for financial transactions built on Java, Spring Boot, Kafka, Redis and a relational ledger, designed for correctness first and throughput second.
Reference Architecture
Digital Asset Infrastructure
The off-chain infrastructure behind a digital asset product: blockchain nodes, wallet services, secure key management, indexing, transaction monitoring and an API gateway.
Reference Architecture
Multi-Tenant SaaS Platform
A SaaS architecture that separates the control plane from the application plane and carries tenant identity through every layer, from the edge to the data store.
Engineering Scenario
Agentic Workflow Automation
An engineering scenario for automating a multi-step business process with AI agents that plan, call tools and act under policy checks, human approval and a full audit trail.
Engineering Scenario
RWA Tokenisation Platform
An engineering scenario for representing real-world assets as permissioned tokens, with an off-chain registry of record, enforced transfer controls and continuous reconciliation.
Have a system that needs to work in production?
Tell us what you are building. An engineer will read it and reply within two working days.