Static-first delivery
Pre-rendered landing pages served directly from Caddy file_server — zero Node overhead for marketing content.
Ships tenant-isolated content at the edge. Static pages served directly from disk; dynamic routes proxied to Node SSR with measurable TTFB and throughput.
Your delivery: —
TTFB — · measured in this browser
Loaded from cache
Phase times are sequential connection steps. TTFB and total are measured from navigation start in this browser and are not the sum of the rows.
Origin
Static origin response <5 ms
Server-side static response target (Caddy file_server); actual delivery varies by network, location, DNS, connection, and TLS.
TTFB is measured from this visitor’s browser.
Platform
Split static and dynamic traffic at the gateway. Measure what matters — TTFB, RPS, and p99 latency.
Pre-rendered landing pages served directly from Caddy file_server — zero Node overhead for marketing content.
Dynamic tenant routes reverse-proxied to Astro Node adapter with isolated per-request rendering.
Namespace-per-tenant content APIs with row-level security and dedicated cache keys.
Caddy negotiates gzip and zstd at the gateway — smaller payloads, faster TTFB worldwide.
Built-in benchmark routes expose server timestamps and mock DB latency for load testing.
Multi-stage builds, compose orchestration, and autocannon scripts for reproducible benchmarks.