Engineering
Software and infrastructure architecture, with specialist depth when your project needs it.
Software & infrastructure architecture
We design the systems and the infrastructure they run on, so that what gets built is easy to change, reproduce and hand over. We work with the cloud provider you already use.
What we do:
- System and Service Design: Services, boundaries and how the parts fit together
- Data and Integration Points: How data flows, and how the new connects to the systems, databases and queues you already have
- Second Opinion: A straight review of an existing design before you commit to it
- Modernisation: A path from an ageing system to a current one, in steps you can ship
- Kubernetes: Cluster setup, Helm charts and deployments
- Terraform: Infrastructure as code, so it can be reviewed, reproduced and handed over
- CI/CD: Build, test and release pipelines with GitHub Actions
- Cloud Providers: We've worked with AWS and OVHcloud, and we work with the provider you already use
Good fit if:
- You're starting a system and want the architecture right from the start
- You want a second opinion on an existing design, or a plan to modernise it
- You want your infrastructure in code and reproducible, with Kubernetes or CI/CD for a new or existing project
Specialisations
When your project needs them, we go deeper in three areas: .NET, distributed ledgers, and Canton and Daml.
.NET
C# and .NET are our main language and platform. We build and modernise the systems that your teams run on.
What we do:
- Main Platform: Services and APIs in C# and .NET, designed to be testable
- Modernisation: Moving older .NET applications to current .NET
- Integration: Connecting to the back-office systems, databases and message queues you already have
- Automated Testing: Unit and integration tests around the business rules
Good fit if:
- You have a system in .NET that needs new features or an upgrade
- You want someone who knows your domain, not just the framework
Distributed ledgers
We've designed and built core blockchain protocols, and we connect ledgers to the systems you already run. We work with the platform that fits your problem, and we start by asking whether a shared ledger fits at all. If it doesn't, we say so.
What we do:
- Protocol Development: Designing and building core blockchain protocol software
- Fit Assessment: Does a ledger actually fit? A straight answer, including "no".
- Ledger Integration: .NET services that read from and write to ledger and blockchain nodes and their APIs
- Typed Libraries: Typed .NET libraries and code generation, so your code works with ledger data instead of raw payloads
- Test Networks: Development and CI against a local test network instead of a shared one
Good fit if:
- You're considering a ledger and want a straight answer on fit
- You want your .NET systems to talk to a ledger
- You want a second opinion on an existing ledger design
Canton & Daml
Canton and Daml are a core specialisation. We apply the architecture, .NET and ledger work above to one network, and it is where our open-source work lives.
What we do:
- Architecture: Parties, privacy model, and how the ledger connects to your existing systems
- Smart Contracts: Daml templates, choices and workflows
- .NET SDK: Our open-source Canton .NET SDK (code generator, runtime types, and gRPC and JSON Ledger API clients) connects .NET systems to Canton
- Local Test Networks: Development and CI against a local Canton network with canton-localnet
- Infrastructure as Code: Our open-source Terraform provider for Canton
- Validator & Node Operations: We run our own validator on the Canton Network, and can set one up for you or run it on your behalf: deployment on Kubernetes with Helm, upgrades with Canton and Splice releases, health checks and alerts, and handover documentation so your team can run it themselves
Node operations are a working-hours service: there is no uptime guarantee and no round-the-clock on-call.
We maintain the open-source Canton .NET SDK: a Daml-to-C# code generator, runtime types, and gRPC and JSON Ledger API clients, published as packages on NuGet. It is built under a Canton Foundation Development Fund grant, and a minimal end-to-end demo shows it in use.
Good fit if:
- You're considering Canton and want a straight answer on fit
- You're building on Canton and need Daml and integration work
- You want a Canton validator without building the know-how in-house first
How we work
Every project starts with a conversation. We understand the problem first, then pick the technology that fits, which is often the simplest one. If you need us to build it, we do. If you need us to run it, we can do that too. We can also lead the project and the team, not just write the code.
The path usually looks like:
- Understand the problem, your systems and your constraints
- Design the architecture: services, data and integration points
- Build it, with tests around the business rules
- Set up the infrastructure, as code
- Hand it over, or keep running it: your choice
