<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bext Blog</title>
    <link>https://blog.bext.dev</link>
    <description>Release notes, technical deep-dives, and ecosystem news from bext.</description>
    <language>en</language>
    <atom:link href="https://blog.bext.dev/rss.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Five Frameworks, One App: an honest, uncached benchmark</title>
    <link>https://blog.bext.dev/2026-06-five-frameworks-one-app</link>
    <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
    <description>We built the same app in Next.js, Remix, Astro, Qwik, and bext, then forced every one of them to render fresh on each request and measured it. bext renders fastest — and the fairness rule cost Next.js a 5× drop it had been hiding.</description>
    <category>engineering</category>
  </item>
  <item>
    <title>Kilobytes, Not Megabytes: Resumability and Real HMR in bext</title>
    <link>https://blog.bext.dev/2026-06-resumability-and-hmr</link>
    <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
    <description>bext islands now resume instead of hydrate — they ship ~0.6KB gzipped, run nothing on load, and survive an edit with their state intact. Here&apos;s how it works, what we measured, and what we deliberately left out.</description>
    <category>engineering</category>
  </item>
  <item>
    <title>Multi-Tenant by Default: Hosting Every Site in One Process</title>
    <link>https://blog.bext.dev/2026-06-multi-tenant-hosting</link>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <description>Running web apps one-process-per-app is exactly why running many of them is expensive. bext shares one render pool across every site on the box. Here&apos;s the model — and where it breaks down.</description>
    <category>engineering</category>
  </item>
  <item>
    <title>The Day One Render Took Down Every Site</title>
    <link>https://blog.bext.dev/2026-06-pool-stall-postmortem</link>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <description>On June 10, a single page render wedged a worker in our shared V8 pool — and within seconds, every site on the server stopped responding. A blameless post-mortem of how one render became everyone&apos;s outage, and the defense-in-depth that bounds it now.</description>
    <category>engineering</category>
  </item>
  <item>
    <title>Building Your First bext Plugin in 10 Minutes</title>
    <link>https://blog.bext.dev/2026-03-building-plugins</link>
    <pubDate>Sat, 28 Mar 2026 00:00:00 GMT</pubDate>
    <description>bext plugins let you add custom middleware, transforms, and cache backends. Here&apos;s how to build one with QuickJS, WASM, or Python.</description>
    <category>tutorial</category>
  </item>
  <item>
    <title>Migrating from Vercel to bext in 15 Minutes</title>
    <link>https://blog.bext.dev/2026-03-migrating-from-vercel</link>
    <pubDate>Thu, 12 Mar 2026 00:00:00 GMT</pubDate>
    <description>A step-by-step guide to moving your Next.js app from Vercel to bext — with zero code changes, automatic TLS, and ISR that just works.</description>
    <category>guide</category>
  </item>
  <item>
    <title>What Our Benchmarks Actually Mean</title>
    <link>https://blog.bext.dev/2026-02-benchmarks-explained</link>
    <pubDate>Tue, 24 Feb 2026 00:00:00 GMT</pubDate>
    <description>Everyone claims their framework is fast. Here&apos;s exactly how we measured bext against Next.js, why we report ratios instead of headline numbers, and where the gains actually come from.</description>
    <category>engineering</category>
  </item>
  <item>
    <title>Inside bext: How We Built a Single-Binary Web Runtime in Rust</title>
    <link>https://blog.bext.dev/2026-02-architecture-deep-dive</link>
    <pubDate>Tue, 10 Feb 2026 00:00:00 GMT</pubDate>
    <description>A look at the architecture decisions behind bext — the shared V8 render pool, on-demand compilation, the ISR stampede guard, and the watchdog that keeps one bad render from taking down the server.</description>
    <category>engineering</category>
  </item>
  <item>
    <title>Introducing bext: The Rust-Powered Runtime That Replaces Your Deployment Stack</title>
    <link>https://blog.bext.dev/2026-01-introducing-bext</link>
    <pubDate>Thu, 15 Jan 2026 00:00:00 GMT</pubDate>
    <description>Today we&apos;re open-sourcing bext — a single Rust binary that replaces nginx, certbot, Cloudflare WAF, Redis, PM2, and Vercel.</description>
    <category>release</category>
  </item>
  </channel>
</rss>