Changelog
Reverse-chronological, and just the real engineering work — the deploy queue, the edge cache, the four ways in, and the price that's live today.
We publish this because "trust us, it works" isn't something you can verify, and a list of what actually shipped is. Every entry below is a real, user-facing change, dated to when it went live rather than when it was decided on — no customer counts, no funding news, no press mentions, because we don't have any of those to report and wouldn't post them here even if we did. This is engineering history, not a highlight reel, and it reads the same whether the week was a good one or not.
New entries land whenever something user-facing actually ships, not on a fixed schedule — check the status page for anything closer to real time.
$11.88 a year (99¢/mo), with $1.99/mo billed quarterly and $2.99/mo billed monthly as the other two options, went live on the pricing page. The custom-domain add-on locked in at +99¢/mo, and none of the three renews at a higher rate than what's shown today.
Seven head-to-head comparison pages and the FAQ went live, each number sourced to the competitor's own current pricing page rather than a marketing claim. The eight-article documentation hub went live the same day.
Terms, privacy, acceptable use and the refund policy all went live in full, each carrying a visible last-updated date instead of a vague "revised periodically" line. All four sit under /legal/, linked from the footer on every page.
Every site now gets a daily backup, kept for seven days, running automatically with nothing to configure or switch on per site. It's the same schedule regardless of plan or how often the site itself changes.
The deploy, status and list tools an AI assistant calls to publish a site landed behind the MCP server — the same primitives the CLI already used, exposed as five distinct tools scoped to deploying, never to billing.
Git push, a zip upload, the CLI and the MCP server all now land in the same deploy queue — one pipeline behind four doors, so a fix to the queue fixes all four routes at once instead of four separate ones.
Static assets now cache at the edge, so a repeat visit in the same region skips the origin fetch entirely and loads from the nearest node instead. It's the same change behind every site on the plan, not an opt-in.
The core job that takes a set of files and turns them into a live site — the piece every deploy route since has been built on top of. Deploys publish strictly in the order they arrive, with the file and count guardrails enforced at upload time rather than discovered after the fact.
What doesn't make this list
Copy tweaks, internal refactors, and fixes that never reached a live site don't get an entry — this page tracks what changed for someone using the product, not every commit behind it. If a change altered what you can do, how much something costs, or what's included, it's here; if it only changed how the code looks on the inside, it isn't.
Join the list and we'll email you once, the day signups open — see what's already built on pricing or the status page.