An Orion browser review for people who keep thirty tabs open

Most people arrive at Orion from the same direction. Chrome has been eating the battery, Safari cannot hold the extensions the job depends on, and the tab strip has turned into a row of identical favicons that has to be hovered over to identify. Orion gets recommended in that situation often enough that it is worth looking at properly, rather than downloading it, keeping it for four days, and drifting back.

The useful question is not whether Orion is a good browser. It is whether Orion solves the specific failure that thirty open tabs represents. Those are different questions, and the answer to the second one is narrower than most recommendations suggest.

What Orion is, stated plainly

Orion is a WebKit browser built by Kagi, the search company. WebKit is the engine Safari uses, which means Orion inherits Safari's rendering behaviour and its power profile rather than Chrome's. It is free to download for macOS, iOS and iPadOS. The Linux build is described as being in beta, and the Windows build is listed as an alpha in active development, with a newsletter signup rather than a download link.

The funding model is stated on the product page and it explains most of the design decisions that follow.

Orion is 100% funded by its users; no ads and no third party deals. Source: kagi.com

That funding comes from Orion+, an optional membership. The pricing page lists three options, described as monthly, yearly and lifetime, at $5, $50 and $150 plus sales tax. Orion itself does not become limited without it. The listed Orion+ benefits are custom app icons, a customisable border around the browser window, a community tag, and early access to beta builds, which places the membership closer to patronage than to a feature gate.

The browser ships with ad blocking and tracker blocking turned on by default, and the site describes the telemetry position as zero. For anyone who currently runs a content blocker as a separate extension, that is one fewer moving part to reinstall.

The extension question decides this for most people

Orion's headline claim is that it is the only browser supporting Safari, Chrome and Firefox extensions at once. That is genuinely unusual, and it is the reason the browser is worth a serious look rather than a glance.

The important detail sits just underneath the claim. The extensions page describes a curated gallery of tested extensions, currently a short list that includes 1Password, uBlock Origin, Dark Reader, Tampermonkey, Consent-O-Matic, iCloud Passwords, Microsoft Single Sign-on and Mullvad VPN. Beyond that list, the Chrome Web Store and Firefox Add-ons are reachable, but the guarantee stops at the curated set.

The practical test takes five minutes and should happen before anything else is decided. Write down the two or three extensions that the working day actually depends on, install Orion, and install those specific extensions. Not similar ones. The exact ones. A password manager that fills on some sites and silently fails on others is worse than no password manager, because the failure is discovered at the moment a login is needed rather than during the evaluation.

This is also where the comparison with a Chromium browser becomes concrete instead of philosophical. A Chromium browser runs Chrome extensions as a native format, so compatibility is the default state. Orion runs them through a compatibility layer, so compatibility is a per extension result. Neither arrangement is better in the abstract. One of them has a specific answer for a specific set of extensions, and that answer is findable in an afternoon.

Thirty tabs is a filing problem, not a memory problem

The usual framing is that too many tabs is a resource problem, and that the fix is a lighter browser. Orion markets in that direction, claiming lower memory use than Safari and far lower than Chrome. Those are vendor claims without a published methodology attached, so they belong in the category of things to verify on a specific machine rather than things to accept.

More to the point, memory is rarely what actually hurts. On a current Mac, thirty tabs load. What fails is retrieval. Finding the right tab takes a hover, a squint, or a keyboard search, and that lookup happens dozens of times a day. It is a filing problem wearing a performance problem's clothes.

Orion has more answers to the filing problem than most browsers, and they are worth naming individually because they solve different parts of it.

Vertical tree tabs give tabs a parent and child relationship, so a research thread can be collapsed and closed as a unit instead of one tab at a time. Tab groups take the opposite approach, splitting a large set into separate focused windows. Pinned tabs hold the handful of sites opened every morning in a fixed position that survives restarts. The tab group switcher shows a visual preview of open tabs when switching, which replaces favicon recognition with something a person can actually read. Focus mode hides the entire interface and turns one site into a full screen application, which is the closest thing in a conventional browser to giving a web app its own space.

Stacked together, these reduce the lookup cost meaningfully. What they do not do is change the underlying arrangement, which is still one window holding everything. Anyone whose real complaint is that work and personal accounts share a window will find that the tab tools improve the symptom without touching the cause. That distinction is covered in more depth on the page about Workspaces, which describes the alternative arrangement of giving each application a persistent place of its own.

Containers and profiles solve two different problems

