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.
How we built it. The technical decisions, architecture choices, and engineering tradeoffs behind running managed servers on infrastructure you own.
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.
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.
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.
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.
We built a secure overlay network to manage your servers without a single open port. Then it became a cross-provider VPC.
We don't stack cookies.
Two essentials and one optional. That's the whole stack.
No advertising. No ad networks. Privacy policy