invisit
Compare

Rybbit alternative: invisit vs Rybbit compared

Rybbit is open source and self-hostable, with session replay on Pro, retention cohorts and user profiles. invisit costs $49 at 1M events against $69 on Rybbit Standard and $139 on Pro, and adds a free plan, heatmaps, revenue from your payment provider, alerts and data kept forever.

.mdllms.txt

Written by the invisit team. Facts about Rybbit checked on , from their own pages.

Choose invisit if

  • You want a free plan. New Rybbit sites collect nothing without a trial or a paid plan.
  • You want click and scroll heatmaps, revenue from Stripe or Paddle, short links, feedback and traffic alerts. Rybbit has none of them.
  • You want data kept forever on every plan, not 3 years on Standard or 5 on Pro.
  • You want web vitals and crawler reads never billed. Rybbit counts web vitals and autocaptured clicks as events.
  • You want a visitor hash that rotates daily by default, not a switch you have to turn on.

Choose Rybbit if

  • You want to self-host. Rybbit is AGPL-3.0 and runs with Docker on a VPS with at least 2 GB of RAM.
  • You want session replays (Rybbit Pro or self-hosted), retention cohorts or user profiles next to your traffic.
  • You want feature flags, experiments or custom SQL dashboards in the same tool as your analytics.
  • You want your Plausible, Umami or Simple Analytics history imported. invisit cannot import history.
  • You pay yearly: a Rybbit year costs eight months, an invisit year nine.

What a month costs

Monthly billing, cheapest plan step that covers the volume. invisit bills events (page views and custom events); Rybbit bills events (page views, custom events, web vitals, outbound and autocaptured clicks). Rybbit's slider says pageviews; its billing docs also count web vitals, outbound links and autocaptured clicks. Session replay needs Pro. Above 50M is Enterprise. A year costs eight months' price.

Monthly price, invisit and Rybbit
A month ofinvisitRybbit StandardStandardRybbit ProPro
10KFree$19$39
100K$14$19$39
1M$49$69$139
10M$199$249$499

Feature by feature

Features, invisit and Rybbit
FeatureinvisitRybbit
Privacy and setup
No cookies, no consent banner neededDaily-rotating hashNo cookies; the visitor hash lasts across days unless salting is on
Data stored in the EUFalkenstein, Germany (Hetzner)Hetzner in Germany and Finland; Cloudflare for CDN and replay storage
Lightweight script (under 10 KB)About 9.8 KB gzipped; extras load on demandAbout 11.8 KB gzipped; session replay loads about 82 KB more
Serve from your own domain@invisitdev/server proxyGuides for Next.js, Nginx, Caddy, Vercel, Cloudflare Workers and more
Open sourceTracker and SDKs, MITAGPL-3.0; self-host with Docker and ClickHouse
Import history from another toolNoPlausible, Umami and Simple Analytics; paid plans or self-hosted
Analytics
Realtime viewYesLive visitors and a real-time globe
Custom events and goalsYesEvents, goals and autocapture; autocaptured clicks bill as events
FunnelsYesEvery plan
Per-visit timelinesEvery visit step by step at any age: in the dashboard, the API and MCPSessions with timelines and user profiles; replays on Pro
Retention cohortsNoDaily or weekly retention cohorts, every plan
HeatmapsClicks, rage and dead clicks, scroll depthNo click or scroll heatmaps
Session recordingsNoPro plan (replays up to 10% of the event limit) or self-hosted
Web vitalsNever billedLCP, CLS, INP, FCP and TTFB; Cloud only, billed as events
JavaScript error trackingGrouped, tied to visits, with its own allowance: 5K reports a month on FreeGrouped by message with stack traces, every plan
AI assistant referralsChatGPT, Claude, Perplexity, Gemini and moreAI channel: ChatGPT, Claude, Gemini, Perplexity, Copilot and more
Crawler reads (search and AI bots)Recorded server-side, never billed; by bot and by page, with AI training and AI answers apartBots page on Cloud; crawlers that run no JavaScript need server reports
RevenueRead from Stripe, Polar, Paddle, Dodo Payments, Creem and Lemon SqueezyNo
Revenue by sourcePaid plans: by source, campaign, landing page and short linkNo
Queries from Google Search ConsoleEvery plan: clicks, impressions, CTR and position, per site and pageCloud only, beside your analytics
Beyond the dashboard
Traffic alertsSpikes, drops, silence and error spikes, to Slack, Discord, ntfy or a webhookNo
Email reportsEvery plan: what changed, on MondaysWeekly email summary per site, Cloud only
Public dashboardsYesPublic dashboards, password-protected links and embeds
Short linksYesOutbound link clicks only, no short links
On-page feedbackYesNo
APIREST, with an OpenAPI documentEvery plan; 5,000 requests a day on Standard, 25,000 on Pro
MCP server for AI assistantsYesHosted, read and write, with OAuth or an API key
Plans
Free plan20K events a month, nearly every featureNo free plan for new sites; a 7-day trial
Free trial14 days on monthly plans, card required7 days on the first subscription
Sites4 free, unlimited on paid plans5 on Standard, unlimited on Pro
Team membersUnlimited, on every plan3 on Standard, 100 on Pro
Data keptForever, on every plan3 years on Standard, 5 years on Pro

