FOUNDATION
The server
Provisioned, hardened, key-only access, firewalled. nginx serving this page over a domain I wired myself.
software engineer · self-hosted
I don't just
show you the work.
You're standing in it.
This page is served by software I run on a box I administer. Behind it: a version-control system I'm writing from scratch, a VPN built at the packet level, and a live sandbox app you'll be able to break and reset. Every piece hosts itself.
↓ look under the hood
00
the loop
why this isn't a template
Most portfolios describe the work. This one runs it. The version
control you'll browse holds the code for the site you're reading, the VPN
that secures it, and its own source — a repo that version-controls itself.
When I ship the next thing, it becomes another repo in
my git,
shown on my site, watched by my dashboard. It compounds
instead of scattering.
01
the stack
built, not assembled
live
building
FROM SCRATCH
Version control
A git-like system in Python — blobs, trees, commits, refs, content-addressed by hash. It hosts its own code.
building
PACKET LEVEL
The VPN
A real tunnel — virtual interface, encrypted transport — plus a guest keyhole you can step through, sandboxed and self-expiring.
building
PLAY WITH IT
The sandbox app
Log in, get your own seeded copy, add and delete rows, run a report. Isolated per visitor, wiped on a timer. Break it freely.
building
MISSION CONTROL
The dashboard
One screen that watches the whole system — sessions, commits, health — and narrates it back to you.
building
ASK IT ANYTHING
The guide
An assistant wired into the ecosystem. Not a FAQ bubble — it reaches into the repos and the live system to answer.