Uncategorised decision

Pola Browser

A competent developer can build the core persistent-folder browser and local restore using existing open-source browser projects as reference, but reproducing the full polished paid product (cloud sync polish, extensions, Keychain autofill, and app-store-ready packaging) is a larger effort best compared against running or forking existing open-source browsers.

Visit website

Built by Matteo Ricupero, who ships 4 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off120 h to build

$0/mo3 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Pola Browser alternatives, with the arithmetic →

What a replacement has to do

  • Open web pages in a macOS app, group tabs into persistent sidebar folders, restore session state on restart, and optionally sync folder state via Google Drive.

What it still won’t have

  • Polished cross-device installer, notarization, and app-store presence
  • Polished UX and performance tuning found in the paid product
  • Early extension integrations and convenience of built-in password autofill
  • Marketing, user support, and trust/brand of the vendor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Pola Browser does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal macOS productivity browser in Swift using WKWebView and SwiftUI. In scope: (1) a tabbed browser shell with navigation and basic history, (2) a left sidebar that lets users create named folders, drag tabs into folders, and open tabs from folders, (3) persistent local storage of folder and tab state using SQLite or a JSON file and automatic restore on launch, (4) Google Drive sync of the folder state via OAuth2 with basic conflict resolution, and (5) an optional floating always-on-top window mode for a tab. Out of scope: full browser extension engine, built-in password manager, Windows/Linux builds, analytics, and paid licensing flow. Include error handling for network and OAuth failures, unit tests for persistence and sync logic, and a README with build and code-signing steps.
How we checked4 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded