Reference architecture
A blueprint scoped to your constraints, not a generic template.
- Multi-tenancy model
- Network & ingress design
- Cost guardrails
The reference implementation of every primitive in design.md.
When you redesign a page, this is the gold standard to study.
Duotone canvas — purple and off-white — with a single dimmed-orange accent at #F25533.
A blueprint scoped to your constraints, not a generic template.
We run it so your engineers ship product, not platform.
The default marketing card (<FeatureCard>): warm cream rounded-[12px], a white icon plate, a hover-lift. One always-orange featured card per grid (often spanning two columns). For dense data use the square <Card> above.
The always-orange featured card — gradient fill, white icon plate, dot-grid + glow. One per grid.
Standard cream feature card with a white icon plate.
Hover lifts the card and warms the title to brand-red.
Title pins to the bottom; the icon plate sits top-left.
Orange for Stakater, muted hairline for the alternative — never green/red.
| Capability | DIY | Stakater |
|---|---|---|
| Managed control plane | ||
| 24/7 SRE on-call | ||
| Self-hosted option | ||
| Platform engineers to hire |
We map your current platform, constraints, and the gap to where you need to be.
A reference architecture and a migration path, scoped to your team and timeline.
Day-2 operations and 24/7 support so the platform stays healthy as you scale.
Shown statically with the menu open for reference. The nav and content here are sample data — decoupled from src/data/navigation.ts. The live (deprecated) header still wraps this page from the top.
The purple "stamp". Sample content — links, certs, and legal are placeholders.