01
Security
Threat model before schema. Least privilege at every boundary, secrets that never reach a client, dependencies pinned and reviewed. Security is a property of the architecture, not an audit at the end.
Software engineering without compromise.
We design, build and operate systems where correctness, latency and security are requirements rather than aspirations. Small senior teams. Production from week one.
§ 01 — Engineering principles
02
Performance
Budgets are set before the first commit and enforced on every build — payload weight, query time, p99 latency. Fast is a constraint we hold, not a phase we schedule.
03
Architecture
Boundaries you can name, data flow you can draw, dependencies that point one way. Decisions are written down with their trade-offs, so the system survives the people who built it.
§ 02 — What we build
Six kinds of work. If the difficult part is the engineering, it is work we take.
- 01
Product platforms
Multi-tenant systems with real isolation, billing correctness and predictable operations.
- 02
Backend systems
Versioned contracts, strict validation, observable behaviour under load.
- 03
Internal software
The tools a company runs on, built with the rigour usually reserved for customer-facing work.
- 04
Infrastructure-heavy applications
Deployment, networking and failure behaviour treated as part of the product.
- 05
Rebuilds and migrations
Incremental replacement of systems that can never be switched off.
- 06
Performance-critical systems
Profiling, redesign and measured results where latency is the product.
§ 03 — How we work
- 01
Understand
Constraints, load, risk and the business behind them — written down before anything is built.
- 02
Architect
Boundaries, data model and failure modes decided explicitly, trade-offs recorded.
- 03
Build
Small senior teams, short cycles, working software in a real environment from week one.
- 04
Harden
Threat review, load testing, error budgets, failure paths exercised deliberately.
- 05
Ship
Progressive rollout, observability in place, rollback proven before it is needed.
§ 04 — Technical capabilities
Boring technology, used precisely.
Tools follow from constraints. This is what most of our production work runs on today — and what we are prepared to argue about.
- Services
- Go — typed, boring, fast to operate
- Interfaces
- TypeScript, Astro, minimal client JavaScript
- Data
- PostgreSQL, event streams, careful migrations
- Edge
- Cloudflare — static delivery, WAF, Turnstile
- Systems
- Distributed systems, API design, queueing
- Practice
- Applied security, infrastructure as code
§ 05 — Project onboarding
Six questions instead of a contact form.
An engineer reads every answer and replies within one working day — with a technical view, questions, or an honest no.