How much does Rybbit Cloud cost compared with invisit?

invisit costs less than Rybbit Standard, or the same, at every volume up to 3M events, and less than Rybbit Pro at every volume. As of November 2026, Rybbit’s pricing is $19 a month for 100K events on Standard and $39 on Pro, $69 and $139 for 1M, and $249 and $499 for 10M. invisit is free to 20K events, then $14 for 100K, $49 for 1M and $199 for 10M.

The steps in between, on monthly billing:

Events a month invisit Rybbit Standard Rybbit Pro
250K $24 $29 $59
500K $49 $49 $99
2M $99 $99 $199
3M $99 $149 $299
5M $199 $149 $299

Rybbit Standard is cheaper at 5M, where invisit’s next step is its 10M plan. Paid yearly, Rybbit costs eight months’ price and invisit nine (invisit billing), so at 1M a year is $552 on Rybbit Standard and $441 on invisit.

What counts differs. Rybbit’s slider is labelled in pageviews, but its billing docs count page views, custom events, web vitals, outbound link clicks, and autocaptured button clicks, copies, form submits and input changes. A site with 300K page views and 30K custom events uses 330K events on both and pays $49 on either. Turn on Rybbit’s web vitals or button-click autocapture and those count too, so the same site can cross into Rybbit’s 1M step at $69. invisit bills page views, custom events and its own outbound clicks and downloads, and never bills web vitals, heatmap clicks or crawler reads.

At the limit, Rybbit stops collecting for the organization’s sites until the next month or an upgrade. invisit warns at 80% of your plan, records all of a first month over, and pauses new events at the limit only in a second month over in a row.

Which Rybbit features need Standard or Pro?

Every current Rybbit Cloud plan is Standard or Pro, and Pro adds session replay, unlimited sites and members, and two more years of data. invisit has one feature set on every paid plan, and its free plan has nearly every feature.

Feature Rybbit Standard Rybbit Pro invisit paid plans
Price at 1M events $69 $139 $49
Sites 5 Unlimited Unlimited
Team members 3 100 Unlimited
Data kept 3 years 5 years Forever
Session replays No Up to 10% of the events No
Heatmaps No No Yes
API requests a day 5,000 25,000 REST API
Revenue No No From your provider
Import history from Last 24 months Last 60 months No import

Funnels, goals, journeys, retention, sessions, user profiles, web vitals and error tracking are on both Rybbit plans (Rybbit’s billing). New Rybbit sites need a trial or a plan to collect anything: sites created since February 13, 2026 in an organization without one record no data. The trial is 7 days, once per organization; invisit’s is 14 days on a monthly plan, with a free plan after it.

Can you self-host Rybbit instead of paying for Cloud?

Yes. Rybbit is open source under AGPL-3.0, and invisit is hosted only: its tracker and SDKs are MIT, but its dashboard and backend are not available to run yourself.

Rybbit’s quick start asks for a VPS with at least 2 GB of RAM and a domain with HTTPS, and installs Rybbit with Docker on ClickHouse. A self-hosted instance has session replay without a plan gate, no replay quota, no API rate limits and unlimited imports.

Some of Rybbit stays on Cloud. Its self-hosted vs Cloud table leaves web vitals, email reports, Search Console, the Bots page, the Pages view and custom SQL dashboards out of self-hosted Rybbit, and a self-hosted instance sends no email, so there are no invitations or password resets. You take on the server: updates, backups and ClickHouse.

Neither Rybbit nor invisit sets cookies. The difference is how long a visitor stays recognisable. Rybbit’s site settings say its user ID is a hash of IP address and user agent, which links a visitor across days and “may be considered storing personally identifiable data under GDPR”. Turning on User ID Salting makes the hash change daily, at the cost of user history past 24 hours and a retention report Rybbit calls effectively useless.

Salting is off for a new site: the setting defaults to false in Rybbit’s schema, although Rybbit’s features page says IDs are re-salted daily. invisit’s hash rotates every day for every site, so nobody is followed from one day to the next.

Signed-in users differ too. rybbit.identify() keeps the ID you pass in localStorage, and Rybbit’s identify docs say custom user IDs are not hashed. invisit hashes the id you pass to identify() and keeps only the hash, and redacts email addresses in property values. invisit can also honour Global Privacy Control and Do Not Track, and has an optional consent mode (privacy guide).

Rybbit Cloud stores analytics on Hetzner in Germany and Finland, and lists Cloudflare for CDN, DNS and object storage, including session replay recordings (Rybbit’s subprocessors). invisit stores everything in Falkenstein, Germany, with Cloudflare in front for DNS and CDN, and a DPA is available.

Rybbit session replay vs invisit heatmaps

Rybbit records sessions and has no heatmaps; invisit has heatmaps and records no sessions. Which one you want depends on whether you watch individual visitors or read a page’s clicks in aggregate.

Rybbit’s session replay is a Pro feature on Cloud. It records mouse movement, clicks, scrolls and navigation, masks inputs by default, and lists clicks and rage clicks on a timeline beside the player. Each month it records up to 10% of the plan’s event limit, 100,000 replays on a 1M plan, and Pro trials of 500K events or more leave replay out. Recording loads replay.js, which measured 81,673 bytes gzipped on November 16, 2026, on top of the 11,767-byte script.js.

invisit’s heatmaps record clicks, rage clicks, dead clicks and scroll depth over your real pages, on every plan and never billed. Each visit’s pages and events stay in order at any age, in the dashboard, the API and MCP (visits), with no recording of the screen.

Both track JavaScript errors. Rybbit groups them by message with stack traces and counts them per session (errors). invisit groups them, ties them to visits and gives them their own allowance, 5,000 reports a month on Free, that never counts as events (errors).

Does Rybbit show AI assistant traffic and crawler reads?

Both do, in similar ways. Rybbit’s Channels report has an AI channel and a Paid AI channel, with referrers from ChatGPT, Claude, Gemini, Perplexity, Copilot, DeepSeek, Grok, Mistral and others (Rybbit’s list). invisit recognises 19 assistants by referrer and utm_source in its own AI tab (how it works).

Rybbit Cloud’s Bots page shows which AI agents and crawlers read which pages, split into agents, answer engines and training, and how many visits each operator sent back. It counts only bots that run JavaScript, unless your server reports the rest through Rybbit’s tracking API, and it needs Block Bot Traffic on. invisit records crawler reads server-side with @invisitdev/server, including user-triggered fetches like ChatGPT-User. Neither bills them.

When Rybbit is the better choice

Rybbit is the better pick in these situations, and some are things invisit does not do at all.

  • You need to self-host. invisit has no self-hosted edition.
  • You want session replays. Rybbit Pro records them on Cloud, and self-hosted Rybbit has no quota; invisit has no recordings.
  • You want product analytics for signed-in users: retention cohorts, user profiles with traits, and user journeys. invisit has no retention cohorts.
  • You want feature flags, experiments or custom SQL dashboards in the same tool.
  • You are leaving Plausible, Umami or Simple Analytics and want your history: Rybbit imports all three on paid plans.
  • You pay yearly, or run around 5M events: Rybbit Standard is $149 at 5M against $199 on invisit.

Switching from Rybbit to invisit

Run both side by side before you remove anything. Both trackers are cookieless and can sit on the same pages.

  1. Install invisit next to the Rybbit script and leave Rybbit running for two to four weeks, so you can compare the numbers.
  2. Replace each window.rybbit.event() call with track(), as below. invisit event names use letters, digits and _ . : -, up to 64 characters, with up to 32 properties; Rybbit names can run to 256 characters, so Signup Button Clicked becomes signup_button_clicked.
  3. Replace rybbit.identify() with identify(). Traits have no equivalent; put the ones you need on events as properties.
  4. Replace rybbit.error() with captureError(), and turn on error tracking for the site.
  5. If you proxied Rybbit’s script, the @invisitdev/server proxy does the same for invisit.
  6. Keep your Rybbit history before you cancel, because invisit cannot import it. On Cloud, Rybbit’s API returns events and sessions; self-hosted, your history is already in your ClickHouse database.
Rybbit invisit
script.js?siteId=123 in the script URL init({ site: '<site id>' })
window.rybbit.event('signup', { plan }) track('signup', { plan })
data-rybbit-event="signup" data-invisit-event="signup"
data-rybbit-prop-plan="pro" data-invisit-prop-plan="pro"
window.rybbit.identify(user.id, traits) identify(user.id)
window.rybbit.error(error) captureError(error)
src/analytics.ts
// Rybbit: the script tag defines window.rybbit
window.rybbit.event('Signup Button Clicked', { plan: 'pro' })
window.rybbit.identify(user.id, { plan: 'pro' })

// invisit
import { identify, init, track } from '@invisitdev/web'

init({ site: '<site id>' })
track('signup_button_clicked', { plan: 'pro' })
identify(user.id)

