Small, security-first tools and experiments.
Opinionated, minimal, and designed to be trusted before they are liked.
Products
Secure foundations
Reusable building blocks such as authentication, authorization, and audit trails.
Pieces designed to sit underneath other products, carrying the weight of trust
so the visible layers can stay simple.
Operational tooling
Internal tools, dashboards, and small services that keep systems observable.
Log viewers, control panels, and one-off utilities that turn vague “something feels off”
into concrete signals and actions.
Focused public tools
Narrow, well-defined tools that do one thing sharply—
a small site, a micro-API, a helper for a specific workflow—
built to be easy to adopt and safe to leave running.
Design frameworks
New work will keep following the same lines:
quiet foundations, clear boundaries, and products that are secure enough
to disappear into the background of someone else’s stack.
Shared principles
What all products have in common
- Security as part of the design, not a post-release patch
- The simplest possible surface, with honest defaults
- Logs and transparency over magic
- Fewer features that actually hold up over time