How it's built
The principles behind the toolkit.
A lab, not a launch
These are the tools that run one developer’s operation daily. Some are live, some stay internal, some are still prototypes. The status label on each card is the honest state — nothing here is dressed up as a finished SaaS.
Evidence over claims
The portfolio audit is self-built and reproducible: a dated snapshot you can re-run, not an external certification. Where a tool is live you can open it; where it is internal, that is stated plainly.
Models are swappable
LLMs sit behind gateways with tiered routing, so a better or cheaper model is a config change rather than a rewrite. Deterministic cores, AI at the edges — the parts that must stay testable do.
Build-vs-buy is costed
Dependencies earn their place: managed auth over hand-rolled auth, pgvector over a separate vector DB, self-hosting only where data gravity demands it. Choices are made on cost and fit, not novelty.