Security and privacy decision

Visible Privacy

A small, useful consent manager is realistic to build and run in-house (multi-week) given mature open-source alternatives exist, though enterprise features, certifications, and broad integrations are costly to replicate.

Visit website
You pay

$7/mo

$84/yr

Read off the official pricing page.

You’d pay instead

$100one-off74 h to build

$45/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 8 seats.

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 Visible Privacy alternatives, with the arithmetic →

What a replacement has to do

  • Detect site scripts and cookies, show a customizable consent banner, block trackers until consent, record consent events, and expose integrations (e.g., Google Tag Manager/GA) for downstream analytics.

What it still won’t have

  • Enterprise SLA and dedicated support
  • ISO 27001 / certified infrastructure
  • White-label / reseller partner programs and commercial guarantees
  • Large catalogue of 50+ prebuilt integrations and on-demand scans
  • Advanced analytics, server-side GTM hosting and legal/compliance assurances

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 8 seats.

Paid seatsseats

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 self-hosted consent-management service using Node.js (Express), React for the admin and banner UI, Postgres for consent logs, and Nginx for TLS/hosting. Core features in scope: client-side customizable consent banner with preference modal, site cookie/script scanner, script-blocking loader that defers third-party scripts until consent, a REST API that records consent events to Postgres, Google Tag Manager/GA Consent Mode integration, and a minimal admin dashboard showing consent metrics and recent logs. Out of scope: ISO27001 certification, SLA-backed uptime guarantees, white-label reseller workflows, and enterprise multi-region infra. Include server-side and client-side input validation, comprehensive error handling, unit and integration tests for the API, and deployment scripts (Docker + docker-compose).
How we checked4 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • Evidence score63

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.

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