Internal tools, data platforms, and the servers underneath them — designed end to end, deployed by hand, and kept running.
Not demos — production systems that carry real workload, real auth, and real data.
Purpose-built dashboards for teams who outgrew spreadsheets — auth, permissions, and workflows shaped around how the business actually operates.
Turning years of raw CSVs and exports into queryable, reconciled datasets — with reports people can actually trust.
Public-facing forms and census tools that feed straight into the backend systems teams already rely on — no manual re-entry.
Wiring language models into existing tools for triage, drafting, and lookup — augmenting the workflow instead of replacing it.
Every project ships to a real server: nginx configs written by hand, TLS certificates managed and renewed, services supervised by systemd, deploys done without ceremony. The boring parts, done properly, are what make the rest reliable.
I design, build, and operate production software — mostly internal tools and data platforms for teams that need something sturdier than a spreadsheet and lighter than an enterprise contract. I write the frontend, the backend, the deploy scripts, and the server config, and I'm the one who gets paged if any of it breaks. That end-to-end ownership is the point: software built by the person who also has to keep it running tends to be built to actually keep running.