Kagi has officially announced that it is ending its active development of the Orion web browser for Linux, choosing instead to redirect its limited resources and engineering focus entirely toward the established macOS and iOS iterations of the software.

The decision marks a sudden halt for a project that had generated substantial curiosity and anticipation within the open-source and Linux desktop communities since it was first unveiled. A native GTK Linux port of Orion was originally announced back in 2025, and after months of steady progress, a public beta was successfully launched earlier this year. The overarching goal of the Linux development team had been to achieve complete feature parity with the popular macOS version of the browser. While recent software updates had visibly closed the gap, bringing the Linux beta progressively closer to that objective, the project will now remain at its current stage of completion under Kagi’s direct stewardship.

Rather than letting the codebase languish in a closed state, Kagi has confirmed plans to make Orion for Linux—alongside the work-in-progress Orion for Windows port—entirely open-source. By opening the code to the public, the company hopes that the wider Free and Open Source Software (FOSS) community will step up to adopt the project, maintain the repositories, and carry the development efforts forward into the future.

In an official statement addressing the difficult decision, Kagi shed light on the realities of running a lean operation in a browser market dominated by tech giants. Orion is built by a very small team comprising just a handful of developers, and the project is funded entirely by Kagi users rather than venture capital or corporate subsidies. Furthermore, the company deliberately chose not to fork Chromium when creating Orion, driven by the philosophy that the modern web ecosystem urgently needs alternative browser engines rather than relying on a single engine overseen by a solitary corporate entity.

Development has ended on Orion for Linux

Ultimately, the small team felt that they had bitten off more than they could chew, spreading their engineering resources far too thinly across multiple desktop and mobile platforms. Building and maintaining a cross-platform web browser is an exceptionally demanding engineering feat, one that is historically accomplished either by massive corporations backed by substantial venture capital or by sprawling, highly coordinated open-source communities. As Kagi candidly noted in its announcement, the company is neither of those things.

Following this strategic shift, active development will continue exclusively on the macOS and iOS versions of Orion, where the browser has built a loyal user base. Conversely, the Linux beta will receive no further updates, bug fixes, or performance improvements from Kagi’s developers. While users who currently have the beta installed can technically continue to use it, the software will remain in its unfinished state, complete with existing bugs and, crucially, no future security patches. Consequently, Kagi has explicitly stated that it does not recommend running the browser for daily web browsing going forward due to the lack of ongoing security maintenance.

The journey of Orion has been marked by mixed reactions from privacy-conscious users and tech enthusiasts alike. Because Orion was not open-source from the very beginning, some members of the Linux and FOSS communities held reservations about adopting it, even as enthusiasm grew around its potential. Many supporters remained hopeful, however, viewing Orion as a breath of fresh air. Unlike mainstream browsers tied to massive advertising conglomerates, Orion was developed by a company with no commercial incentive to track user data, inject sponsored search results, chase lucrative search distribution deals, or gamify user experience elements simply to boost its own corporate bottom line.

Whether the broader open-source community will rally around the codebase remains to be seen. Industry observers and Linux advocates are hopeful that opening up the repository will either successfully drive the browser forward under community leadership or, at the very least, allow developers to pick over its constituent parts to benefit other independent browser and web technology efforts in the future.

Kagi has indicated that it will release further details regarding the open-sourcing process, repository availability, and licensing structure over the course of the next month.

Leave a Reply

Your email address will not be published. Required fields are marked *