Analytics and monitoring decision

Rybbit

Use the upstream open-source repo and self-host — a single technical person can stand up and run Rybbit for production use faster and cheaper than reimplementing it.

Visit website
Subscription$13/month ✓ verified
Initial build6 hours
Monthly upkeep6 hours + $30
Evidence1/1 runs agree

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

What a replacement has to do

  • Collect pageviews and events via the tracking script, ingest into a database, index session replay data, serve a dashboard with funnels/journeys/web vitals, and provide an API for exports.

What it still won’t have

  • Managed hosting (scaling, uptime SLA)
  • Priority support and managed backups
  • Enterprise features tied to hosted plan (e.g., dedicated instance, SSO via vendor)
  • Hosted data retention guarantees and billing convenience

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 3 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 Rybbit deployment: clone https://github.com/rybbit-io/rybbit and produce a Docker Compose deployment that runs the backend, web UI, and required services. Use PostgreSQL for metadata, an S3-compatible bucket for session replay storage, and an NGINX reverse proxy with TLS. Core features in scope: tracking script ingestion, autocapture, session replay storage/serving, funnels/goals, basic API export, user login, and a single-organization dashboard. Out of scope: reimplementing the UI, training new ML models, or creating a new tracking SDK. Provide scripted install (bash/Makefile), health checks, basic monitoring (disk, DB connectivity), automated daily backups, error handling, and a minimal test suite that verifies ingestion, replay storage, and dashboard listing.
How we checked5 sources · 1/1 runs agreed · evidence score 99

How the score was reached

  • Self-host verdict base92
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • 1/1 assessment runs agreed+4
  • Evidence score99

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 1 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded