I build open tools for understanding your data
// The AI is the easy part.
What I build
Your agent re-learns your database every session and never learns what a colleague would tell it in thirty seconds — which column is the real one, which join surprises people, which field died in the migration. dbprint measures the half a database can report, gives you one place to write down the half it can't, and puts both in front of the agent.
A coding agent worth using needs your whole toolchain, and handing it that on your own machine is a bad idea. claudebox gives each session a disposable container with everything the agent needs and only as much of the host as you allow, behind a web interface that renders the conversation — code, diffs, diagrams — with panels for tasks, queued follow-ups, and forking at any point in the history.
A shell setup is a decade of pasted fragments in whatever order they landed, and a new machine means doing it again by hand. profile.d turns each piece into a plugin listed in one file, runs them through a staged lifecycle so order is explicit, and puts a new machine one install away.
All are open source, run on your own machine, and answer to nobody's pricing page. That is not incidental.
What I run
Most of my time goes into one data platform, end to end: a billion messages a year through it. Before that, more than two decades of software engineering across healthtech, aesthetics tech, e-government and freelance work.
Same pattern the whole way through: before AI delivers value, the team has to agree on what the numbers mean. So that's where I'm putting my time.