Doc 02 / Services Capability index — six entries

The capability index.

Everything below is work we do ourselves, at a senior level. The depth is in backend and security engineering; the range covers the whole system. Each entry lists what it actually produces — because a service that doesn't name its deliverables is a service you can't hold to anything.

S-01

Backend engineering

The core of the practice. Production services in Java and Spring Boot: REST APIs with contracts worth versioning, JPA/Hibernate data layers that don't fight the database, PostgreSQL schemas designed for the queries you'll actually run, and microservice boundaries drawn where the domain says — not where the diagram looks nicest. Built for load, audits and a long operational life.

Production services API contracts Data model & migrations Test suites

S-02

Security-conscious design

Not a penetration-testing shop — build-side security, which is where most breaches are actually decided. OAuth2 and SSO integration, JWT session models that expire and rotate correctly, Spring Security configured by someone who has read the filter chain, secure API gateways, least-privilege access design and audit trails that survive a compliance review. Earned on platforms where "security-conscious" was a legal requirement, not a value statement.

OAuth2 / OIDC / SSO Auth & session architecture API gateway hardening Threat model document

S-03

System architecture & advisory

For teams that have engineers but need conviction: architecture for new platforms, design reviews of existing ones, technology selection with the trade-offs written down, and honest assessments of legacy systems — including when the right answer is "don't rewrite it." Advisory output is always a document you own, in language your team can act on without us in the room.

System design documents Architecture reviews Scaling & migration plans Technology assessments

S-04

Frontend & full-stack integration

An API is half a product. We deliver the layer that consumes it: admin panels, operational dashboards, client-facing interfaces — pragmatic, fast and wired correctly into the auth flows underneath. The advantage of a backend-first consultancy doing frontend work is that the seams between the two are designed by the same hands, so nothing is duct-taped at the boundary.

Web interfaces Admin & ops dashboards End-to-end auth flows API integration

S-05

Cloud & deployment

Getting software into production and keeping it there: containerization, CI/CD pipelines that fail loudly and early, environment design with a real separation between staging and production, reverse proxies and TLS done properly, and enough observability to answer "what happened at 3 a.m." Cost-conscious by default — infrastructure sized to the workload, not the résumé.

CI/CD pipelines Container & environment setup Deployment runbooks Monitoring baseline

S-06

End-to-end product delivery

The primary engagement, and the reason the firm exists: take a product from a problem statement to a running system — design, build, deploy, hand over. One senior engineer accountable for the whole chain, which means no gaps between "the architect's intent" and "what actually shipped." Particularly suited to SMEs building operational platforms and international clients who want a single, reliable point of engineering responsibility.

Working product Full documentation Deployed infrastructure Knowledge transfer

§ 02.7 — Engagement models Three shapes

Model A

Advisory

Architecture reviews, design consultation and standing technical counsel. Fixed scope or retainer. You keep every document produced.

Model B

Embedded delivery

A senior engineer working inside your team on a defined system or workstream — raising the bar on review and design while shipping alongside your people.

Model C

End-to-end build

We own the outcome: scope, design, build, deploy, hand over. Milestone-based, with written status you can forward to a board.

Next step

Not sure which entry fits? Describe the problem — we'll map it.

Open Doc 05 / Contact