Gatelamp for makers

A banner only on the sites that need one.

Gatelamp scans every one of your small sites and shows a banner only where something needs consent. When a site changes, you hear about it.

Where it gets hard

A banner everywhere, to be safe

Without a clear view of what each site loads, the easy answer is a banner on all of them. Visitors click it away on sites that never needed one, and a tool priced per site bills you for each.

The same tools, described again and again

The same analytics, bot check and affiliate links run on most of your sites. Each cookie page lists them again, and when one changes, every page needs an edit.

Embeds that sneak in

You paste a YouTube video into a post or try a new chat widget. From then on that site loads something that needs consent, and nobody noticed.

How it goes with Gatelamp

  1. Scan every site

    A real browser visits each site three times: before a choice, after “Reject all” and after “Accept all”. It writes down every cookie, bit of storage and request to another domain, with the script that caused it.

    Site scanner →
  2. Switch the lamp off where you can

    Each finding comes with a way out: self-host Google Fonts, load videos on click, count visitors without cookies. A site with nothing that needs consent shows no banner, and still gets a current cookie page.

    No-banner advice →
  3. Describe each tool once

    Your analytics, bot check and affiliate links get one description in a shared library, and every site points to it. Update a description and every cookie page that uses it updates too.

    Describe once →
  4. Hear when something sneaks in

    You get an email when a scan finds a tool that isn’t in your inventory yet, or when a site without a banner starts loading something that needs consent. Turn its banner on, or fix the cause.

    Alerts →
For example

Our own portfolio is the example. When we checked our 39 sites, 4 clearly needed a banner, because they use Google Analytics. 8 load only cookieless analytics and what the site needs to work, so their lamp stays off. The other 27 need none for what their pages load, but their affiliate links can need consent in France and Germany, so those are still open. Umami runs on 37 of them and is described once in the library.

Gatelamp for makers: common questions

Do sites without a banner still count?
Yes. They still get scans, alerts and a cookie page, so they count as a site. The plan is to make them cheap, so you watch every site instead of only the ones with a banner.
What do I add to each site?
At launch: a plain script tag for any site, an npm package, and an Astro component that renders the cookie page at build time. The script runs from your own domain, so a strict Content Security Policy can stay as it is. More platforms are planned.
Which plan fits a portfolio of small sites?
Maker is for a handful of sites, Studio for many. Both are monthly and per workspace, never per pageview. Free covers one site with a monthly scan, to try it. Prices follow before Gatelamp opens, and everyone on the waitlist gets the early price.

Gatelamp is in development, so plans, features and prices can still change. It helps you follow the published rules on cookies and consent; it isn’t legal advice.

Early access

Switch on early.

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