Desifex

Design systems

One brand. Everything you build wears it.

Set your brand up once and every application in the workspace is built in it — not a palette applied afterwards, but the instructions the builder designs from.

Acme brandAapalette · type · a binding briefyours, or a client'sProposals its own data, its own address, its own users Supplier portal its own data, its own address, its own users Field survey its own data, its own address, its own users change the brand and all three restyle — in seconds, with no rebuild

For your own team

One design system for the workspace, and the fifth application looks like it came from the same company as the first. Nobody re-specifies the colours, nobody rebuilds the components, and nothing drifts because a different person asked for the next one.

Change the brand later and every application restyles in seconds, with no build spent and nothing to review. That is the part that is hard to do any other way: a rebrand that would be a quarter of work across five applications is an afternoon here.

For your clients

A design system per client, in a workspace per client. Everything you build for them is in their brand — the pilot, the portal, the internal tool — so what you hand over looks like their software rather than like a tool you used.

A workspace's own design systems are visible and editable only to that workspace. A client's brand belongs to the people working with that client, not in a gallery everyone browses. Two workspaces can each have one called "Primary" and neither will ever see the other.

One account belongs to as many workspaces as you need, so moving from one client to the next is changing workspace rather than signing in as somebody else — and the separation stays in the workspace rather than depending on which account you remembered to use.

The brief is the half that makes it real

A brand is the easy half: colours and type get rendered into the stylesheet, and changing them restyles an application in seconds.

The brief is what stops this being a repaint. Left to decide for itself, any builder draws the same page every time — sidebar, page header, four stat tiles, a table — and thirteen design systems come out as one layout in thirteen palettes. So each brief states where navigation lives and what the content actually is, and the builder treats that as binding rather than advisory.

Ledger has no navigation chrome at all and reads as a printed statement. Bloom is a centred column of prose. Signal is one full-bleed list with an overlay. Aurora is a bento grid. None of them will draw a sidebar and a table.

Your brief is written the same way — dense, tables rather than cards, navigation on the left and always visible, numbers right-aligned, no decorative imagery — and from then on it is what your applications are designed to.

Three ways to get a brand in

Each of them proposes a palette and a brief for somebody to read, edit and accept. Nothing is saved automatically — a brand imported wrongly and applied silently is worse than one entered by hand.

Your brand guidelines

Logos, screenshots, a brand book as a PDF, your web fonts. The fonts travel into every application built in that system, so your typefaces are genuinely used rather than approximated.

Your website

Give us an address. The page is opened in a real browser and its colours, typefaces, corners and spacing are measured from what is actually rendered — not from what a brand document says they should be.

Your Figma library

Published colour and text styles, read through Figma’s API with a personal access token used for that one request and never stored.

Or start from one of the thirteen below and change what you need, which is usually faster than starting from an empty brief.

Thirteen ship with the platform

Real screens, drawn by the builder in each system and stored with it — not mock-ups made for this page. They are also the evidence that this holds genuinely different looks, which is what makes a brand of your own worth setting up rather than a filter over ours.

Enterprise

Business software, in six tempers.

Dense
A dense operational console; crisp blue, tiny corners
Classic
A formal system of record; warm, serif headings, deep red
Soft
A rounded modern workspace; friendly indigo, roomy
Slate
A monitoring board of figures and charts; colour is the data
Contrast
Legibility ahead of elegance; top tabs, large type, loud focus
Ledger
A printed statement — no chrome, ruled lines, a running balance

SaaS

The product-company end of the shelf.

Aurora
Deep violet, soft light; a bento grid around a generated answer
Signal
Pure neutrals, one electric accent; one full-bleed list, ⌘K first
Bloom
Warm cream and sage, a soft serif; a centred column of prose

And four of their own

Where the shelf stops being a catalogue.

Smooth
Editorial and unhurried — the one this site is built in
Techie
An instrument panel: monospaced, keyboard-first
Modern Retro
Cream paper, heavy outlines, hard offset shadows
Jukebox
Mid-century American in a modern frame; capsules and a chrome lip

Changing one later

Colours, type and shapes reach existing applications immediately, with no build spent — which is what makes a rebrand across a portfolio an afternoon rather than a project.

A changed brief cannot restructure screens that already exist, so the workbench says the design system has moved on and offers to restyle each application, which does run a build. Never automatically: one edit should not silently spend a build on every application you have.

Send us your brand

Point us at your guidelines or your website — or a client's — and we will show you one of your own applications drawn in it, rather than a swatch row.

Tell us in the message instead.

We use this to reply to you and for nothing else. No newsletter, no third party. What we keep