Copy the source, not a dependency

Whole screens, built from Volt UI.

Page sections, application layouts and tested workflows. Each one comes with a live preview, its complete source and the components it is made of.

Browse Blocks Docs

blocks/hero-spotlight.ts
Pricing that stops being interesting once you ship.
Every tier includes the full component source. The paid ones only add people and support.
Monthly Annual Save 20%
Starter
For the side project that might become something.
$0 / month
Every component and block
MIT licensed source
Community support
One seat
Most popular
Pro
For the product a small team ships every week.
$19 / month
billed $228 yearly
Everything in Starter
Figma design kit
Private theme presets
Five seats
Priority issues
Team
For the design system several teams depend on.
$63 / month
billed $756 yearly
Everything in Pro
Unlimited seats
SSO and audit log
Shared Slack channel
blocks/pricing-tiers.ts
Why teams pick it
Everything you need, nothing you have to unlearn.
Plain Angular components in your own repository. No runtime to upgrade, no theme API to fight.
Motion that ships with the markup
Every interaction here is CSS and a pointer handler — no animation runtime, no bundle cost, and it degrades to a static section when the visitor asks for reduced motion.
@keyframes
mask-composite
pointermove
prefers-reduced-motion
Accessible underneath
Roles, focus order and keyboard paths come from the primitives, not from markup you have to remember to write.
Themed by tokens
Five colour presets, five shape presets, light and dark. Blocks inherit them because they never hard-code a colour.
Copy, do not install
The source lands in your repository. Rename it, gut it, keep it — nothing upstream can break it later.
Composed from real components
Buttons, cards, switches and avatars you already use, arranged. Nothing here is a one-off.
blocks/feature-bento.ts

Blocks: 11
Layouts: 10
Recipes: 3
Volt components in use: 21

Blocks

Sections that already move.

Whole page sections built from Volt components, with the motion already wired. Every block is one file: copy it, rename it, and delete the parts you do not want.

One file each
Template, styles and behaviour in a single standalone component.
No animation runtime
CSS and a pointer handler. Nothing to add to your bundle.
Theme-aware
Built on tokens, so every preset and dark mode come along.

Hero Spotlight

3 atoms

Centred opening with a spotlight that follows the pointer.

Ships on every push

From commit to production without the ceremony.

Push a branch and get a URL. No pipeline to maintain, no console to learn, no meeting about who owns the deploy.

Deploys: 2.4M
p95 build: 38s
Uptime: 99.99%

acme/storefront

main

Deploying

Installing dependencies 142 packages
Building library ng-packagr
Running tests 394 passed
Deployed to production edge, 14 regions

Hero Split

4 atoms

Copy on the left, a live product panel on the right, tilted toward the reader.

Why teams pick it

Everything you need, nothing you have to unlearn.

Plain Angular components in your own repository. No runtime to upgrade, no theme API to fight.

Motion that ships with the markup

Every interaction here is CSS and a pointer handler — no animation runtime, no bundle cost, and it degrades to a static section when the visitor asks for reduced motion.

@keyframes
mask-composite
pointermove
prefers-reduced-motion

Accessible underneath

Roles, focus order and keyboard paths come from the primitives, not from markup you have to remember to write.

Themed by tokens

Five colour presets, five shape presets, light and dark. Blocks inherit them because they never hard-code a colour.

Copy, do not install

The source lands in your repository. Rename it, gut it, keep it — nothing upstream can break it later.

Composed from real components

Buttons, cards, switches and avatars you already use, arranged. Nothing here is a one-off.

Feature Bento

2 atoms

Asymmetric grid where each card lights its own border under the cursor.

What we do

Four things, done properly, instead of everything.

01
Design systems
A component library your team actually uses, because they helped decide it.
We audit what you already ship, throw away the half of it that duplicates the other half, and rebuild the rest as tokens and components in your own repository. You end up owning the source, not renting it.
Token architecture
Component library
Figma kit
Adoption plan
02
Frontend architecture
The decisions that are expensive to change, made once and written down.
Routing, state, data fetching, rendering strategy and the boundaries between them. We leave you with a running application and a document explaining why every choice in it was made, so the next engineer does not relitigate all of them.
Architecture review
Reference app
Decision records
Team workshop
03
Performance
Numbers that move, measured on the devices your customers actually hold.
We profile on real hardware and real networks rather than a developer laptop on fibre, fix what the traces point at, and put a budget in CI so the wins stay won after we leave.
Trace analysis
Bundle surgery
CI budgets
Before and after
04
Accessibility
Conformance you can evidence, not a plugin score in a screenshot.
A manual audit against WCAG 2.2 AA with assistive technology, prioritised by how many people each issue blocks, plus the fixes implemented and the regression tests that keep them fixed.
Manual audit
Remediation
Automated checks
Statement

Service List

3 atoms

Numbered rows that open as you point at them, instead of four equal cards.

Browse Blocks

Layouts and recipes

Frames and workflows to fill in.

Layouts give an application its frame. Recipes show behaviour over time: a form that validates, a search that waits for the network, a table that paginates.