The Menu Bar Is the Last Unmanaged Surface in Your Ops Stack
Cross-border sellers obsess over the wrong dashboards. We tune Amazon PPC bids at 2 a.m. Shanghai time, wire Klaviyo flows for a DTC launch, and argue about 3PL SLAs — while the actual control plane of daily operations, the macOS menu bar, stays a junk drawer. Every freight tracker, VPN client, Shopify admin tab, and timezone clock fights for the same two inches of screen. That clutter isn’t cosmetic. It’s latency on every decision you make between supplier emails. So when a tool shows up claiming to impose order on that strip, I pay attention — even if it’s a free open-source utility with rough edges. Blenny, built by a developer posting as fish, is exactly that kind of tool.
What Blenny Actually Does — and Why the Mechanism Matters
Blenny is a macOS menu bar organizer. The pitch is simple: it gives menu bar apps three states — Visible, Revealable, and Hidden. You draft your groups and ordering, then hit Apply when you’re ready. Undo restores the previous change. Apps that spawn several menu bar icons get managed together as a unit, which is the detail that separates this from the dozen “hide your icons” utilities that have floated around for years.
The mechanism is what makes it interesting to me as an operator. According to the developer’s launch notes, Blenny never moves your pointer and never simulates dragging, and it doesn’t require Screen Recording permission. Ordering does require Device Control permission plus access to the menu bar layout file. That’s a meaningfully different security posture from the drag-simulation approach that most menu bar managers use, and for anyone running a work machine that touches payment credentials, ad accounts, or supplier contracts, permission surface area is not a trivial concern.
It’s built specifically for macOS 27 on Apple silicon. It’s free, with source available under Apache-2.0. There’s an interactive demo on the website, and the gallery’s Organize view is a recreation using sample apps rather than a live capture. The developer is asking for specific bug reports on GitHub rather than vague praise.
That’s the whole product. No pricing tier, no team plan, no upsell. Which is precisely why I think it’s worth a longer essay than the launch page deserves on its own.
The Incumbent Landscape Is Crowded and Mostly Stale
If you’ve been on a Mac for more than a decade, you remember Bartender, the category-defining menu bar manager that has gone through at least one controversial ownership change and a paid upgrade cycle that annoyed a chunk of its user base. Then came Hidden Bar, a free open-source alternative that does one thing — collapse icons behind a divider — and does it adequately. Ice arrived more recently as a fuller-featured open-source Bartender replacement, and Dozer occupies the minimalist end of the same spectrum.
Blenny’s differentiation isn’t feature count. It’s the three-state model plus the non-simulating mechanism. Bartender and Ice both lean on accessibility APIs and, in some configurations, screen capture tricks to render and move icons. Blenny’s developer explicitly says it avoids pointer simulation and Screen Recording entirely. Whether that claim holds up under scrutiny is something I can’t verify from a launch page — but the architectural choice is the right one to make, and it’s the kind of thing that matters more as macOS tightens permission prompts with each release.
Why Amazon sellers should care more than Shopify ones
Here’s a pattern I’ve noticed across operator setups. Shopify-first DTC people tend to work in a browser all day — Shopify admin, Klaviyo, Meta Ads Manager, a Slack window. Their menu bar is mostly noise: Dropbox, 1Password, a calendar widget. Annoying, not load-bearing.
Amazon sellers live differently. Their day is a relay between native-ish tools and browser tabs: Amazon Seller Central in one window, Helium 10 or Jungle Scout alongside it, a VPN client pinned open for regional marketplace access, Keepa running price alerts, a freight forwarder’s tracking portal, and at least one timezone clock because your FBA inbound shipment cutoff is calculated in Pacific time while your factory is in Shenzhen. That’s six or seven persistent menu bar items minimum, several of which spawn multiple icons. A tool that groups them by function — sourcing, logistics, ads, comms — and lets you reveal them on demand is a real workflow improvement, not a cosmetic one.
TikTok Shop and Temu operators sit somewhere in between, but they skew toward the Amazon profile because of how many native dashboards and third-party trackers they juggle. If you’re running multi-marketplace, the menu bar is your only always-visible status board. Treating it as decoration is a mistake.
What Cross-Border Operators Can Borrow From This Launch
I read a lot of Product Hunt launches, and most of them are noise for our industry. This one is useful less for what it is than for what it signals about how to think about your own tooling stack.
The three-state model is a good mental template. Visible, Revealable, Hidden isn’t just a menu bar taxonomy. It’s a decent way to classify every tool in your operation. Visible tools are the ones you touch hourly — Seller Central, your ad dashboard, your 3PL’s portal. Revealable tools are the ones you need within a click when something breaks — your freight forwarder’s tracking, your returns processor, your chargeback evidence folder. Hidden tools are the ones that should exist but never demand attention — backup services, VPN clients, password managers. Most sellers I audit have everything in the Visible bucket, which is why they feel busy without being productive.
Draft-then-apply is the right interaction pattern for risky changes. Blenny lets you stage a reorganization and commit it when you’re ready, with Undo as a safety net. That’s the same pattern you should demand from any bulk-operation tool in your stack. If your repricing tool or your inventory sync doesn’t let you preview a bulk change before it goes live across thousands of SKUs, you’re one fat-finger away from a margin disaster. The menu bar is low stakes; the principle isn’t.
Permission minimalism is a competitive feature. The developer’s insistence on avoiding Screen Recording and pointer simulation is worth noting because it’s the opposite of how most SaaS tools in our space behave. Look at how many Shopify apps request read access to your entire order history to do something that only needs product data. Look at how many Amazon tools want your full Seller Central credentials rather than scoped API access. Every permission you grant is a liability. When you evaluate your next tool — whether it’s a returns management platform or a landed cost calculator — ask what the minimum viable permission set is, and be suspicious of vendors who won’t tell you.
Self-signed and notarization-free is a tradeoff, not a dealbreaker. More on this below, because it’s where my judgment gets less generous.
Where My Judgment Says It Falls Short
I want to like Blenny more than I do, and the reasons I don’t are mostly about maturity rather than concept.
The caveat list is long for a tool this narrow. The developer is admirably upfront: the app is self-signed and not Apple-notarized. Some unattributed icons can disappear while management is active. Clicking the clock won’t open Notification Center until you stop management — the trackpad gesture still works. Multi-display setups haven’t been tested. Those limits are documented in the README, which I respect, but “clicking the clock breaks Notification Center” is the kind of bug that will drive a busy operator insane within an hour. If you rely on Notification Center for Slack DMs from your sourcing agent or calendar alerts for supplier calls, this is a real workflow tax, not a footnote.
Not notarized is a genuine enterprise problem. For a solo operator on a personal Mac, self-signed is fine if you’re comfortable with the security prompt. For anyone running a team, or anyone whose laptop is subject to a corporate MDM policy, an un-notarized binary is likely to be blocked outright or flagged in a way that creates IT tickets. That’s not a knock on the developer — notarization costs money and time, and this is a free Apache-2.0 project — but it does mean Blenny is realistically a solo-operator tool for now, not something you’d standardize across a five-person ops team.
Multi-display being untested is a bigger deal than it sounds. A lot of cross-border operators run a laptop plus an external monitor, especially anyone doing creative work for TikTok Shop or managing listing images for Amazon. If you’re in that configuration, you’re the beta tester. The developer says so explicitly, which is honest, but it means you should not install this on your primary work machine the week before Q4 peak.
The category has a graveyard problem. Menu bar managers have a history of abandonment. Bartender changed hands and alienated users. Hidden Bar is maintained but minimal. Ice is newer and still finding its footing. Blenny is a one-developer project with a GitHub issue tracker as its support model. That’s fine for a free utility, but it means you should treat it as a tool you might have to replace, not infrastructure you build workflows around. Don’t let your morning routine depend on it.
Where the math breaks
If you’re a solo operator, the math is simple: free tool, thirty minutes of setup, modest quality-of-life gain. Worth trying on a secondary machine.
If you’re running a team, the math breaks immediately. You can’t deploy an un-notarized app at scale without IT involvement. You can’t rely on a one-person project for a workflow that touches everyone’s daily routine. And the Notification Center bug alone means you’d field complaints. For teams, the honest answer is: wait for notarization, wait for multi-display support, and revisit in six months. If the project is still alive and the caveats have shrunk, it becomes a real candidate. If it’s abandoned, you’ve lost nothing.
What I’d Watch / Test Next
This week, if you’re curious, do three things. First, install Blenny on a secondary Mac — not your primary trading machine — and run it for two full working days with your real menu bar load: VPN, timezone clock, freight tracker, ad tools. Note specifically whether the Notification Center breakage interferes with anything you actually use, and whether any icons vanish in a way that costs you a click. Second, file at least one specific bug report on the GitHub repo if you hit something reproducible; the developer explicitly asked for that, and it’s how open-source tools in this category survive. Third, and more importantly, apply the three-state framework to your broader stack. List every tool you touch in a week and bucket it Visible, Revealable, or Hidden. I’d bet you find at least three subscriptions you’re paying for that belong in the Hidden bucket — or should be cancelled entirely. The menu bar is a small surface. The discipline of deciding what earns a permanent spot on it is not.
