HN Debrief

Orion Browser by Kagi

  • Browsers
  • Privacy
  • Open Source
  • Developer Tools
  • Europe

Orion is Kagi’s browser, built on WebKit rather than Chromium or Gecko, and pitched as a privacy-focused browser with built-in ad blocking, vertical tabs, and unusually broad extension support. A lot of the excitement came from one specific promise: on Apple platforms, especially iPhone and iPad, it offers a way to run browser extensions that people normally associate with desktop Firefox or Chrome. That made Orion immediately interesting to users who want tools like uBlock Origin or SponsorBlock on iOS without living entirely inside Safari.

If you are evaluating Orion, treat it as an interesting niche browser rather than a full mainstream replacement yet. The practical questions are not the headline features but whether your workflow depends on Apple-only integrations, cross-device sync, stable extension behavior, or source transparency for security review.

Discussion mood

Interested but skeptical. People like the ambition, the ad blocking, and the extension story on iOS, but the mood is held back by repeated bug reports, missing Apple integrations, shaky extension compatibility, and deep discomfort with using a closed-source browser as a primary browser.

Key insights

  1. 01

    Browser security is more than WebKit

    Using upstream WebKit does not buy Orion a free pass on security. A browser vendor can weaken hardening flags, add vulnerable UI code, inject risky extension bridges, or patch the engine in ways you cannot inspect. That reframes the source debate. The issue is not ideology about open source. It is whether anyone outside the vendor can meaningfully verify the security posture of one of the most privileged apps on your machine.

    If you are evaluating a browser, ask about hardening, patch cadence, and reviewability, not just which rendering engine it embeds. For security-sensitive use, treat a closed-source browser from a small vendor as an extra trust dependency.

      Attribution:
    • asadotzler #1
    • roblabla #1
    • laserbeam #1
  2. 02

    uBlock Origin support on iOS is overstated

    The flagship pitch that Orion lets you run Firefox extensions on iOS runs into an ugly caveat. Commenters said uBlock Origin can be installed, but does not function as real uBlock Origin, and that what users are seeing is usually Orion's own blocker. That matters because many people care less about the extension badge and more about the exact capabilities, like custom filters and element picking, that distinguish full uBlock Origin from lighter Safari-compatible blockers.

    Do not evaluate extension support by installability alone. Test the specific extension features you rely on, especially on iOS where browser APIs and engine restrictions still limit what is truly possible.

      Attribution:
    • red_alpacalypse #1
    • graynk #1
    • buzer #1
  3. 03

    Three extension ecosystems means years of glue code

    Supporting Safari, Chrome, and Firefox extensions sounds like marketing, but the engineering point is real. Safari now shares much of the WebExtensions API surface, yet coverage gaps and edge cases still make cross-browser support messy. Kagi said this took seven years of work, which matches the lived experience of extension developers who know that "supports WebExtensions" rarely means full compatibility. The interesting part is not the standards story. It is the amount of compatibility glue required to make ordinary extensions mostly work.

    If your product depends on browser extension portability, budget for compatibility work even when standards appear aligned. "WebExtensions" reduces divergence, but it does not remove it.

      Attribution:
    • freediver #1
    • espetro #1
    • vanyaland #1
  4. 04

    Search index dependence is hard to escape

    The Yandex argument exposed a structural constraint in search, not just a Kagi controversy. Commenters pointed out that building a broad, fresh search index is now so difficult that smaller engines often have to rent coverage from the few incumbents that already have crawling access, historical data, and enough scale to stay inside robots.txt allowlists. That makes Kagi's use of external indexes look less like a quirky choice and more like a market bottleneck.

    If you are building on search, mapping, or other web-scale data, assume upstream dependence will shape your politics and product. Supplier risk is not a back-office concern when only a handful of firms control the underlying index.

      Attribution:
    • zargon #1
    • dewey #1 #2
  5. 05

    Calling it a wrapper misses the hard part

    Dismissing Orion as a thin skin over WebKit underrates how much work sits above the engine. Maintaining browser chrome, platform ports, security boundaries, and extension support is a substantial software project in its own right. The useful distinction is not "real browser" versus "wrapper." It is whether the team can sustain all the glue code and platform work needed to make that stack reliable over time.

    When judging a browser startup, look past the engine choice and ask whether the team can maintain the integration layer for years. That layer is where usability wins and reliability failures usually show up.

      Attribution:
    • mrweasel #1
    • gen2brain #1

