On building boring, reliable systems that work the first time. PostgreSQL, data provenance, correctness over cleverness, and the craft of infrastructure that doesn't wake you up at 3AM.
The engineering philosophy behind systems that institutional clients depend on: correctness as the floor, not the ceiling.
Why institutional systems must maintain complete provenance. On the difference between what happened and what the data says happened.
Why institutional software is won or lost in the last 10% of implementation. A meditation on craft, edge cases, and finishing.
PostgreSQL, server-rendered HTML, and why we keep reaching for tools that were already stable when we started the firm.
Why we use Postgres as our primary datastore, message queue, full-text search, job scheduler, and time-series database.
We build boring, reliable infrastructure for institutions that cannot afford downtime. Let's talk about your system.
Work with us →