See identifying signed-in users for when to call identify(), and connect your payment provider to see revenue, which Rybbit does not track.

Why teams pick invisit

invisit starts from a simple question: who actually came to your site, and what brought them there? So it leads with people, not only totals. Each visit keeps its pages and events in order, next to where it came from, including the AI assistants that now send real visitors.

It also covers the jobs that usually need a second tool. Revenue arrives straight from your payment provider, and paid plans split it by the source behind each payment. Crawler reads show which search engines and AI bots read your pages, Google Search Console queries show what people searched, and heatmaps, web vitals, short links and feedback sit in the same dashboard. Every paid plan has every feature, so there is no tier to outgrow.

And it stays out of your visitors’ way: no cookies, no banner, nothing that follows anyone from one day to the next.

invisit or Rybbit? Common questions

Is invisit cheaper than Rybbit?

At 1M events a month invisit costs $49 a month, and Rybbit Standard costs $69 a month and Rybbit Pro costs $139 a month, so invisit costs 65% less than Rybbit Pro. invisit bills page views and custom events; Rybbit bills events (page views, custom events, web vitals, outbound and autocaptured clicks). Prices checked against Rybbit's pricing page on November 16, 2026.

Does Rybbit have a free plan?

No, Rybbit has no free plan: no free plan for new sites; a 7-day trial. invisit is free up to 20K events a month with no time limit, and its free plan has nearly every feature.

What does invisit have that Rybbit does not?

invisit includes lightweight script (under 10 KB), heatmaps, revenue, revenue by source, traffic alerts, short links, on-page feedback, and free plan; Rybbit does not, as of November 16, 2026.

When should I choose Rybbit over invisit?

Rybbit suits you better than invisit when one of these is true. You want to self-host. Rybbit is AGPL-3.0 and runs with Docker on a VPS with at least 2 GB of RAM. You want session replays (Rybbit Pro or self-hosted), retention cohorts or user profiles next to your traffic. You want feature flags, experiments or custom SQL dashboards in the same tool as your analytics. You want your Plausible, Umami or Simple Analytics history imported. invisit cannot import history. You pay yearly: a Rybbit year costs eight months, an invisit year nine.

When should I choose invisit over Rybbit?

invisit suits you better than Rybbit when one of these is true. You want a free plan. New Rybbit sites collect nothing without a trial or a paid plan. You want click and scroll heatmaps, revenue from Stripe or Paddle, short links, feedback and traffic alerts. Rybbit has none of them. You want data kept forever on every plan, not 3 years on Standard or 5 on Pro. You want web vitals and crawler reads never billed. Rybbit counts web vitals and autocaptured clicks as events. You want a visitor hash that rotates daily by default, not a switch you have to turn on.

Can I self-host Rybbit for free?

Yes. As of November 2026 Rybbit is AGPL-3.0 and self-hosts with Docker and ClickHouse on a VPS with at least 2 GB of RAM, with session replay and no rate limits. Web vitals, email reports, Search Console, the Bots page and SQL dashboards stay Cloud only, and a self-hosted instance sends no email. invisit has no self-hosted edition; its tracker and SDKs are MIT.

Does Rybbit use cookies?

No. Rybbit's tracker sets no cookies. Its visitor ID is a hash of the IP address and user agent that stays the same across days unless you turn on User ID Salting per site, and Rybbit's docs say the unsalted ID may count as personal data under the GDPR. invisit sets no cookies and rotates its visitor hash every day by default.

What counts as an event on Rybbit Cloud?

As of November 2026, Rybbit counts page views, custom events, web vitals, outbound link clicks, and autocaptured button clicks, copies, form submits and input changes, across an organization's sites. Its pricing slider is labelled in pageviews. invisit bills page views and custom events; web vitals, heatmap clicks and crawler reads are free.

Does Rybbit have heatmaps?

No. As of November 2026, Rybbit's features and docs describe no click or scroll heatmaps; the only heatmap is a weekday-by-hour traffic chart. Its session replays on Pro show clicks and rage clicks one session at a time. invisit has click, rage click, dead click and scroll depth heatmaps, and no session recordings.

Where does Rybbit Cloud store data?

Rybbit Cloud stores analytics on Hetzner in Germany and Finland. Its subprocessor list names Cloudflare, a US company, for CDN, DNS and object storage, including session replay recordings. invisit stores analytics in Falkenstein, Germany, on Hetzner, with Cloudflare in front for DNS and CDN, and has no session recordings.

Can I move my Rybbit history into invisit?

No. invisit cannot import history from another tool. Rybbit Cloud has an API with endpoints for events and sessions on every plan, and self-hosted Rybbit keeps everything in your own ClickHouse database. Pull what you want to keep before you cancel, and run both side by side for a few weeks.

More comparisons