Wavebox reviewed after a month of daily use

Most people arrive at a wavebox browser review after the same month. Tabs crossed forty, two Slack workspaces started fighting over the same window, a second Google account knocked the first one out of session, and somewhere in there a client email went to the wrong address. The search that follows is not really about features. It is about whether one specific product fixes that, what it costs to keep, and what it quietly takes away in exchange.

Wavebox is one of the older names in this category and one of the most complete. That completeness is the interesting part of the review, because it cuts both ways.

What it is organised around

Wavebox is a Chromium browser rebuilt around applications instead of tabs. The left edge holds a sidebar of apps arranged the way a phone home screen is arranged, grouped into containers the product calls Spaces and Groups. Each container carries its own signed-in session through cookie containers, which is the mechanism that lets two accounts of the same service stay logged in at once without either one dropping.

On top of that base sits an unusually long feature list. Split screen and multi window let two apps sit side by side with resizable panes. Focus Mode switches off notifications, badges and sounds in one move. Global Search runs across apps, tabs and dashboards rather than just the open page. Extensions come from the Chrome Web Store, with a set of built-in ones already present. A large library of what the product calls boosts adds per-app tweaks, and an assistant named Brainbox sits on top of pages.

The breadth is deliberate. This is a product that has been shipped and extended for years, and the feature list reflects requests collected over that time rather than a single tight idea. For someone who wants a lever for every situation, that history is the appeal. For someone who wants three things that work without configuration, it is the reason the first session feels crowded.

Because it is Chromium underneath, the pages themselves behave the way they do in Chrome. Rendering, extension APIs and developer tooling are familiar, and the sites that only ever get tested against Chrome work without argument. The base is conventional, and everything distinctive lives in the layer above it.

The free tier is a demonstration, not a home

This is the part that decides whether a trial goes anywhere. The Basic plan is free and permanent, and it allows two groups holding two apps each, one extension, and a single dashboard.

Two groups of two apps is four applications in total. A realistic minimum for the person who searched for this in the first place looks more like work mail, personal mail, two Slack workspaces, a project tool and a document tool, which is six before anything optional. The free tier is best read as a way to confirm that the app-shaped model suits how the day runs, not as a permanent setup. The one extension limit lands hardest on anyone whose password manager is a browser extension, since that single slot gets claimed immediately.

Anyone testing it should know that a seven day Pro trial is offered without a card, and that a thirty day money-back window applies to purchases. That combination means the honest test is possible: run the paid tier for a real week, including the busiest day of the month, rather than judging the free tier and concluding the product is thin.

What it costs next to the rest of the category

Tool	Free tier	Paid	Platforms
Wavebox	2 groups of 2 apps, 1 extension, 1 dashboard	Pro at $8.33 per month billed annually, Teams at $12.50 per user per month	macOS, Windows, Linux
Shift	5 Spaces, 10 apps per Space	Advanced at $199.99 per year	Mac, Windows
Ferdium	Full product, open source	No paid tier	macOS, Windows, Linux

Current figures come from each vendor's published pricing, including the Wavebox pricing page, and they change without notice. The structural difference matters more than the numbers. One product bills monthly against a small free tier, one sells a yearly licence with a usable free tier, and one is community maintained with no paid tier at all. A monthly subscription is easier to leave and easier to forget, which cuts both ways depending on how the year goes.

One detail worth knowing before paying full price: students, education staff and people working in the non-profit sector are directed to start the seven day trial with an education or .org address and then contact support to claim a discount. It is not advertised on the plan cards, and it is easy to miss.

Feature by feature detail against the approach taken here is set out on Compared with Wavebox, and the equivalent breakdown for the yearly-licence option is on Compared with Shift.

The two things reviewers keep returning to

Two themes appear across user reviews consistently enough to plan around.

Memory

Running many isolated sessions costs memory, and Wavebox is frequently described as heavy on RAM. That is not a defect so much as the price of the design: every container with its own cookie store and its own live page is a separate process, and separation is the product. Sleep and hibernation controls exist to claw some of it back by parking inactive apps, and using them is not optional on a machine with limited memory. Anyone on a base-configuration Mac should treat the trial week as a memory test as much as a workflow test, with Activity Monitor open at least once.

The learning curve