Orion ships both containers and profile isolation, and they are frequently confused, which leads to people choosing the wrong one and concluding the browser does not work.

Containers separate cookies and sessions inside one window. The product page uses the example of searching flights in one container and hotels in another. Two accounts on the same service can be signed in simultaneously without signing out of either. This is the lightweight option and it covers most everyday account juggling.

Profile isolation is heavier and more thorough. The macOS page describes each profile as getting its own browser, its own custom icon and its own emoji in the dock, which is a stronger separation than the usual profile switcher inside a single application. A client account and a personal account end up as two visually distinct items rather than two entries in a menu.

The reason this matters more than it sounds: notification routing follows the separation. Anything that lives in one window competes for attention with everything else in that window, regardless of how well the cookies are partitioned. A browser that keeps each web application in its own window is answering that specific complaint, which is a different complaint from cookie separation. The Features page lays out how that arrangement differs from tab grouping, and it is worth reading before deciding which of the two problems is the one actually being solved.

How Orion sits against the other options

Everything below is drawn from the published pages of each product.

Option	Engine	Extensions	Account separation	Price
Orion	WebKit	Safari, Chrome and Firefox, curated set guaranteed	Containers and profile isolation	Free, optional membership from $5 per month
Safari	WebKit	Safari extensions	Profiles	Free with macOS
Chrome	Chromium	Chrome Web Store	Profiles	Free
Wavebox	Chromium	Chrome Web Store	Spaces and groups	Free tier limited to 2 groups with 2 apps each, Pro listed at $8.33 per month billed annually
Ferdium	Electron	Not a general browser	Services and workspaces	Free and open source

The table makes the shape of the decision visible. Orion competes on engine and extension breadth. The application oriented tools compete on arrangement, giving each service a fixed home instead of a tab. Those are different products aimed at different frustrations, and a comparison that puts them in a single ranking is measuring the wrong thing. Side by side breakdowns for the second category are collected in Compared with Wavebox and Compared with Ferdium.

The trade-offs worth knowing before switching

Three of them are structural rather than matters of taste.

The first is engine coverage. A minority of business web applications are built and tested against Chromium only, and video conferencing and screen sharing are the usual places this surfaces. WebKit handles the modern web well, but a single non negotiable internal tool that misbehaves is enough to force a second browser to stay installed, which undoes part of the reason for switching.

The second is platform reach. With Linux in beta and Windows in alpha, Orion is currently a decision for an individual on Apple hardware rather than a standard a mixed team can adopt. Anyone choosing a browser on behalf of other people should read the platform pages before making a recommendation.

The third is the size of the operation behind it. A browser maintained by a small independent company funded directly by its users has obvious advantages in incentives and obvious exposure in continuity. The trajectory of Arc has made that exposure concrete for a lot of people this year, and it is now a reasonable thing to weigh rather than paranoia. The practical hedge is unglamorous: keep bookmarks and passwords in something portable, so that a future move is an afternoon rather than a project.

Where switches actually fail, usually in week two

The first three days of any browser switch feel good, because novelty does a lot of work. The failures show up later, and they are predictable enough to plan around.

The most common one is the half move. The old browser stays installed for one stubborn site, then a second site joins it, and within a fortnight two browsers are running with sessions split between them. That is worse than either browser alone, because now a tab could be in one of two places. The fix is to decide in advance which sites are allowed to stay behind, write them down, and treat the list as closed.

The second is password friction. Autofill behaviour differs between a native Safari extension, a Chrome extension running through a compatibility layer, and the browser's own password manager. Orion ships a built in manager and also supports 1Password and iCloud Passwords from its curated list, which is three possible arrangements. Picking one deliberately on day one avoids the situation where credentials end up in two stores and neither is complete.

The third is a quiet one. A browser that is pleasant to use encourages keeping more tabs open, not fewer, because the cost of each additional tab feels lower. Vertical tree tabs and a visual switcher raise the ceiling on how much clutter is tolerable. That is an improvement in comfort and it can be a step backwards in focus, depending on whether the goal was to find tabs faster or to have fewer of them open at once. Deciding which of those two the week is meant to prove keeps the evaluation honest.

What to change first

Install Orion alongside the current browser rather than instead of it, then run the extension test and one week of normal work. If retrieval improves but account collisions and notifications stay exactly as annoying as before, the problem was never the tab strip, and the next thing to look at is an arrangement where each web application holds its own window, which is what SpaceDeck is built around.