Skip to content

Blog

The Log

Everything after the deploy, and the work of building strackt. Technical decisions, product updates, and the unfiltered building journey.

Featured story

The fast part was the preparation

PHP2Shell's fix landed at 13:34 UTC; our customers' PHP servers had it by 15:30. The speed came from being ready. Here's how, and what still broke.

From the archive

RSS

Month 69

Month 69 of building strackt. The PHP CVE day, a story rewritten around what happens after the deploy, and less outreach than I promised.

The freedom to leave

A deploy tool leaves you the maintaining; a managed server keeps the server when you go. We built the way out: stop the management, keep the server.

Month 68

Month 68 of building strackt. More feedback than features, the first five euros of revenue, and a server you can now take back when you leave.

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.

Month 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.