On October 2, Kagi announced it is ending development of Orion Browser for Linux and Windows. The source code for both will be released within 30 days so the community can carry them forward, while Kagi's small team refocuses on macOS and iOS. The Linux beta keeps working but stops receiving updates — Kagi itself says not to use it as your main browser anymore. The Windows release planned for late 2026 is cancelled outright.

If You're on the Beta: Move This Week

An unmaintained browser is not a quirky choice — it's a liability. The browser is the most attacked software on your machine, and without security updates the beta becomes a sitting duck within weeks. Treat October as your migration deadline.

The practical steps are boring and that is the point: export your bookmarks now while the beta still runs cleanly, move saved logins into a proper password manager if you haven't, and pick a daily driver. On Linux the sane options are Firefox (or a Firefox-based fork), Brave, or plain Chromium — depending on how you weigh extension compatibility against de-Googling. Keep the Orion beta installed if you're curious about whatever the community builds next, but demote it from "the browser I log into my bank with" to "the browser I watch."

One Fewer Engine on the Desktop

Here's the part that matters long-term. Orion was built the hard way: WebKit-based, not another Chromium skin. On the Linux desktop, non-Chromium browsers are already an endangered list — Firefox and its forks on Gecko, and not much else you can daily-drive. Every retreat like this is another data point for the Chromium monoculture: fewer engines means fewer independent implementations of web standards, and Google's interpretation of the web quietly becomes the web.

Kagi was upfront about why: a tiny team, funded entirely by its users, trying to ship an independent browser across three platforms. That is a bet almost nobody wins. The takeaway isn't that Kagi failed — it's that independent browser engines are brutally expensive to maintain, and the market keeps proving it.

"The Community Will Maintain It" — Will It?

Open-sourcing the code is the right move, and Kagi deserves credit for doing it instead of letting the code rot internally. They've even contacted open-source foundations about long-term stewardship. But let's be honest about what a community WebKit browser fork actually needs:

  • Dedicated maintainers, not drive-by contributors. A browser needs people triaging security CVEs every week, not just hackers fixing a pet bug.
  • Security backporting. WebKit gets constant upstream security fixes; someone has to port, test, and ship them on a schedule attackers respect.
  • Build and release infrastructure. Nightlies, stable releases, distro packaging, auto-updates. Unsexy, essential, and a lot of work.
  • A governance home. Kagi said plainly it won't be the core maintainer. A foundation — or a company with a business reason to care — is what turns a code dump into a living project.

None of that is impossible, but "source available" is step zero of about fifty. When the code drops, the most valuable early contributions aren't code at all: testing, bug reports, distro packaging, and documentation.

What Happens Next

The code should land within 30 days of the announcement, so early November. Watch Kagi's blog and the new repository for the license terms — those determine everything a fork is allowed to do. Until a credible maintainer steps up, treat any "Orion continued" build as experimental.

Orion for Linux was a genuinely interesting bet: a privacy-respecting, WebKit-based browser from a company that charges users instead of advertisers. Its exit is a loss for browser diversity, full stop. Migrate your daily browsing now — and if the community fork gets legs, you'll know where to find it.

Sources: Kagi, "An Update on Orion for Linux and Windows" (blog.kagi.com, October 2, 2026).