Work

Our work, by domain.

Most of what we build ships under our partners’ names. So we describe it by the domains we work in, and share the rest in qualified discussions, under NDA.

Commerce platforms

Point-of-sale, ERP and commerce systems for businesses with many locations, products and ways to sell. We build them as configurable platforms, so that one core can carry many brands.

What we bring

  • configurable catalogues, pricing and roles
  • white-label, multi-tenant cores
  • integration with payments and operations
  • operation that holds up when the connection doesn’t

Financial infrastructure

Systems that let merchants, businesses and institutions carry out financial operations inside a regulatory framework. The work sits in the protocols, the life of each transaction, and the controls around them.

What we bring

  • transaction integrity
  • identity and access control
  • auditability
  • interoperability between systems

Healthcare data

Clinical data rarely arrives clean. We bring it together into one model, keep the source of every value, and send what is uncertain to people for review.

What we bring

  • integration with existing systems
  • normalisation and data quality
  • provenance and lineage
  • review queues

Governed AI

Multi-agent systems, retrieval and AI assistants that work inside real processes. Each one has evaluation, clear limits, and a person who signs off where it matters.

What we bring

  • multi-agent design
  • retrieval grounded in authorised sources
  • evaluation and confidence signals
  • human review and audit trails

Engineering enablement

A controlled way for teams to build with AI on complex, long-lived systems: clear policies, review gates, and models that can run on the organisation’s own infrastructure.

What we bring

  • a secure development lifecycle
  • review gates for AI-generated code
  • quality controls in delivery pipelines
  • in-house or on-premises models

Web, mobile, backend and cloud delivery, in service of all of the above.

Confidential by design.

We sign a mutual NDA before any technical detail is exchanged, and we never name a partner without written approval. What we can say in public:

products shipped
8
partners
5
domains
5

Questions

Why don’t you name the organisations you work with?

Because most of them ask us not to. We sign a mutual NDA before any technical detail is exchanged, and we never name a partner without written approval. In qualified discussions, under NDA, we show architecture materials and demonstrations.

Do you only work in these domains?

They are where our depth is. Work outside them needs a good reason, and if we are not the right fit, we will say so on the first call.

Do you hold certifications such as SOC 2 or HIPAA?

No, and we don’t claim any. For regulated work, we agree the compliance requirements in writing before design starts, and build to them.

Want to see more than we can publish?

Architecture materials and demonstrations are shared under NDA, after a technical call.