Cookie banners only where they’re needed.

Gatelamp scans all your sites, tells you which ones need a banner, and gives those an honest one in their own style. One dashboard for every site.

One email to confirm, one when your invite is ready. Unsubscribe in one click.

waitlist by waitlark

See it

All your sites, at a glance.

Designs for the dashboard, the banner and the scanner, filled in with our own sites as example data.

Dashboard design with our own sites as example data: 39 sites, 34 that need no banner, 5 with a banner on, and one that needs a look. About the dashboard
The same banner on four of our own sites, each in the site’s own colours, type and corners. Accept and reject are always the same size, and the first layer says how many companies get data. About your site’s style
Scan design for fijnhier.nl, one of our own sites: nothing is stored before a choice or after a refusal, and two Google Analytics cookies after “Accept all”. Glim suggests how the site could drop its banner. About the scanner
Why the lamp

Most sites don’t need a banner. Ours didn’t.

A lamp at the gate only goes on when someone’s coming. When we checked our own 39 sites, this is what we found.

34 need no banner

Only cookieless analytics and things the site needs to work.

5 ask first

They use Google Analytics or embed videos, so they need consent.

How a site goes without one
Ask

Where a banner is needed, an honest one.

The rules are built into the editor. Reject is as easy as accept, nothing is ticked in advance, and you can’t publish a banner that breaks that.

Banner editor design for fijnhier.nl: the live preview next to the settings, and the rule check. “Reject all” was turned into a text link, so one rule fails and publishing is blocked until it’s fixed. About the honest banner
Settings design: the second layer in Dutch, one of six starter languages. Every switch starts off, the focus ring shows where the keyboard is, and reject and accept stay the same size. About languages
Watch and manage

Describe it once. Hear when it changes.

One library for every tool on every site, and an email the day a scan finds something new or too early.

Library design with our own tools: each one described once and used on every site that runs it. Google Analytics 4 is open, with its provider, cookies, how long they stay and where data goes. About the library
Alert email design: the weekly scan of themes.dev found Google Fonts and a YouTube embed loading before anyone chose. The email names the page and the cause, and links straight to the fix. About alerts
Prove

A cookie page that’s current. Proof of every choice.

The cookie page is built from what the scanner finds, and every yes or no is kept with the banner version someone saw.

Cookie page design for fijnhier.nl, in the site’s own style. Every row comes from the inventory: name, provider, purpose, how long it stays and what kind of storage it is. About the cookie page
Proof design: one consent ID looked up. The visitor rejected everything on 18 October against banner version 12. No IP address or browser details are stored. About proof of consent
Features

Ask, watch, manage, prove.

Everything a portfolio of sites needs to handle consent honestly. Every feature has its own page.

Ask

An honest banner in your site’s own style, only on the sites that need one.

Watch

A scanner that visits your sites like a real person and tells you what changed.

Manage

Every site in one dashboard. Describe a tool once and use it everywhere.

Prove

Records of every choice, a declaration that stays current, and privacy on by default.

See all features
How it works

From first scan to lamp off in four steps.

  1. Add your sites

    One line in your layout, or a component in Astro. Every site shows up in the dashboard.

  2. Scan them

    A real browser visits each site three times and writes down what gets stored or sent.

  3. Fix it or ask

    Follow the advice so a site needs no banner. Where one is needed, switch on an honest one.

  4. Keep watching

    Weekly scans and an alert the day something changes. The cookie page updates itself.

Install design for an Astro site: one component in the layout, the script served from your own domain, and a cookie page rendered at build time. Names can still change. About running on your domain
How it works, in detail
Why Gatelamp

Built for people with more than one site.

We made Gatelamp for our own sites first. These are the things we couldn’t find elsewhere.

A banner only where it’s needed.

Most cookie tools charge per site or per pageview. Gatelamp tells you which sites can do without a banner, and keeps an eye on them.

The rules are built in.

Reject as easy as accept, nothing pre-ticked, the number of third parties on the first layer. You can’t publish a banner that breaks them.

Runs from your own domain.

A small web component served by your site. Your security headers stay strict, and there’s no extra third party.

Priced per workspace.

Not per pageview or session. Sites that need no banner don’t make your bill bigger.

Early access

Switch on early.

Join the waitlist for Gatelamp. We invite people in small groups, and waitlist members get the early price.

One email to confirm, one when your invite is ready. Unsubscribe in one click.

waitlist by waitlark