Proofed, pressed,
and ahead.

The .pyxl format: async loader, server actions, and the React component in a single file — server-rendered, hydrated, hot-reloading, file-based routing.

Declare plugins in pyxle.config.json; they wire services, middleware, and their own schema at startup. WebSocket endpoints and the client navigation cache landed in the same release.

Edge caching with per-route TTLs, sanitized production errors, layout loaders, and a faster static path.

Route-shape changes — new pages, renamed loaders, layout moves — apply live, without restarts or cache-clearing rituals.

Reproducible two-box benchmarks against six frameworks, load generator on its own hardware, losses shown alongside wins.

HEAD output rebuilt through a sanitising allowlist, CSRF exemptions matched on path boundaries, oversized form posts failing loud.

pyxle serve --workers N: independent server processes per core, sync endpoints threadpooled, small assets served from memory. This site runs it.

pyxle-db (SQLite, PostgreSQL, MySQL behind one explicit-SQL API) and pyxle-auth (argon2id sessions, RBAC, API tokens) — every claim enforced against live database servers in CI.

A launch program: the first five community plugins that meet the published standards are recognised as ecosystem pioneers, with the spotlight and a roadmap seat. The bar is public; the race is to the bar, not to the submit button.

The Phase B design discussion is open — how plugins will ship their own API endpoints, then whole pages. Founding authors co-design it.

pyxle-auth providing its own sign-in endpoints out of the box; webhook plugins owning their URLs with the right CSRF posture.

Sign-in screens, dashboards — and the admin-panel moment this framework should eventually have.

The DatabaseLike idea, generalised: framework-defined interfaces for mail, storage, cache, and more, so providers (Postmark, SES, S3, R2…) are swappable by config, not code. Pyxle ships the interface; the community ships the adapters — one recommended pick per capability, alternatives behind it.

Mail, storage, jobs, observability — the plugins the ideas page calls for, built by the community or by us.

Write .tsx in your .pyxl, and get loader-data types generated from the Python side — the request that comes up most, answered end to end.

Type-hint a Pydantic model on an @action and get parsing, validation, and clean 422s for free — Python-native, FastAPI-familiar.

renderToPipeableStream under the hood: Suspense boundaries in .pyxl, a loading.pyxl convention, first paint before the slowest loader finishes.

pyxle build --static for pages that never change, per-route revalidation for the ones that rarely do — serve stale, re-render in the background.

A local dashboard that shows the app the way the framework sees it: every route with its loaders and actions, fire test requests at them, watch cache state, and an overlay that maps any element on screen back to the .pyxl that rendered it.

Diagnostics, completions, and go-to-definition that cross the Python↔JSX boundary; pyxle check growing into a real linter.

Engineering notes and honest write-ups — how the SSR pool works, what the benchmarks taught us, what broke.

The release where minor versions stop being allowed to break you. It lands when the plugin API has proven itself, not on a date.

Managed hosting from the people who write the framework: push a Pyxle app and skip the server story entirely — with AI scaffolding in the mix. In development; the newsletter hears it first.