Custom Chromium and Brave builds

Egon Browser

A Brave-based browser we built for a private client, with its own branding and privacy defaults set to the client’s requirements.

  • Brave
  • Chromium
  • Privacy
  • Branding
Built on
Brave (Chromium)
Our part
We built Egon on Brave’s open-source code, changed its privacy defaults and replaced the branding.

The client and the problem

The client wanted a browser under its own name, Egon, with privacy and data-handling behavior set to its own requirements instead of the defaults a general-purpose browser ships with.

What we built

We built Egon on Brave’s open-source code, which runs on Chromium. We changed its privacy and data-handling defaults to match the client’s requirements and replaced the Brave branding with Egon’s own. The branding work sits apart from the engine changes, so either can be updated without touching the other.

  • A custom browser built on Brave and Chromium
  • Privacy and data-handling defaults changed to the client’s requirements
  • Egon branding, kept separate from the engine changes

Why it was hard

A Brave-based browser has two upstreams: Brave’s code and the Chromium code under it. Each privacy default is set in one layer or the other, so every change meant finding where that default lives and making sure it survives the next update of both.

How it fits together

Egon: two upstreams and the client’s changes

  1. Egon Browser

    • Branding

    The client’s product: the Egon name, logo and interface identity.

  2. Branding

    • Branding

    Egon’s name, icons and product strings, kept apart from the engine changes.

  3. Privacy defaults

    • Privacy

    Privacy and data-handling defaults changed to the client’s requirements, in the Brave or Chromium layer where each is set.

  4. Brave

    • Brave

    Brave’s open-source browser code, the base Egon is built from.

  5. Chromium

    The engine under Brave.

  • Client's product
  • Our engineering
  • Upstream: third-party code we build on
Egon’s branding and privacy defaults sit on Brave’s code, which in turn sits on Chromium.

Related services

Facing a similar engineering problem?

Tell us what you are building. A browser engineer will walk you through how we would approach it, what is hard about it and what it takes to keep it current after launch.

Send a project brief

More case studies: Custom Chromium and Brave builds