This page was meant as a playground of sorts to help me see how different theme options and behaviors work together. It's not so much a showcase of Brio's components, as it is a playground to explore with. It will likely change over time.
An internal tool: navigation chrome, metrics, a status table, and actions.
Scheduled maintenance. The eu-west region upgrades to the new build pipeline tonight, 02:00 UTC.
| Application | Status | Version | Updated |
|---|---|---|---|
| checkout-web | Live | v4.12.0 | 4 minutes ago |
| api-gateway | Live | v2.31.4 | 26 minutes ago |
| billing-worker | Canary | v1.9.0-rc2 | 1 hour ago |
| search-indexer | Failed | v0.8.3 | 3 hours ago |
| notifications | Live | v5.2.1 | 5 hours ago |
A product surface: hero, features, showcase, pricing, and an FAQ.
PLATFORM-FIRST COMPONENTENTS
Semantic HTML, modern CSS, and a handful of web components. No framework required, no build step required.
No credit card required
Built on the popover API, dialog elements, and cascade layers. The browser does the heavy lifting, so the runtime cost stays near zero.
Every component reads semantic tokens. Reskin the whole library from one small file, at the root or any scope.
The server renders HTML and JavaScript enhances it. Pages work before the bundle loads, and keep working when it fails.
Layout comes from a handful of composition primitives, so components stay small and focused on theme and state. Drop them into server templates and ship.
State binds to ARIA and native attributes, contrast is verified at the token level, and every control is keyboard-reachable out of the box.
$0 / month
$24 / month
Contact us
Yes. Every component is styled CSS first; the web components add behavior like focus management and dismissal on top.
Tokens are overridable at any scope. Set them on a container and only that subtree reskins.
Palette stops are mode-aware, so dark mode follows the same theme file automatically.
Copy a snippet, point a link tag at a theme, and your interface is done.