Build it for Aback. Engineer it for reuse. Release it for everyone.

Aback UI is the interface foundation behind the products of Aback Group, published as an open-source React component library. It has 57 components and 16 blocks today, one set of design tokens, a CLI that copies source into your project, and an npm package for teams that would rather import.

Why it exists

Aback Group runs several products, and each one had rebuilt the same pieces: buttons, dialogs, data tables, settings rows, empty states. They drifted apart in small ways, and every fix had to be made more than once. Aback UI pulls those patterns into one place, makes them accessible and documented, and lets each product take them as source it can still change.

Releasing it publicly keeps the bar high. A component that has to make sense to a developer outside Aback cannot quietly depend on one product's data, routes, or business rules.

Where the components come from

Components are reimplemented from patterns that ship in Aback products, not copied from them, and product-specific logic stays in the products. Each component page says which products use it, and Built with Aback UI shows them side by side.

How it is maintained

The code lives in a public repository on GitHub (opens in a new tab) under the MIT licence. Releases are versioned, published to npm with provenance from CI, and recorded in the changelog. Until 1.0, APIs may still change; component pages mark what is stable and what is beta. Contributions follow the contributing guide.

What it is not

Aback UI is not a hosted service, a page builder, or a framework. It does not need an account, phone home, or fetch component code from the internet at install time. It targets React 19 and Tailwind CSS v4 and does not claim support for setups it has not been tested in.