How it actually works.

Network Layer Blocking

Blocked before the first byte leaves your machine.

Most browsers delegate ad blocking to extensions that run inside the page renderer — they intercept requests after the browser has already resolved DNS and opened a connection. Kairon does the opposite.

The blocker sits inside Electron's session.webRequest layer, which fires before any network I/O happens. When you navigate to a URL, Kairon's filter engine evaluates every sub-resource request — images, scripts, fonts, XHR calls, WebSocket upgrades — against a compiled rule set derived from EasyList and uBlock Origin's filter lists. Matching requests are cancelled at the onBeforeRequest hook; no TCP connection is opened, no DNS lookup fires, no bytes transfer.

• Rule compilation at startup — filter lists are compiled from EasyList and EasyPrivacy into a binary decision tree on first launch and cached.
• Resilient fallback logic — requests are intercepted using native C++ hooks for maximum performance, with a seamlessly integrated JavaScript fallback that activates only if the native engine fails to attach, ensuring blocking never silently fails.
• Cosmetic filtering — after a page loads, a separate CSS injection step hides filter-matched DOM nodes that slipped through (e.g. server-rendered ad placeholders).
• No extension overhead — because blocking runs natively in the main process rather than in a content script, it adds zero extension memory to the renderer.