The second recurring note is that the product takes time to learn. With Spaces, Groups, cookie containers, profiles, boosts, dashboards and an assistant all present, the surface area is wide. Reviewers who report the best results describe setting it up once, deliberately, and leaving it alone. Reviewers who report frustration usually describe trying to use it like a normal browser and being surprised when it behaves like something else. The first week is configuration work, and pretending otherwise is how a trial gets wasted.

How the setup hour is actually spent

Since the first week is configuration, it helps to know what that hour contains before starting it.

The first decision is the grouping axis, and it is the one that gets changed later if it is chosen carelessly. Grouping by account puts every work login in one place and every personal login in another. Grouping by client puts one customer's chat, documents and tracker together regardless of which account signs into them. Grouping by task puts writing tools in one place and communication in another. All three are valid, and mixing them is what produces a sidebar nobody can navigate two months later.

The second job is the cookie containers. Two accounts of the same service need to be placed in different containers deliberately, because dropping both into one container recreates the original problem inside a nicer interface.

The third is the sleep policy, which is where the memory question gets answered in practice. Apps that need to deliver notifications, such as chat, should stay awake. Reference tools, dashboards and anything opened twice a week should sleep aggressively. Getting this wrong in either direction produces either a heavy machine or missed messages.

The fourth is notifications, one app at a time. The default state is everything alerting, which is the fastest way to conclude that a tool has made the day worse. Turning most of it off and leaving two or three sources on is what makes Focus Mode meaningful rather than decorative.

The last is the extension slot on the free tier, or the full extension set on Pro. Deciding what a password manager, an ad blocker and a clipper each need to see is a policy question, not a preference, especially on a machine that touches client accounts.

An hour spent on those five things produces a setup that survives. An hour skipped produces a second browser holding the same mess in a different shape, which is the honest description of most abandoned trials in this category.

What it does better than a stack of Chrome profiles

Chrome profiles already provide session isolation for free, so the useful question is what the paid layer adds.

The clearest gain is that apps become findable objects rather than tabs to hunt for. A sidebar with a fixed position for each app removes the search step, and unread badges attach to the app instead of being buried in a tab title. Split screen removes a whole class of window shuffling for anyone who works with a document and a chat open at once. Global Search across apps beats the profile approach outright, because profiles cannot see into each other.

The gain is smaller for someone whose real problem is two Google accounts and nothing else. That case is solved by a second Chrome profile in about four minutes, at no cost, and adding a subscription on top of it buys convenience rather than capability.

Where any wrapper stops being the answer on macOS

This applies to the whole category, and it is the reason some people abandon these tools in week three.

Everything lives inside one application. The macOS app switcher shows one icon, so reaching a specific client Slack means reaching the wrapper first and then finding the app inside it. Notifications are delivered under one application name, so Focus filters and per-app notification rules apply to the whole bundle rather than to the account that matters. Mission Control groups the windows together. Dock badges aggregate.

The sharpest edge is link handling. A calendar invite opened from a mail client, a link clicked in a desktop Slack app, a URL launched from a terminal: all of these go to whichever browser macOS treats as the system default, and that browser has no idea which account owns the link. Unless the tool holding the accounts is itself the default browser, the wrong-account error keeps arriving from outside.

None of this makes a wrapper the wrong choice. It does mean the choice is between two costs, not between a cost and a free lunch. Splitting the day by app so each one keeps a real window, a real icon and a real place in the app switcher is the other way to pay, and the reasoning behind it is laid out on Workspaces.

Who should actually try it

Try it if the day involves many different services rather than many accounts of one service, if extensions and per-app customisation matter, and if a Linux machine is part of the rotation, since cross-platform coverage is a genuine advantage here. Try it with the Pro trial rather than the free tier, and set aside an hour for setup instead of expecting it to feel right on first launch.

Skip it if the actual problem is two accounts of the same service, which browser profiles already solve, or if the machine is short on memory and the day is already close to the edge. Published pricing for the alternative approach is on Pricing.

What to change first

Before subscribing to anything, spend one week with a Pro trial and count two numbers by hand: how often the wrong account opened, and how often a known app had to be hunted for. If the first number dominates, session containers are the fix and this product is a strong candidate. If the second dominates, the fix is giving each app its own window and its own icon, which is the shape behind SpaceDeck.