01active
Infrastructure
Rocky 10 VPS
Guarded provisioning, rootless services, reversible hardening, and explicit evidence boundaries for a small public edge.
Independent systems / 2026
Small systems.
Clear edges.
Software, services, and infrastructure built with an eye for the boundary: what is public, what is private, and what can be explained plainly.
01 Narrow surfaces
02 Explicit limits
03 Reversible changes
The operating idea
Make the boundary
legible.
The interesting work is usually not the service itself. It is the line around it: the route, the policy, the rollback, the evidence.
Public endpoints stay small. Administrative surfaces stay private. Documentation describes the trade-offs instead of hiding them behind a status badge.
Available surfaces
Useful, deliberately scoped.
01active
Encrypted DNS
DoH on the public edge. DoT on the tailnet. No account and no query history.
Setup and policy 02maintainedPersonal forge
Forgejo with HTTPS cloning through the edge and native SSH on a separate hostname.
Clone endpoints 03open workProjects and systems
A concise index of the tools, infrastructure, and experiments that make up the surface.
View the indexSelected work
Built to be understood.
02active
Public service
Encrypted DNS edge
A narrow DoH and tailnet DoT surface backed by filtered resolution, DNSSEC, rate limits, and no query history.
Open surface03maintained
Software delivery
Personal forge
Private-by-default Git hosting with HTTPS through the edge and native SSH on a separate origin hostname.
Open surface