Against the grain

  1. 01

    Recent builds seem better than old reputations

    Some of the harshest complaints appear to be lagging behind the current product. People actively using newer Mac and iOS builds said Apple Pay now works, 1Password can work, the compatibility toggle fixes most broken sites, and Orion has become stable enough to replace their other browsers. That does not erase the long bug list, but it suggests Orion's reputation may still be anchored to rougher earlier releases.

    If you wrote Orion off a year ago, re-test your exact workflow instead of relying on stale impressions. Browser quality changes quickly, and old complaints may no longer match current builds.

      Attribution:
    • loehnsberg #1
    • lanamo #1
    • JumpCrisscross #1
    • technovangelist #1
  2. 02

    Built-in ad blocking is becoming table stakes

    The strongest pro-Orion case had little to do with Kagi branding and everything to do with default ad blocking. Commenters argued the modern web is so degraded by intrusive and scammy ads that blockers should be first-class browser features, much like popup blockers became. In that framing, Orion is less a special case than part of a broader shift away from ad-funded browsers being credible stewards of user interests.

    If you build browser-dependent products, assume more users will browse with aggressive blocking on by default. Test against that reality now instead of treating ad blockers as an edge case.

      Attribution:
    • matheusmoreira #1
    • tjpnz #1
    • mrngld #1
  3. 03

    Apple still sets the ceiling on iOS browsers

    Some of Orion's missing capabilities are less about Kagi execution than about Apple policy. Private Relay is a Safari feature, alternative engines on iOS remain constrained outside special regions, and even in the European Union the process is described as burdensome enough to deter real competition. That makes Orion's rough edges easier to understand, even if they are still frustrating to users.

    When comparing iOS browsers, separate vendor mistakes from platform-imposed limits. If your workflow needs deep Apple integration, assume Safari will keep structural advantages for the foreseeable future.

      Attribution:
    • left-struck #1
    • Gareth321 #1
    • TingPing #1

In plain english

API
Application Programming Interface, a technical method that lets one software system send requests to another.
Chromium
The open-source browser project that powers Google Chrome and many other browsers like Brave, Edge, and Opera.
Gecko
Mozilla’s browser engine, used by Firefox to render web pages.
iOS
Apple’s operating system for the iPhone.
robots.txt
A website file that tells search engines and crawlers which parts of a site they are allowed to access.
SponsorBlock
A browser extension that skips sponsored segments and other unwanted sections in YouTube videos.
uBlock Origin
A widely used content blocker that blocks ads, trackers, and other unwanted page elements with advanced filtering controls.
WebExtensions
A common browser extension API model used across Chrome, Firefox, Safari, and compatible browsers.
WebKit
The browser engine used by Safari and some other browsers to render web pages and run web content.

Reference links

Browser and extension references

Orion product and roadmap links

Kagi and Yandex controversy

Privacy and advertising references

Alternative browsers and search tools

  • Zen Browser
    Mentioned as an open source, Europe-positioned Firefox-based browser alternative.
  • LibreWolf
    Recommended as an open source Firefox-derived alternative for people leaving Chrome.
  • Helium Browser
    Suggested as an alternative privacy-oriented browser by users unhappy with Orion.
  • Helium Browser website
    Linked to explain Helium's value proposition as a more opinionated Chromium-based browser.
  • Uruky
    Mentioned by a commenter switching away from Kagi for moral reasons tied to the Yandex issue.