live · rendered on every request checking connection…

This page is proof, not a pitch.

Everything below is real: rendered by the same Rust engine you're looking demos of, with numbers pulled from an actual Postgres database, not staged screenshots. The sales pitch lives at coderb.dev/redline — this site is the evidence it points to. View-source, open the network tab, run your own Lighthouse pass. Nothing here is asking you to take our word for it.

>_

You are looking at Redline right now. This exact page — the layout, the templating, the auto-generated SEO files, the live stats panel below — is built and served by the engine itself. No separate marketing site, no mockup.

Live Stats

Nothing here is a screenshot

Three different kinds of "live": per-load performance measured in your own browser, traffic persisted in a real Postgres table, and in-process engine state read fresh on every request.

current visitors (last 5 min, not deduped)

Page views today

Pages served (all-time)

Engine uptime

Last render time

Views, last 30 days

Gauge + tiles + sparkline refresh every 15s via GET /api/stats/live — a small fetch, not a websocket.

Vanilla HTML/CSS/JS 0 KB framework

No React. No build step. Still interactive.

The gauge above, the filter below, and this step-through are all plain DOM APIs — no virtual DOM, no hydration, no bundler. View-source and it's exactly what ships.

Under the hood

vanilla JS

Request hits the router

An Axum router matches the path. Static assets (CSS/JS/images) are served straight off disk with long-lived cache headers, bypassing templating entirely — they never touch step 2.

Performance snapshot

Navigation Timing API
MetricThis pageMedian web page
Load time 62% of mobile pages miss "good" LCP (<2.5s)
Total page weight 2.1 MB
Requests 72
Lighthouse (Perf / A11y / Best Practices / SEO) 100 / 100 / 96 / 100

"This page" column measured live in your own browser via performance.getEntriesByType() — nothing hardcoded. "Median web page" cites the 2025 Web Almanac's Page Weight chapter (mobile, 50th percentile) and its Performance chapter — a general web median, not a specific WordPress/Wix measurement we could stand behind.

Lighthouse scores measured 2026-09-02 against a local build of this exact page (headless Chrome, mobile emulation) — 10 requests, ~22 KB total transfer (favicon and logo included), 1.1s Time to Interactive. Not a production/CDN run, so treat as directional rather than a guarantee for every network condition. Run your own — it's one click in Chrome DevTools.

What Redline generates automatically

SEO/GEO plumbing, not bolted on

These are outputs, not claims — every link below is a file this same process wrote to disk at startup, or a header/response you can inspect right now.

sitemap.xml

Rebuilt at every startup from every page's front matter — add a page, it's in here on the next boot.

seo

robots.txt

Explicitly allows GPTBot, ClaudeBot, PerplexityBot, and Google-Extended alongside general crawlers — a deliberate policy, not a default left untouched.

geo

llms.txt

A curated, markdown page index for AI/LLM crawlers, per the llmstxt.org convention.

geo

OpenGraph + Twitter Card tags

Per-page, from the same front matter that drives the sitemap. See the live inspector below — it's reading this exact document's <head>.

seo

JSON-LD structured data

A schema.org object per page, built from the same metadata. Also visible in the inspector below.

geo

/health

Liveness + database connectivity in one JSON response — what a load balancer or uptime check would hit.

ops

/api/stats/live

The exact endpoint driving the live stats panel above — open it directly, no auth, nothing hidden.

ops

Security headers

fetched live, not copy-pasted

CSP, HSTS, X-Frame-Options, X-Content-Type-Options, and a locked-down Permissions-Policy on every response — read straight off a live response below, not typed in by hand. (Fetched from /health rather than this page itself, so checking them doesn't also count as an extra page view.)

checking a live response…

Live meta inspector

reads this page's own <head>

Not a mockup of what the tags would look like — this reads the OpenGraph, Twitter Card, and JSON-LD tags out of the current document right now.

reading document.head…

Next step

See what this engine is for

This page exists to prove the plumbing works. The pitch — what Redline is, who it's for, how to get one — lives at coderb.dev/redline.

coderb.dev/redline →