At least the cap-height of the L, on all sides.
The punctuation is the brand
The name is "Let's Go Live!", apostrophe and exclamation mark included. We have seen every possible way to get it wrong. "LGL" is fine inside the team and in file names, but it never goes public.
Let's Go Live! everywhere the public sees it.
lgl-node and lgl-remi for file names, repos and internal shorthand.
Lets Go Live, missing the apostrophe.
Let's Go Live, missing the exclamation mark.
LetsGoLive, which is not the name.
Who we are, in four words
| Name | What it is | When to use |
|---|---|---|
| Let's Go Live! | The company name | Everywhere public. Copy, contracts, credits, print |
| LGL | Internal shorthand | Inside the team, file names, repo prefixes. Never in public copy |
| letsgolive.nl | The address, not the brand | URLs, footers, business cards |
One wordmark, two endings, three plates
The wordmark is Lato Black with one modification: the round punctuation dots are squares. That detail is older than this guide and we like it too much to lose it. There are two versions. The exclamation mark version is the brand-name lockup; the period version is the original wordmark. Both are always one colour: ink on paper, white on rack black or on orange. Keep it off photos unless it sits on a plate, and below 120 px switch to the square mark.
Primary · ink on #F7F8FA
Dark · white on #121212
On orange · mono white
120 px · minimum
Original · "Live." · mono only
Use the square or favicon mark instead of shrinking the wordmark. 80 px is allowed in navigation only, with padding.
Only on a #F7F8FA or #121212 plate. Never straight on the image.
Rotate, outline, shadow, gradient, or recolour beyond these three plates.
We rebuilt the wordmark as vector paths, so nothing needs the font installed. The original raster file stays hosted for reference.
Assets
Everything is hosted here, ready to link. Wordmarks come as SVG and as 2000 px transparent PNG. The square plates and the avatar are for social profiles; platforms crop avatars into circles, so the plates keep the wordmark clear of the edges.








Workbench, not garage
Most of the palette is paper, grey and ink. Then there is the orange, which we ration. It marks state or the single primary action on a page, and that is it: no decorative washes, no warm backgrounds, never more than a tenth of the screen. The status colours mean what they mean in a control room, because that is where we learned them.
The one primary button on the page. A live state. 18 px+ if it's text on paper.
Decorative washes, gradients, section backgrounds "for warmth".
Orange body text on #F7F8FA, which fails WCAG AA. Use filled buttons or 18 px and up.
Light is the default. Dark is the rack.
Light comes first on everything we ship, but plenty of us work in dark rooms, so dark mode is a toggle away (top right on this page) and the choice is remembered. The orange and the status colours stay put. Only the greys swap.
Three typefaces, three jobs
Three typefaces, each with one job. Lato Black shouts the headline, IBM Plex Sans carries the argument, and Martian Mono states the facts. We tried letting them trade jobs once. Never again.
Black
Weight 900 only, tracking −2.5%, headlines only. H1 is 46, sections are 40, card titles 26, all with line-height 1.0. The lighter weights of Lato are gone; if you find one in the wild, it is old.
16–18 px, line-height 1.55, measure 55–65ch. Use 500 for emphasis; bold belongs to the display face.
glass-to-glass 480 ms · 12 × cam
Specs, labels, captions, code. Labels are caps at 12 px with 8% tracking, like a label-maker strip. The face is already wide, so never track it further.
Shot at work, shown as-is
We only publish our own photos, and honestly they are a bit boring: flat light, no grade, cables dressed. That is the point. Screens show the real software running the real show. If a stock library could have supplied the image, it does not go up.
Own photos only. Flat light, no grade. Cables dressed.
Screens showing the actual software running the actual show.
Stock photography, in any form.
Team portraits, handshakes, "vibe" shots of the crowd.
The rewrite test
Here is the test we use: if a sentence would survive unchanged on a competitor's site, it is not ours yet. Name the protocol, name the number, and start with what actually broke. Readers can decide for themselves whether we are capable.
We delivered a seamless end-to-end livestream solution for Samsung at Gamescom 2026.
Cutting-edge multi-region broadcast for Solana's global events in Hong Kong and Abu Dhabi.
We're passionate about elevating live experiences at The Edge.
Samsung, Gamescom 2026. [n] stages, one control room. The vendor's router API dropped commands under load, so we wrote our own control layer.
Solana Hong Kong → Abu Dhabi. Same show file, different venue, [x] weeks apart. Contribution over SRT, [ms] glass-to-glass.
The Edge. [What broke. What we built instead. One number.]
Short sentences. "We built", "we run". Name the protocol and the number. Dry humour is fine. Enthusiasm about the work is fine; enthusiasm about ourselves is not.
seamless · cutting-edge · unlock · empower · elevate · end-to-end solutions · passionate about · revolutionizing · trusted by · anything that sounds generated.
The spec line is the evidence
Every case gets the same card. Photo with a status chip, Lato title, the mono spec line, a few lines of body, one link. The spec line is the part we actually care about. It carries the proof; the paragraph is commentary.
180 px with our own photo, and a status chip bottom right: an 8 px square plus a caps label.
Mandatory. Martian Mono caps, 4% tracking, meta colour. City, date, the numbers, the custom build.
"Read the build →" in orange mono, the only accent on the card.
The details are the brand
Everything is built like the racks it describes: square corners, hairline rules, printed labels. We ask one question of every detail. Would it survive in a control room? If not, it does not ship.
One primary per page: orange fill, mono caps, 10×16 padding. Secondary is a hairline, ghost is just ink.
Inputs: panel fill, hairline border, radius 0. Focus turns the border orange, without a glow.
Status chips are filled squares, not dots. They don't pulse.
Two devices, two places. One background.
The burn-in lives on project overviews; the signal path lives on project pages. They never share a viewport. The patched-schematic background sits behind heroes and print, never behind body text. Everything else stays plain: paper, ink, hairlines, one orange.
A · Burn-in
Project overviews, home work grid, socialsEvery photo in a list or grid carries two corners: source label top-left, timecode bottom-right, the way a multiviewer labels a source. Orange plate and a 2 px orange frame only when that project is live right now. Nothing else on the image.
Four stages, one control room. We wrote the router-control layer.
Contribution over SRT, 480 ms glass-to-glass.
[What broke. What we built instead.]
B · Signal path
Project pages onlyOne continuous 1 px ink line runs down the left of the page. Each section is an orange node on it; a section not yet written is a hollow node. Directly under the title, every case is told as three stations: IN · WE BUILT · OUT. No rack texture, no rails. The line is the whole device.
Four stages, one control room. The vendor's router API dropped commands under load, so we wrote our own control layer.
C · Background, patched schematic
Hero, cards, decks, socials, printA faint dot grid is the canvas. Routed hairlines snap to it: right-angle bends only, every bend on a dot. Hollow nodes are open ports; where a cable is plugged, the port and its line turn orange. Always on one side of a surface, always fading under content. Same DNA as the signal path, one scale up.

Card 85 × 55 mm, shown at 4:1. The front's orange cable exits the bottom edge; the back's enters the top edge at the same column, so the route continues around the card.
Secondary reference: label tape
On file, not in use on the site. Staggered strips of real cable-label text in faint ink, one strip orange. Candidate for merch, crew shirts, case stickers. Martian Mono 500 at 9–11 px, 6% tracking, #C9CDD4 on paper, 1 px hairline top and bottom per strip.
Where each one goes
No other decorative devices. Bracketed values are placeholders on purpose; leave them visible until the data exists.
The numbers, for whoever builds it
The values a build actually needs, in one place. The full token set lives in this page's own source; view source and copy the :root block.