Overview & Guarantees
static.bio is a link-in-bio service built for developers who care about performance and privacy. We deliver public profile pages as pure HTML + CSS with zero JavaScript, designed for sub-100ms time-to-first-byte from the edge (typical TTFB in NA/EU is ~20-50ms, with higher values in more distant regions), and a privacy-first architecture that tracks nothing by default.
This isn't a marketing page—it's a technical contract. If you're evaluating whether to trust this system, read on.
The Contract
Core guarantees:
- Zero JavaScript on public pages. Pure HTML + CSS, server-rendered, nothing else.
- Designed for sub-100ms TTFB from the edge. Typical TTFB in NA/EU is ~20-50ms; test suite measures ~98-120ms including network latency. Higher values in more distant regions.
- HTML + CSS budget <15KB gzipped. Actual size: ~1.88KB + ~8.2KB for the avatar (base64-encoded).
- No cookies, no third-party scripts. Public pages set zero cookies and load zero external resources.
- No subscriptions. Free forever. Or pay once for a few bonus features, and own it forever.
High-Level Architecture
The system is architected as two almost-separate applications:
Public Profiles
Public profile pages follow a simple request flow:
Browser → Edge Runtime → renderProfilePage(input) → HTML stringThe renderer is a pure function: it takes profile data and returns HTML. No database access, no network calls, no environment reads. This design makes the output deterministic and cacheable.
- Route:
/api/profile/[username](viaproxy.tsrewrite) - Runtime: Edge Runtime (production) for sub-10ms cold starts
- Output: Pure HTML with inline CSS, zero script tags
- Framework: None—the renderer is framework-agnostic
Dashboard
The dashboard is a separate Next.js app for authenticated creators:
- Route:
/dashboard/** - Runtime: Node.js (standard Next.js server components)
- Tech: React, Tailwind, Auth.js
- Purpose: Profile management, billing, analytics (Lifetime plan only)
The dashboard and public profiles share a database but have completely separate runtime behavior. Dashboard code never touches public pages.
Why This Exists
Link-in-bio services are mispriced. Most charge monthly subscriptions for what is essentially a static HTML page. The infrastructure cost is negligible, but the business model demands recurring revenue.
static.bio exists because:
- Subscription fatigue. Developers want to pay once and own their profile forever.
- Performance matters. A link-in-bio page should load instantly, not after a React bundle downloads.
- Privacy by default. No tracking cookies or third-party analytics. We only store aggregate click counts when you opt in, plus standard infrastructure logs.
- Hand-rolled quality without hand-rolling. You get the performance and simplicity of a custom page without building it yourself.