maple keeps a studio's client brands in one place
The app
maple is a web app where a design studio keeps what it knows about its clients' brands: colours, typefaces, logos, links, files and notes, in one place the whole studio works from. Three studios use it, among them three55 studio, each with between 7 and 15 active clients. Its code is private, so the whole app is not in a window here; a read-only demo studio is open to anyone, with the credentials on its sign-in page. The windows on this page run maple's own code for one feature each.
Saltmarsh Coffee
Brand
Colours
5Named colours in any format, with print specs, scales, contrast and token exports.
Typography
2Typefaces with their files, fallbacks and text styles.
Logos
7Logos in every colourway, as SVG or PNG.
The problem
A studio's designers and developers work on the same clients and think about them differently. A graphic designer specifies a colour in Pantone and CMYK; a front-end developer wants it in OKLCH, as tokens. A brand arrives as a pile of files whose names are the only record of which is which, and a client is sent PDFs and zips that are out of date a week later. maple holds the brand once, in the form each of them needs, and gives the client a link to the finished version.
Product decisions
One colour, optional layers. A colour is a name and a value in any CSS format, and everything else is optional: print references, a scale from 50 to 950, roles such as primary. A studio with five hexes is done in a minute, and one with a full print specification loses nothing. What a designer enters is never overwritten: maple keeps the value as typed and stores the hex and OKLCH it derives beside it, labelled derived. Pantone is text the studio types, never a lookup, since its libraries are licensed and no conversion to it is exact. The same colours read as a Palette for designers and as Tokens for developers.
Colours
Primitives
| Token | OKLCH | Entered |
|---|---|---|
| --marsh-green | oklch(38.2% 0.043 157.6) | #2f4a3a |
| --crema | oklch(89.9% 0.035 82.9) | #e9dcc4 |
| --roast | oklch(40.5% 0.077 44.2) | #6b3a24 |
| --kiln-orange | oklch(63.8% 0.162 43.7) | #d9642b |
| --ink | oklch(22.2% 0.004 84.6) | #1c1b19 |
Logos sorted on upload. A logo is one piece of artwork: a type (Standard, Wordmark, Icon, Favicon, or one the studio adds), a name within it, and the palette colours it is drawn in. Dropping in a pile of files fills in all three for each: the type and name from the file name, and the colours from the name and from what the artwork draws, each joining the logo only when the client's palette has one close to it. Nothing is saved until a designer has looked: every type is a dropdown and every colour is picked from the palette, so a wrong guess costs a click. Logos go up as SVG; PNGs and a favicon pack are drawn from it on download.
Six files, read from their names and artwork
| Artwork | File | Name | Type | Colours |
|---|---|---|---|---|
| SALTMARSH_logo_horizontal_marsh-green.svg | Horizontal | |||
| Saltmarsh Coffee Logo Reversed.svg | Default | |||
| SC-wordmark-v2.svg | Default | |||
| logo_black_FINAL.svg | Default | |||
| saltmarsh-icon.svg | Default | |||
| favicon (1).svg | Default |
Each logo sits on a backdrop it can be seen on, taken from the brand itself: Light is the brand's lightest primary and Dark its darkest, not a standard white and black it never uses. Choosing a backdrop, or trying one of the brand's colours, marks every logo with a colour under 3:1 on it, the minimum for a graphic, and names the colour that falls short.
Logos
Standard
- Default
- Reversed
- Mono
Icon
- Default
- Reversed
Fonts are read, then checked. Uploaded font files are read first, and each family is shown with the weight and style its files claim, to correct before saving, because foundries' own metadata is often wrong: maple trusts a style name before a weight class. Downloads convert between TTF, OTF, WOFF and WOFF2 losslessly only, so an OTF is never offered as TTF, which would mean redrawing its curves.
A type scale for two screens. A client's type scale is two modular scales, one for the narrowest screen and one for the widest, and every step is fluid between them. A different ratio at each end is the point: headings grow faster than body text as the screen widens, where a single ratio would only zoom everything. Sizes are kept in px, which is what designers set, and read in px, rem, em or as a clamp() for the developer, so the unit is a way of reading the scale rather than part of it.
- H3Headline67.1px41.5 to 80
--text-3xl: clamp(2.594rem, 1.793rem + 3.56vw, 4.997rem);- H5Headline35.5px26.6 to 40
--text-xl: clamp(1.66rem, 1.38rem + 1.244vw, 2.499rem);- BodyBody text sets the rhythm of every page.19px17 to 20
--text-base: clamp(1.063rem, 1rem + 0.278vw, 1.25rem);- SmallBody text sets the rhythm of every page.14px13.6 to 14.1
--text-sm: clamp(0.85rem, 0.839rem + 0.05vw, 0.884rem);
Notes that follow the brand. A note is what the team knows about a client, and it can mention a colour, a logo or a typeface from an @ menu. The note stores the thing's id, not its value, so renaming a colour updates every note that mentions it, and a deleted one reads as removed rather than breaking.
Notes
Signage colours
Signage uses Marsh Green on Crema, never the reverse. Confirmed with the client on the 12th.
#signage#printAda Lovelace12 SeptFor client
Signage uses {{colour:c1}} on {{colour:c2}}, never the reverse. Confirmed with the client on the 12th.unchanged- c1Marsh Green#2f4a3a
- c2Crema#e9dcc4
Links & Files
- Saltmarsh brand filefigma.com
- Fraunces on Google Fontsfonts.google.com
- Print specificationsPDF · 1 KBFor client
Notes
Signage colours
Marsh Green on Crema for every sign, never the reverse.
Ada Lovelace · 12 SeptFor client
Rebrand budget
Owner wants the menu boards done before the cups. Quote both.
Grace Hopper · 3 Oct
Font licences: built, then cut. A typeface first carried its licence, its seats and its expiry, and downloads of its files could be limited by role. Studios already keep that paperwork with their accounts, so the fields went unfilled, and a limit on downloads stopped nobody who could see the preview, which loads the same files. I removed all of it rather than keep a feature nobody used.
Design system
Quiet and exact. maple is a tool studios judge by eye, and every page of it is full of other people's colour, so its own look stays out of the way: warm paper surfaces, near-black ink, hairline borders instead of shadows, and one clay accent used only where attention is owed, such as the newest note. Titles are set in Instrument Serif and the interface in Geist. Its 93 tokens and 24 components are its own, with a live reference page in the app, and the typefaces and the palette are fixed by a decision record, so changing either is a decision rather than a drift.
Muted marks. A studio or a client is drawn as a mark: its initials, one of maple's icons, or an image, on a tone. The tones are a closed list of muted hues, kept quiet on purpose, because on a client's page the client's own colour is the one that should lead; the client's own palette is offered beside them. A new client starts on the tone its name gives it, so no mark is ever blank, and any of it can be changed.
Engineering
Isolated by Postgres. Every studio's clients sit in one database, and a studio's brand files are often under NDA, so one studio seeing another's data is the worst failure maple can have. A where studio_id = ? on every query holds until one query forgets it. Instead, every query runs in a transaction as a database role that cannot bypass row-level security, with the studio and the user set for that transaction only, so nothing survives into the next request on a pooled connection. The policies admit a row only when it belongs to the current studio and the user is a member of it. A query that forgets its filter returns nothing rather than another studio's rows.
// every query runs inside this, as a member or as a client link
withStudio(db, actor, studioId, (tx) => ...)
// one transaction, and three settings that end with it
select set_config('app.user_id', $user, true),
set_config('app.studio_id', $studio, true),
set_config('role', 'maple_app', true) -- cannot bypass the policiesThe link, decided in Postgres. A client's link runs in the same kind of scope with a link set in place of a user, so no membership policy admits anything. Select-only policies admit the one client the link opens and what is marked for it, and there is no write policy for a link at all. What a client can read is decided by the database, not the page.
-- a member: the current studio, and only if they belong to it
create policy colours_all on colours for all to maple_app
using (studio_id = app_studio_id() and app_is_member(studio_id));
-- a client link: the one client it opens, for reading only
create policy colours_share on colours for select to maple_app
using (client_id = app_share_client());Files straight to storage. Postgres holds each file's details; the bytes are in Cloudflare R2, which charges nothing for downloads, most of a studio's traffic. The browser uploads straight to R2 under a signed address for the studio's own folder, so no file passes through the app, and downloads are five-minute signed links. What maple makes rather than stores, brand kits, PNGs, converted fonts and favicon packs, is cached and reused. A link's preview is fetched on the server from public hosts only, and an uploaded SVG is served so it can never run script.
Tested on Postgres, without a server. The 189 tests run against PGlite, Postgres compiled to WebAssembly, with the real schema and the same policies the database gets. One reads and writes across studios by id, with and without membership, and fails if any studio table has no policy. The public demo is one read-only account, and a test fails if any server action that writes does not refuse it. CI runs these, a production build and six end-to-end tests on every push.
Where it stands
- studios using it
- 3
- active clients each
- 7 to 15
- tests
- 189
maple has been in use since September 2026 by three studios, among them three55 studio, each with between 7 and 15 active clients. Decided and not yet built: a history of every change with named releases of a whole brand, fields a studio defines for itself, and import and export of colours as design tokens and swatch files.
To try it, sign in to the demo studio: open a client, switch its colours to Tokens, try its logos on a brand colour, mention a colour in a note, or download its brand kit. Nothing you change is saved.