Security and privacy decision

Blurweb.app

A single competent developer can build and maintain a local-only browser extension that matches the core BlurWeb functionality in about a week; the vendor's cloud sync and license infrastructure are the main things you would not replicate.

Visit website

Built by Sanskar Tiwari, who ships 8 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-off32 h to build

$0/mo1 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • User installs a browser extension, hovers or draws a rectangle to select page elements, the extension overlays a blur on those elements and optionally saves the rule locally so the blur persists on page reload.

What it still won’t have

  • Cross-device sync and centralized license management (the product advertises sync across devices and license activation)
  • Official paid support, updates and license recovery workflows
  • Any server-side features the vendor may add later (analytics, remote revocation of licenses)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Blurweb.app 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 cross-browser extension (TypeScript, Webpack/Rollup, Manifest V3) with a React/Preact popup and a content script that: 1) adds an in-page hover selector and allows drawing a rectangle to choose an area; 2) applies a CSS blur overlay to the selected DOM node(s) and supports an adjustable blur intensity; 3) persists per-domain blur rules in chrome.storage.local (or browser.storage.local) and re-applies them on page load using selectors and element position heuristics; 4) uses MutationObserver to reapply blurs on dynamic pages; 5) provides UI to keep/clear blurs and keyboard shortcuts; 6) includes build scripts for Chrome/Firefox/Edge, extension manifest, CI tests (unit for core utilities and integration tests with puppeteer/playwright), error handling and telemetry-free privacy-safe logging. Out of scope: server-side sync, license verification, and paid account management.
How we checked3 sources · 2/3 runs agreed · evidence score 81

How the score was reached

  • Build verdict base78
  • 3 cited sources+3
  • Evidence score81

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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded