Writing about Maple, building an integration, or putting us on a slide? Take what you need — no permission required, and no need to ask first. The one thing we do ask is that you use the artwork as it is rather than redrawing it.
The lockup is the default — reach for the bare mark only where the name is already present, and for the tile only where the mark has to hold its own edge against chrome we don't control. Each tile below shows the exact file you get.
The brand is a warm amber at hue 59 on a near-black that leans brown rather than blue. Everything else in the product is a neutral or a severity colour — the accent is deliberately the only saturated thing on screen.
--primary oklch(0.714 0.154 59) brand accent, dark theme --primary oklch(0.66 0.16 59) brand accent, light theme --background oklch(0.207 0.008 67) app ground, dark theme --amber-deep oklch(0.55 0.16 55) landing accent, pressed --amber-soft oklch(0.78 0.12 65) landing accent, raised Headings are Geist. Body copy is Geist Mono — that is not a mistake or a code-block rule, it is the default text face across the product. An observability tool is read the way a terminal is read, and the monospace keeps ids, durations, and hex digests in columns that line up.
The wordmark is Geist Medium at −0.02em. Both faces are open source, under the SIL Open Font License.
Traces, logs, and metrics
p95 842ms · error_rate 0.4% · 1a2b3c4d5e6f7890
Maple
These aren't style preferences — each one is a property the artwork actually has, and breaking it produces a logo that renders wrong rather than one we merely dislike.
The eyes and the notch beside the trunk are knockouts in a single evenodd path — whatever sits behind reads through them. A gradient arrives at the eyes at a different value than at the silhouette edge, and they stop reading as eyes.
The rounded tile exists so the mark survives a browser tab strip. Inside a header or a slide that already has a surface, it is a box around a box — use the bare mark.
Setting “Maple” next to the mark in whatever face is to hand gives you a different logo every time. The lockup above is outlined, so it needs no font installed.
Scale it uniformly and take a colourway from this page. If none of them clears your ground, use mono white or mono ink rather than mixing a new one.
Keep clear space of at least half the mark's width on every side. The bare mark stops resolving below 16px — its eyes are barely a pixel wide and antialias into a blob — so below that, use the tile.
Everything here is the exact byte the product ships. If you need something that isn't in the kit — a different ratio, a partner lockup — ask rather than improvise.
Need something the kit doesn't cover — a partner lockup, a different ratio, or permission to do one of the four things above? Email hello@maple.dev.
Maple's source is FSL-1.1-ALv2, and each release converts to Apache 2.0 two years after we publish it. Neither one hands over the name or the artwork. The FSL says so in its own words, and Apache repeats it in its section 6. So a fork gets every line of the code and none of this page: ship it under your own name and your own mark. Saying what it is stays fine. “A fork of Maple”, “built on Maple”, “compatible with Maple” are all true, and none of them needs asking.
What isn't fine is looking like us when you aren't: Maple in your product name, domain, or handle, or the mark placed so it reads as endorsement or partnership where there's no agreement. We can ask you to stop, and if we do, please stop.
Maple and the Maple mark are trademarks of Makisuo, Inc. Other names and logos on this site belong to their owners.