Built

SAUCE

SAUCE is the component library our interfaces are built from — written by us, documented, tested, and themed through tokens.

A sheet of SAUCE components — inputs, buttons, a table and a dropdown — on a dark theme.

Every input, table, modal and control in it is ours, documented in Storybook and covered by tests. A token system sits underneath, so one set of components can carry a different brand per client, or per tenant at runtime, without being forked.

We built it instead of reaching for Tailwind, Material UI or a bought template because those optimise for getting something on screen fast, and the cost is that everything built with them looks and behaves alike. A tool for a clinic should not feel like a marketing dashboard. Owning the kit also means a breaking change, a vulnerability or an abandoned package is our problem on our schedule, not someone else’s on theirs.

This is software work. See how software works

Stream
Software
Kind
Our own tooling
Theming
Tokens, per tenant at runtime
Documented
Storybook
Client
V Source

Start a conversation