Featured story
A Tuesday Where the Thing Works
Signup's open — quietly since the 7th, properly since the 9th. Beta runs a couple of months, aiming for Q4. No confetti, just a working form.
Jan PeterBlog
The Log
Unfiltered reality. Technical decisions, product updates, and the building journey.
Jan PeterFrom the archive
RSSMonth 67
Month 67 of building strackt. You can't plan your way to production-ready — you have to iterate through what only breaks once real infrastructure is on the line.
Month 66
Month 66 of building strackt. Two testers read it the same wrong way in one week — the fix wasn't the price, it was the sign on the door. Early access is close.
The walks we didn't take
The breaks used to be where the hard decisions got made. Now the work is refinement, and I can do that from a campervan — it just costs a couple of walks.
We wipe your server. Here's why.
The first thing we do to your new VPS is erase it — disk and all. That's not the risky part; it's the only honest way to manage a server we didn't build.
Tearing out Filament
We're tearing out the last of Filament's customer-facing panel — one of the final pieces before early access, and what it actually took to do it without breaking things.
Craft or compulsion
Seven weeks from early access, and I still can't tell where craft stops and can't-let-it-go begins. On details — and the date that makes me choose.
A production 500, fixed from the terminal
A 500 on our own live site, diagnosed and fixed without leaving the terminal — every step one CLI command, right up to the one we still had to SSH for.
The early devlog lives here now
Four years of building notes from projectstrackt.dev — the original strackt devlog — now live here in The Log. Same story, one place, old links still work.
Month 65
Month 65 of building strackt. CVE patching, self-renewing certs, an installable CLI — the boring month that mattered. And finally a date for early access.
The app is the subject
For a long time the admin was a Filament CRUD panel — honest forms over the data, and it tells you nothing about what matters. So we tore the customer side out and rebuilt it: your app as the subject, the server as supporting cast.