The Browser Is the Most Underrated Piece of Your Cross-Border Stack
Most cross-border operators I know run their entire business through a browser tab bar: Amazon Seller Central on one monitor, Shopify admin on another, a dozen TikTok Shop and Temu dashboards bookmarked, Helium 10 and Keepa open for research, Klaviyo for flows, a freight forwarder’s portal, three supplier chats, and a payment dashboard they check like a nervous tic. The browser is the actual operating system of a modern e-commerce business — and almost nobody thinks about it. That’s why Zigzag Browser, a native Mac browser built by Zigao Wang as a deliberate exit ramp from Arc, caught my attention. It’s not an e-commerce tool. But the way it thinks about workspaces, memory footprint, and account isolation maps almost perfectly onto the problems that make multi-marketplace selling miserable. Here’s what’s worth stealing, and where I think it falls short.
What Zigzag Actually Solves (And Why It’s Not Really About Browsers)
The pitch is simple: Arc users got burned when The Browser Company pivoted toward AI-first products and left power users feeling abandoned. Zigzag is the “life after Arc” answer — a native Mac browser that keeps the sidebar-and-spaces workflow people liked, but rebuilds it on WebKit instead of Chromium. The headline number is the one that matters: the whole app is 18 MB, versus Arc at 871 MB. That’s a 48x difference in install footprint, and it’s the kind of claim that should make any operator running a 16GB MacBook Air sit up.
The feature set reads like a love letter to people who organize their work by context rather than by window: colored spaces you swipe between, split view, peek, Chrome extension support (1Password and Tampermonkey are named explicitly), built-in ad blocking, one-import migration that brings over everything so you’re already logged in, no account required, and open source. The “no AI” line is clearly a positioning jab at Arc’s direction, and it’s a smart one — plenty of operators are fatigued by AI features bolted onto tools that didn’t need them.
But here’s the cross-border angle. The reason this matters to a seller isn’t the MB count. It’s that a browser with first-class “spaces” is a browser with first-class account isolation — and account isolation is the single most under-discussed operational risk in multi-marketplace selling.
Why Amazon sellers should care more than Shopify ones
A Shopify-only DTC operator lives in one admin, one Klaviyo account, one Meta Ads Manager. A browser is a browser. But an Amazon FBA brand owner running three marketplaces, two Seller Central accounts under different legal entities, a Vendor Central login, and a separate advertising console is one sloppy tab away from a linked-account flag. Amazon’s own Seller Central policies around related accounts are notoriously unforgiving, and the standard workaround — separate Chrome profiles, or a dedicated anti-detect browser — is clunky, expensive, or both. A lightweight native browser where each colored space is a clean, persistent container is a genuinely interesting middle path. Same logic applies to anyone juggling TikTok Shop seller centers across regions, or Temu and SHEIN supplier portals that don’t always play nice with the same cookies.
How It Stacks Up Against the Incumbents
Let me be blunt about the comparison set, because “a new browser” is a crowded category and most of them die.
Versus Arc. Arc’s problem was never the sidebar — it was the bloat and the strategic drift. Zigzag’s 18 MB vs. 871 MB framing is a direct attack on that, and the open-source, no-account posture is a trust play. If you were an Arc power user who fled, this is the most on-the-nose replacement I’ve seen.
Versus Chrome. Chrome is the default because everything integrates with it — Helium 10, Keepa, Jungle Scout’s extension, Shopify’s admin, every ad platform. Zigzag claims Chrome extension support, which is table stakes and also the hardest promise to keep. If 1Password and Tampermonkey work but your niche Amazon research extension breaks, the browser is dead to you. That’s the real test.
Versus anti-detect browsers like Multilogin or AdsPower — which I won’t link because the source doesn’t name them and I don’t want to imply an endorsement. Those tools solve account isolation properly, with fingerprint spoofing and proxy management, but they cost real money per profile and feel like spyware. Zigzag isn’t trying to be that. It’s a consumer browser with good workspace hygiene, which is a different (and honestly more honest) product.
Versus Safari. WebKit-native means it inherits Safari’s engine — good for battery, sometimes bad for site compatibility. Amazon Seller Central is a heavy, JavaScript-laden app. Whether Zigzag renders it cleanly is an empirical question, not a marketing one.
Where the math breaks
The 18 MB headline is real but slightly misleading as a decision metric. Install size isn’t runtime memory. A WebKit browser with ten tabs of Seller Central open will still eat RAM — the engine is leaner, but the web apps are the same web apps. The MB comparison tells you about disk and update friction, not about whether your 8GB machine will choke during Q4 peak. Don’t buy the number as a performance guarantee; treat it as a signal that the team cares about craft.
What Cross-Border Sellers Can Borrow From This
Even if you never install Zigzag, the product’s design philosophy is a checklist for how you should be structuring your own operating environment.
One space per marketplace, per entity. If you’re running US and EU Amazon accounts, or a Shopify store plus a TikTok Shop plus an Etsy shop, color-code them and never cross the streams. Etsy and eBay sellers with multiple shops face the same linkage risk Amazon does, just with less press. The browser-level container is the cheapest insurance you’ll ever buy.
Kill the account-required default. Zigzag’s “no account” stance is a quiet rebuke of every SaaS tool that forces a login before you can use a feature. Audit your stack: how many tools require an account just to view a dashboard? Each one is a credential you’re trusting and a session you’re leaking.
Extensions are your real integration layer. The browser is where Helium 10, Keepa, and your ad-blocker live. A browser that handles extensions well is worth more than a browser with a prettier UI. When you evaluate any tooling switch, ask what breaks at the extension layer first.
Open source as a continuity hedge. “Nobody can shut it down” is the pitch, and for operators who got rug-pulled by Arc’s pivot or by any number of dead SaaS tools, that’s not ideology — it’s business continuity. Prefer tools where your data and workflow survive the vendor.
The AI fatigue angle is real
The explicit “no AI” positioning deserves a paragraph of its own. Every tool in the e-commerce stack is now shipping an AI copilot, and most of them are mediocre. A browser that deliberately refuses to add one is making a bet that operators want speed and reliability, not another chatbot. I think that bet is correct for the browser category specifically — you don’t want your window to the internet making judgment calls — even if AI is genuinely useful elsewhere in the stack.
Where My Judgment Says It Falls Short
Three concerns, in order of how much they’d affect a seller.
Mac-only. The source is explicit: native Mac browser. The overwhelming majority of cross-border operations — especially China-based supplier-side teams and warehouse staff — run Windows. This is a boutique tool for the founder’s laptop, not a company-wide deployment. That limits it to the operator, not the operation.
Chrome extension compatibility is a promise, not a proof. WebKit doesn’t run Chrome extensions natively; any support is a compatibility layer. The source names 1Password and Tampermonkey, which are relatively simple. The heavy, DOM-scraping Amazon research extensions are exactly the ones most likely to break. Test before you commit.
No account sync cuts both ways. No account means no cross-device sync of your spaces and tabs. For a solo operator on one machine, fine. For a team, it means no shared workspace — which is precisely where the account-isolation benefit would be most valuable. There’s a tension there the product hasn’t resolved, at least not in the launch copy.
What I’d Watch / Test Next
This week, if you’re curious: install Zigzag on a secondary Mac (not your money machine), import from your current browser, and stress-test the two things that actually matter — whether your Amazon research extensions survive, and whether Seller Central renders cleanly under WebKit. Time-box it to an afternoon.
Then run the audit that matters more than the browser choice: list every marketplace and ad account you log into, and map each to a distinct browser container. If you’re currently sharing cookies across two Amazon entities or two TikTok Shop regions, fix that this week regardless of which browser you use. And watch whether Zigzag ships Windows and any form of team sync — those two features would move it from “interesting founder tool” to “plausible operating layer” for a real cross-border team. Until then, it’s a well-aimed product for a narrow slice of operators, and a useful reminder that the most important tool in your stack is the one you never think about.
