Kagi Ends Orion for Linux, Plans to Open-Source Code

Kagi is ending development of its Orion browser for Linux and plans to open-source the code, a change that leaves beta users with a browser they can run but no clear path to its next official update. The company’s update covers both Linux and Windows. For anyone using Orion as a daily browser, the immediate question is who will ship a security fix when one is needed.

The platform split is substantial. Kagi is also ending its own development of the work-in-progress Windows port while shifting its focus to macOS and iOS, AlternativeTo reports. Its account says the WebKit-based Linux and Windows versions will no longer receive updates after October 2, 2026. That date describes the end of the existing update path; it does not establish when, or whether, a community-maintained build will reach users.

Orion’s Linux beta arrived only months before the decision. Recent releases had brought it closer to its goal without completing it, OMG! Ubuntu reports. Kagi intends to release the Linux codebase and the unfinished Windows port. The promise creates an opportunity for other developers, but it also shifts the practical burden of finishing, packaging and maintaining those versions away from Kagi.

What Open-Sourcing Can Put in Developers’ Hands

Publishing source code can give outside developers a way to examine Orion’s Linux implementation, repair defects and adapt it. It can also make an otherwise closed project easier to continue after its original developer steps back. For a browser, though, a usable handoff has several layers: permission to reuse the code, enough code and build instructions to produce working software, a place to coordinate changes, and people prepared to review and release them.

The announced plan does not, on the information available here, specify a license, a publication date or how community contributions will be handled. Those details affect different groups in different ways. A developer needs to know what the license permits and whether the released material can produce the browser people have been testing. A user needs to know where an update will come from, how to verify it and whether anyone is committed to responding to security problems. A repository could answer the first set of questions while leaving the second untouched.

My test for credible support is a maintained release channel: identifiable maintainers publishing installable builds, dated fixes and a way for users to receive those fixes. Source availability is evidence that maintenance is possible. It is not evidence that maintenance is happening. That standard applies especially to a browser, which routinely handles untrusted websites, downloads, extensions and sign-ins. Users should judge any future Orion Linux project by what it delivers to their devices, not by the existence of a download page or a familiar name.

The strongest case for Kagi’s plan is that releasing the code preserves an option the company could otherwise close. Developers who care about Orion on Linux or Windows may be willing to work on it even if Kagi will not. A public codebase can let them inspect bugs and decide whether the unfinished ports are viable. That outcome would require sustained work, and the current announcement cannot recruit maintainers on its own.

A Beta User’s Decision is Different from a Developer’s

Linux users who followed the beta face a near-term choice. They can keep using an existing installation, but the end of Kagi’s updates changes the assumptions behind that choice. An installed browser does not stop working on the day development ends. Websites may continue to load, saved settings may remain in place and familiar workflows may feel unchanged. None of those observations tells a user whether a newly discovered vulnerability will be fixed in the build they have.

Anyone relying on the beta can identify its installed version, check whether its update mechanism still offers a supported release, and plan a current browser for sensitive tasks if updates have ended. Those are precautions, not a claim that an Orion Linux installation has a known security flaw. The supplied accounts do not establish one.

The beta label also sets a boundary on expectations. A beta invites testing and can improve quickly, as Orion’s recent Linux releases reportedly did. It does not promise that every missing feature will arrive. With official work ending before the Linux version reached its intended destination, a prospective maintainer would inherit unfinished product work alongside the recurring maintenance of a browser. For users, those are separate risks: a feature may remain incomplete even if security patches appear, or the interface may remain pleasant while updates lapse.

Windows presents another starting point. Its Orion port was still a work in progress, while Linux had reached beta. Releasing both codebases under a community plan gives developers two possible projects, but the work needed to turn each into a dependable download will differ. Treating a future Linux beta build and a future Windows port as the same promise would obscure their different stages of development.

What Changes When the Maintainer Changes

Kagi’s continued focus on macOS and iOS also limits what readers should infer from the Orion name. Development on those platforms does not, by itself, maintain a Linux or Windows build. A browser can share an identity across operating systems while depending on separate platform work to build, test and distribute each version. A fix made for one release needs to reach the others through an actual maintenance process.

That process has editorial implications for anyone recommending software, too. A page that says a browser is ‘open source’ may be accurate while giving readers a misleading impression of its current support. A more useful description would distinguish the last Kagi-issued Linux build from any later community build and give each a date and maintainer. Labels should describe the software a reader can install today, rather than the project’s potential.

For now, Kagi’s decision has a firm near-term consequence and an unresolved longer-term possibility. Its Linux development is ending; the proposed code release could give others a route to continue it. The person opening Orion on a Linux laptop still needs an update they can identify, obtain and trust. That is where any community handoff will become visible.