TypeScript engine
Block themes compiled to a clean-room WordPress renderer on edge isolates. Cold starts in 0–5 ms — the hot path for your anonymous traffic.
The thesis[01] — WHY NOW
Everyone else caches WordPress.
We replaced its engine.
Every “fast WordPress” host is a cache play — quick while the cache is warm, WordPress-slow the moment it isn't: logged-in users, search, carts, the first hit after every publish. We rebuilt the runtime itself on edge isolates, so the miss path is nearly as fast as the hit path.
tezpress — uncached, dynamic0 ms
Edge-cache CDN — cache hit0 ms
Premium WP host — cache hit0 ms
Typical managed WP — uncached0 ms
Illustrative p50s from public benchmarks (architecture doc §1). The point: we're faster on a miss than they are on a hit.
The Render Ladder[02] — 100% COMPAT, DAY ONE
Speed is a progress bar,
not a migration cliff.
Every site lands with full WordPress compatibility, then climbs. Routes graduate tier by tier — and each rung shaves the path to first byte.
Hook-compatible runtime
Dynamic blocks and the most popular plugins re-implemented on the same actions-and-filters contract — priority-exact, via the same hooks API Gutenberg uses.
Real PHP, managed
Classic themes, the long tail of plugins, all of wp-admin — real WordPress on managed PHP, always behind the edge cache, never your hot path.
North-star metric[03] — WHAT WE SHIP AGAINST
p50 TTFB · uncached< 0 ms
p99 TTFB< 0 ms
measured from0 continents
isolate cold start0–0 ms
Dynamic requests, zero cache, real visitor geography. Cache hits are boring here — the architecture makes the miss path nearly as fast as the hit path.