Selected practice
Software systems
Backend services in Go, Python and TypeScript: queues, schedulers and the paths that must not drop a record.
Read the scopeportfolio@nullframe:~$ profile --overview
Build reliable systems. Explain every decision.
An Austin engineering practice that designs, builds and reviews backend systems for teams that need a senior pair of hands.
STATUS / BOOKING FROM NOVEMBER
Open channel
Overview
Systems, signals and shipped practice.
An Austin engineering practice that designs, builds and reviews backend systems for teams that need a senior pair of hands. Most work runs six to twelve weeks against a fixed scope agreed in writing first.
Selected work
A clear record of process and responsibility.
Selected practice
Cloud architecture
AWS and Cloudflare environments defined in code, with the migration plan written before anything moves.
Read the scope
Selected practice
Security review
A read through auth, secrets and data handling before somebody else finds the gap.
Read the scopeIndex
Capabilities, arranged as a working index.
Software systems
Service design, refactors and the unglamorous parts: retries, idempotency, backfills.
Cloud architecture
Terraform, container platforms and a cost model you can actually read.
Security review
Threat modelling, dependency review and a written list of what to fix first.
Data platforms
Ingest pipelines, warehouse modelling and reporting that agrees with itself.
Developer tooling
CI that finishes, local stacks that boot, and release steps nobody dreads.
Technical discovery
Two weeks inside an existing codebase, ending in a written assessment.
Before work begins
Scope first. Estimates after.
Send the shape of the problem and whatever is already written down. A scope note and a range come back before anyone talks about a start date.
Start an enquiryWhat clients say
“He read our Terraform before the first call and came back with a migration plan we could argue with.”