Public identity
sbdmfp.dev is the public edge of a private workspace: software, services, and infrastructure made by one independent builder and operator.
The short version
I build tools and small systems that are easier to inspect, operate, and change than they are to advertise. The interesting part is often the boundary around a service: the route, the policy, the rollback, and the evidence.
The public surface stays deliberately incomplete. It shows enough to make the work legible without turning a private home lab into a catalogue of targets.
How I work
Expose the smallest useful interface, and keep administration somewhere private.
Say what a service does, what it does not do, and which assumptions it depends on.
Back up before mutation, validate after it, and leave a way back when the edge gets complicated.
What stays private
Credentials, internal hostnames, administrative dashboards, personal records, and operational details do not belong in the public index. Keeping them private is not a missing feature; it is the intended boundary.
Explore the surface
Read the projects, use the documented DNS service, or inspect the public Git boundary.
A final note
This page will grow if there is something useful to add. It will stay small if there is not.