What we do

Engineering by the day
or the sprint.

Backend and platform engineering, built to run in production and handed over maintainable.

01What we take on

Three categories of work. Most engagements fall into one; some begin in the first and continue into the second.

Build

Services and APIs

Java and Kotlin on the JVM, HTTP and messaging interfaces, relational data access, and the pipeline that puts it into production. Written for the engineer who inherits it.

Remediate

Login and access

Single sign-on rollouts and migrations, OIDC and SAML integrations, directory federation, and the authorisation model underneath. Including the difficult cases: two identity providers required to coexist, or an authentication flow no one is willing to modify.

Sustain

Platform and delivery

Builds, containers, deployment, environments and the observability that makes an incident readable. Typically alongside a team that has outgrown its original setup.

02How an engagement runs

  1. Scope and rate in writing

    An initial call on the requirement, followed by the scope, the rate and the boundaries in writing before work begins. Suitability is established at that stage.

  2. Delivery in your environment

    Your repository, your pipeline and your review process. Access is granted by you, scoped to the engagement and revoked on completion.

  3. Handover as a deliverable

    Decisions and their rationale are documented as they are made. The engagement closes with code your team can maintain unaided.

Out of scope

Managed services, and any arrangement that leaves standing access to your systems in place between engagements. Engagements extend for as long as the work does — an embedded quarter is normal — but each has defined scope and an end date rather than an open-ended seat.

03Terms

Rate

Daily, or fixed scope

A day rate for open-ended work, a fixed price where the scope is stable. Both quoted in writing before the first day.

Contract

Under your terms

Your paperwork, your governing law and your venue, executed as issued.

Invoicing

EU B2B, reverse charge

Monthly in arrears. Peppol e-invoicing for public bodies required to receive structured invoices.

Tell us what you are building

The stack, the shape of the work and the intended timing are sufficient for an assessment of fit.