image 1
image 2
image 3

What an Engagement Covers

We are engaged for four properties, not for whatever needs building. Work outside them is declined or referred, which is the only way the guarantee means anything.

The four things we answer for

  • Security by design. The architecture, not a review at the end.
  • Regulatory fit. The rules your product answers to, treated as versioned data.
  • Private AI. Models running where your data already lives.
  • Immutable records. Proof that what was written was not altered afterwards.

How it runs

  1. Assess. What data is involved, how sensitive it is, and which regulations you answer to. This is short, and it is where most of the value is decided.
  2. Design the architecture. For where the system will actually live: your private cloud, your own servers, or fully on-premises.
  3. Build. With the components that deliver the guarantees, and with open-source or proprietary pieces chosen for what you are permitted to run.
  4. Deploy inside your perimeter. Your data stays on your infrastructure at every stage, including during deployment.
  5. Audit and harden. Test the deployment and verify that access controls behave the way the architecture says they do.
  6. Hand over. Documentation, deployment guidance, and the knowledge to operate and extend the system without us.

The components you inherit

We are not a consultancy that writes a report and leaves. Reusable core components carry the recommendations into the product: tenancy, a dockerised identity service, and outbound messaging. Your product adopts them instead of building the same foundations again, and they stay in your codebase afterwards.

They are not sold separately and there is no licence to renew. They are part of an engagement, which is why the advice arrives already implemented.

A team working from shared dashboards during an engagement

What you keep

  • The product, the roadmap and the customer relationship. All three were always yours.
  • The source, the documentation and the deployment procedure.
  • The ability to operate it without us. If handing over leaves you dependent, the engagement failed.

What we decline

General development capacity, staff augmentation, and work outside the four guarantees. Not because it is beneath us, but because a specialist who accepts everything stops being able to answer for anything.

How it starts

A conversation about the constraints you work under. Bring the regulation you answer to and the thing you are not allowed to send to a third party; those two usually decide the shape of the whole engagement.

Questions we get asked

Schedule a Meeting