Skip to content

🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.

Enhance comparison pages with deep dive sections for analytics tools

Bill Yang9f6e3d0b998f
diff --git a/docs/content/blog/_meta.js b/docs/content/blog/_meta.js
index f11f9979a..92588524e 100644
--- a/docs/content/blog/_meta.js
+++ b/docs/content/blog/_meta.js
@@ -1,4 +1,8 @@
export default {
+ "best-google-analytics-alternatives":
+ "The 9 Best Google Analytics Alternatives in 2026 (Free & Paid)",
+ "best-web-analytics-tools":
+ "The 10 Best Web Analytics Tools in 2026, Compared by Use Case",
"5k-stars":
"How my open source SaaS got 5,000 Github stars in 9 days with zero marketing effort",
"website-traffic-drop":
diff --git a/docs/content/blog/best-google-analytics-alternatives.mdx b/docs/content/blog/best-google-analytics-alternatives.mdx
new file mode 100644
index 000000000..2b4f65966
--- /dev/null
+++ b/docs/content/blog/best-google-analytics-alternatives.mdx
@@ -0,0 +1,173 @@
+---
+title: "The 9 Best Google Analytics Alternatives in 2026 (Free & Paid)"
+description: "Looking for a Google Analytics alternative? We compare 9 GA4 alternatives on pricing, privacy, features, and self-hosting β€” including free and open-source options."
+date: 2026-07-19
+tags: ["analytics", "privacy", "comparisons"]
+author: Rybbit Team
+---
+
+Google Analytics is still the default β€” and still the tool people most want to leave. Since the forced GA4 migration, the complaints have been remarkably consistent: the interface buries simple questions under 150+ reports, busy properties get sampled data, cookie-based tracking forces consent banners that silently drop a third or more of your real traffic, and several EU data-protection authorities have ruled that Google Analytics data transfers violated GDPR.
+
+The good news is that the alternatives in 2026 aren't compromises anymore. Several of them ship features GA4 has never had β€” session replay, error tracking, uncomplicated funnels β€” while staying cookie-free and consent-banner-free.
+
+Full disclosure up front: we build [Rybbit](https://rybbit.com), the first tool on this list. We've kept every claim about the other tools factual β€” pricing and limits below come from each vendor's own published pages as of July 2026 β€” and we'll tell you honestly when another tool is the better fit.
+
+## Quick comparison
+
+| Tool | Starting price | Free tier | Open source / self-host | Best for |
+| --- | --- | --- | --- | --- |
+| [Rybbit](#1-rybbit) | $19/mo (100k events) | ❌ (7-day trial) | βœ… Free | Teams that want GA4-level depth without the complexity |
+| [Plausible](#2-plausible) | $9/mo (10k pageviews) | 30-day trial | βœ… Community Edition | Simple, lightweight traffic stats |
+| [Matomo](#3-matomo) | €29/mo cloud (50k hits) | Free on-premise | βœ… Free | Feature parity with old Universal Analytics |
+| [Fathom](#4-fathom-analytics) | Slider pricing ($45/mo at 500k) | 7-day trial | ❌ | Set-and-forget simple stats |
+| [Umami](#5-umami) | $20/mo (1M events) | βœ… Free Hobby plan | βœ… Free (MIT) | Developers and hobby projects |
+| [PostHog](#6-posthog) | Usage-based after free tier | βœ… 1M events/mo free | Partially | Product teams that want the full toolkit |
+| [Simple Analytics](#7-simple-analytics) | $20/mo | βœ… For hobby sites | ❌ | EU-hosted simplicity |
+| [Pirsch](#8-pirsch) | $6/mo (10k pageviews) | 30-day trial | Enterprise only | Budget-friendly privacy analytics |
+| [Cloudflare](#9-cloudflare-web-analytics) | Free | βœ… Entirely free | ❌ | A free rough signal, not a GA replacement |
+
+## Why people are leaving GA4
+
+Before the list, it's worth being precise about what you're escaping, because it determines which alternative fits:
+
+- **Consent loss.** GA4 needs cookies, so GDPR/ePrivacy requires a consent banner in most jurisdictions. A large share of visitors decline. Teams that switch to cookieless analytics routinely find their real traffic is 30–60% higher than GA4 reported.
+- **Sampling and retention.** Complex reports on busy properties get sampled, and standard GA4 properties keep event-level data for at most 14 months. Unsampled exports live in GA360, which starts around $50,000/year.
+- **Complexity.** GA4 is an event warehouse with a reporting UI, not an analytics product. Most teams need a dashboard, not a data modeling project.
+- **Legal risk.** Data-protection authorities in Austria, France, and Italy all found GA's EU–US transfers unlawful in the Schrems II era. The regulatory direction hasn't reversed.
+
+If you searched for a **GA4 alternative** specifically because of one of these, jump to the tool that fixes it: consent loss and legal risk β†’ any cookieless tool below; sampling β†’ [Rybbit](#1-rybbit) or [Matomo](#3-matomo); complexity β†’ [Plausible](#2-plausible), [Fathom](#4-fathom-analytics), or [Pirsch](#8-pirsch).
+
+## 1. Rybbit
+
+**Best for: teams that want GA4-level depth β€” funnels, session replay, error tracking β€” without GA4's complexity or cookie banners.**
+
+[Rybbit](https://rybbit.com) is an open-source, cookie-free analytics platform that deliberately sits between the "simple stats" tools and the heavyweight product-analytics suites. The dashboard reads like Plausible β€” one page, instantly legible β€” but underneath it ships the features that usually force teams back to Google: [funnels](/features/funnels), [user journeys](/features/user-journeys), [session replay](/features/session-replay), [error tracking](/features/error-tracking), [Web Vitals](/features/web-vitals), user profiles, and custom events with attributes.
+
+Because it's cookie-free with daily-rotating visitor hashes, you don't need a consent banner, and you see every visitor β€” including the ones GA4's banner was hiding from you. There's no sampling at any traffic level. Independent reviewers have come to the same conclusion: Travis of travis.media called Rybbit [the best Google Analytics alternative](https://travis.media/blog/rybbit-best-google-analytics-alternative/) after testing it against the field.
+
+- **Pricing:** from $19/month for 100k events, 7-day free trial. Every feature is on every plan; [session replay](/features/session-replay) comes with Pro. See [pricing](/pricing).
+- **Self-hosting:** fully open source and [free to self-host](/docs/self-hosting) with Docker.
+- **Limitations:** no historical import from GA4 (nobody has this β€” Google only exports to BigQuery). Importers exist for Plausible, Umami, and Simple Analytics. Rybbit is also younger than Matomo or Plausible, though it ships features neither has.
+
+## 2. Plausible
+
+**Best for: simple, lightweight traffic stats with the longest track record among privacy tools.**
+
+Plausible is the tool that made privacy-first analytics mainstream: a single-page dashboard, a script it advertises as ~54Γ— smaller than GA's, and cookieless tracking that needs no consent banner. It's open source, EU-hosted, and independent.
+
+The trade-off is depth. Plausible intentionally stops at traffic analytics β€” goals and simple funnels exist, but there's no session replay, no error tracking, no user-level view. If your questions are "where do visitors come from and what do they visit," it answers beautifully; if you ask "why did signups drop," you'll need another tool alongside it.
+
+- **Pricing:** Starter $9/month for 10k pageviews (1 site); Growth $14/month and Business $19/month add sites and team members. 30-day trial, no card required. Two months free on annual billing.
+- **Self-hosting:** free Community Edition.
+- **Limitations:** pageview-based pricing climbs with traffic; feature set is deliberately minimal.
+
+See our detailed [Rybbit vs Plausible](/compare/plausible) comparison.
+
+## 3. Matomo
+
+**Best for: teams that want the closest thing to old Universal Analytics, or a mature free self-hosted option.**
+
+Matomo (formerly Piwik) is the veteran of this list β€” nearly two decades old, with the largest feature surface of any GA alternative: heatmaps, A/B testing, tag manager, and hundreds of plugins. Its free on-premise Community Edition has no hit limits, which has made it the default for public-sector and compliance-heavy deployments.
+
+The honest downside is age: the interface feels like the era it came from, and the full feature set on-premise means assembling paid plugin bundles (Team bundles from €275). Cloud pricing is hit-based and EU-hosted (Frankfurt) with no data sampling.
+
+- **Pricing:** cloud from €29/month for 50k hits; free trial with no card. On-premise Community Edition is free forever.
+- **Self-hosting:** yes β€” the most battle-tested self-hosted analytics there is.
+- **Limitations:** dated UX, plugin-based pricing complexity, heavier to run than newer tools.
+
+See [Rybbit vs Matomo](/compare/matomo).
+
+## 4. Fathom Analytics
+
+**Best for: set-and-forget simple stats from a long-running independent company.**
+
+Fathom was one of the first paid privacy-analytics products, and it stays deliberately simple: one dashboard, cookieless tracking, forever data retention, and every plan includes at least 50 sites. It's a polished, stable product from a small company that's been profitable for years.
+
+- **Pricing:** slider-based by pageviews; $45/month at 500k pageviews (the entry 100k tier is priced lower on their slider). 7-day trial; two months free on annual billing. No free tier β€” their FAQ is upfront about that.
+- **Self-hosting:** not offered.
+- **Limitations:** simple by design β€” no funnels on the level of product tools, no replay, no self-hosting.
+
+See [Rybbit vs Fathom](/compare/fathom).
+
+## 5. Umami
+
+**Best for: developers and hobby projects that want free, minimal, MIT-licensed analytics.**
+
+Umami is a lightweight open-source analytics tool that developers love: trivial to self-host, MIT-licensed, and its cloud has a genuinely free Hobby plan. The product covers pageviews, referrers, custom events, and basic reports, and stops there.
+
+- **Pricing:** Hobby cloud plan is free forever; Pro is $20/month for 1M events. 14-day trial on paid plans.
+- **Self-hosting:** free, and among the easiest to run (a small Node app + database).
+- **Limitations:** minimal reporting depth; small team behind it; most of its adoption is the free tier.
+
+See [Rybbit vs Umami](/compare/umami).
+
+## 6. PostHog
+
+**Best for: product engineering teams that want analytics, feature flags, A/B testing, and a data warehouse in one platform.**
+
+PostHog isn't primarily a GA replacement β€” it's a product-analytics platform that happens to include a web analytics dashboard. If you want feature flags, experiments, SQL access to raw events, and session replay in a single vendor, it's the strongest option, and its free tier is huge: 1M events every month, no card required.
+
+The flip side: PostHog is a lot. The pricing is per-product and usage-based (from $0.00005/event after the free tier), which is cheap at small scale and requires spreadsheet attention at large scale, and the interface has GA4-ish complexity because it's solving a bigger problem than web analytics.
+
+- **Pricing:** 1M events/month free, then usage-based; card only needed past the free tier.
+- **Self-hosting:** a hobby self-deploy exists; the real product is cloud.
+- **Limitations:** complexity and cookie/consent posture depend on how you configure it; web analytics is a side dish, not the meal.
+
+See [Rybbit vs PostHog](/compare/posthog).
+
+## 7. Simple Analytics
+
+**Best for: EU-based companies that want the most privacy-conservative option.**
+
+Amsterdam-based Simple Analytics is exactly what the name says, with a notable 2026 twist: it now positions itself as a *complement* that fixes the traffic GA4 misses, arguing GA can under-report by up to 60%. It's EU-hosted end to end, has a free tier for hobby sites, and an AI chat interface over your stats.
+
+- **Pricing:** free for hobby sites (1 user, 5 websites, 1 month of history); paid from $20/month with usage-based sliders. 14-day trial, no card.
+- **Self-hosting:** not offered.
+- **Limitations:** per-user pricing adds up for teams; short history on the free tier; simple by design.
+
+See [Rybbit vs Simple Analytics](/compare/simpleanalytics).
+
+## 8. Pirsch
+
+**Best for: the lowest-priced paid entry point in privacy analytics.**
+
+Pirsch is a German-built, cookieless analytics tool with developer-friendly touches (server-side tracking via SDKs is a first-class feature) and aggressive pricing: $6/month covers 10k pageviews across up to 50 websites with unlimited team members and unlimited retention. The $12/month Plus tier adds funnels and A/B testing. It also ships importers for GA, Plausible, and Fathom.
+
+- **Pricing:** from $6/month; 30-day trial, no card required.
+- **Self-hosting:** only on the paid Enterprise tier β€” the code isn't free OSS.
+- **Limitations:** smaller feature set than Rybbit or PostHog (no session replay or error tracking); self-hosting is gated.
+
+## 9. Cloudflare Web Analytics
+
+**Best for: a free rough signal when you can't justify any budget β€” not a GA replacement.**
+
+Cloudflare's free web analytics is cookieless and takes one minute to enable if you're already behind Cloudflare. But know what you're getting: per Cloudflare's own developer docs, dashboard stats are based on a ~10% sample of page-load events and retention is limited to 30 days. There are no custom events, goals, or funnels.
+
+- **Pricing:** free.
+- **Limitations:** sampled reporting, ~30-day retention, minimal features. Fine as a sanity check; unusable as your only analytics.
+
+## Which Google Analytics alternative should you pick?
+
+- **You want depth without the pain** β€” funnels, replay, errors, and a dashboard anyone can read: **[Rybbit](/pricing)**. That's the exact gap we built it for.
+- **You want the simplest possible stats page:** **Plausible**, **Fathom**, or **Pirsch** (cheapest), in roughly that order of polish.
+- **You want maximum features and don't mind the learning curve:** **PostHog** (modern, product-focused) or **Matomo** (mature, UA-like).
+- **You want free forever:** **Umami's** Hobby cloud tier, or self-host **Rybbit**, **Umami**, **Plausible CE**, or **Matomo** β€” all [genuinely free to run yourself](/docs/self-hosting).
+- **You want zero budget and zero setup:** **Cloudflare**, eyes open about sampling.
+
+## FAQ
+
+**Do I still need a cookie banner with these tools?**
+Not for the cookieless ones (Rybbit, Plausible, Fathom, Umami, Simple Analytics, Pirsch, Cloudflare) when used as designed β€” they don't set cookies or track individuals across sites. GA4 and full-configuration PostHog generally do require consent in the EU.
+
+**Can I import my Google Analytics history?**
+Effectively no β€” Google only exports GA4 data to BigQuery, and no alternative can rebuild its reports from that. The standard move is to run your new tool in parallel with GA4 for a few weeks, then archive the GA4 property. (Rybbit does [import data](/docs) from Plausible, Umami, and Simple Analytics if you're switching between alternatives.)
+
+**Is Google Analytics illegal in Europe?**
+It's not banned, but DPAs in Austria, France, and Italy ruled its EU–US data transfers unlawful under GDPR, and using it compliantly requires consent banners plus careful configuration. Cookieless alternatives remove most of that burden.
+
+**What's the best free Google Analytics alternative?**
+Self-hosting an open-source tool (Rybbit, Umami, Plausible CE, Matomo) gives you the most for free if you can run Docker. If you want free *cloud* hosting, Umami's Hobby plan and PostHog's 1M-events tier are the real ones; Cloudflare is free but sampled.
+
+---
+
+*Ready to see what GA4 has been hiding? [Start a free Rybbit trial](https://app.rybbit.io/signup) or explore the [live demo](https://demo.rybbit.com/81) β€” setup is one script tag and takes about five minutes.*
diff --git a/docs/content/blog/best-web-analytics-tools.mdx b/docs/content/blog/best-web-analytics-tools.mdx
new file mode 100644
index 000000000..b4b4e3cf5
--- /dev/null
+++ b/docs/content/blog/best-web-analytics-tools.mdx
@@ -0,0 +1,125 @@
+---
+title: "The 10 Best Web Analytics Tools in 2026, Compared by Use Case"
+description: "An honest guide to the best web analytics tools in 2026 β€” privacy-first trackers, product analytics suites, and free options β€” with verified pricing for each."
+date: 2026-07-19
+tags: ["analytics", "tools", "comparisons"]
+author: Rybbit Team
+---
+
+Every list of web analytics tools pretends there's one "best" answer. There isn't β€” a solo blogger checking referrers, a SaaS team debugging a signup funnel, and an EU retailer with a nervous legal department need genuinely different products.
+
+So this guide is organized around the question that actually decides the purchase: **what do you need your analytics to do?** We build one of these tools ([Rybbit](https://rybbit.com)), so we'll flag that bias where it matters β€” and every price and limit below comes from the vendor's own published pages, checked July 2026.
+
+## The short version
+
+| If you need... | Use | Price anchor |
+| --- | --- | --- |
+| Depth + simplicity in one tool | [Rybbit](#rybbit) | $19/mo, 100k events |
+| The simplest possible dashboard | [Plausible](#plausible), [Fathom](#fathom-analytics) | $9/mo Β· slider ($45 at 500k) |
+| The cheapest paid plan | [Pirsch](#pirsch) | $6/mo, 10k pageviews |
+| Full product-analytics suite | [PostHog](#posthog) | 1M events/mo free, then usage-based |
+| Free ads-ecosystem default | [Google Analytics 4](#google-analytics-4) | Free (GA360 β‰ˆ $50k/yr) |
+| Free forever, cloud-hosted | [Umami](#umami) | $0 Hobby plan |
+| Maximum features, self-hosted, free | [Matomo](#matomo) | Free on-premise; cloud €29/mo |
+| Strictest EU privacy posture | [Simple Analytics](#simple-analytics) | Free hobby tier; $20/mo paid |
+| Zero budget, zero setup | [Cloudflare](#cloudflare-web-analytics) | Free (sampled) |
+
+## How to choose a web analytics tool
+
+Four questions sort the whole market:
+
+1. **Traffic stats or behavior?** Counting visits, referrers, and top pages is the easy half. Understanding *behavior* β€” funnels, session replay, user journeys, errors β€” is where tools diverge sharply. Simple trackers stop at the first half.
+2. **Cookies or cookieless?** Cookie-based tools (GA4 chief among them) require consent banners in most of the world, and every declined banner is a visitor deleted from your data. Cookieless tools see everyone and need no banner.
+3. **Cloud or self-hosted?** If analytics data legally can't leave your infrastructure, your shortlist is the open-source tools: Rybbit, Matomo, Plausible CE, Umami.
+4. **Who reads the dashboard?** If the answer includes non-analysts, weight simplicity heavily. The most common analytics failure isn't missing data β€” it's a tool nobody opens.
+
+## Rybbit
+
+**The all-rounder: product-analytics depth on a dashboard anyone can read.**
+
+Most tools on this list force a choice between simple-but-shallow and deep-but-painful. [Rybbit](https://rybbit.com) exists to refuse that choice: a single-page, real-time dashboard in the Plausible tradition, with [funnels](/features/funnels), [session replay](/features/session-replay), [user journeys](/features/user-journeys), [error tracking](/features/error-tracking), [Web Vitals](/features/web-vitals), and user profiles built in β€” capabilities that otherwise require a PostHog-class suite. Tracking is cookieless (no consent banner, no lost visitors, no sampling), the whole platform is open source, and there's a [live demo with real data](https://demo.rybbit.com/81) you can click around right now.
+
+**Pricing:** from $19/month for 100k events β€” [all features on every plan](/pricing), 7-day trial. Self-hosting is [free with Docker](/docs/self-hosting).
+**Skip it if:** you need years of GA-style ad-attribution workflows, or feature flags and experiments in the same tool (that's PostHog territory).
+
+## Google Analytics 4
+
+**The default, and the tool everyone on this page is measured against.**
+
+GA4 is free, integrates natively with Google Ads, and exports raw events to BigQuery β€” for paid-acquisition teams inside Google's ecosystem, it remains genuinely hard to replace. It's on this list on merit.
+
+But treat its price with suspicion: "free" is funded by your visitors' data feeding Google's ad network. The operational costs are consent banners (and the 30–60% of traffic they cost you), report sampling on busy properties, 14-month standard retention, and an interface that has made "how do I just see my top pages?" a support-forum genre. Unsampled data means GA360, at roughly $50,000/year. If those are your pain points, our [detailed GA4 comparison](/compare/google-analytics) breaks down the switch β€” or see the full [guide to Google Analytics alternatives](/blog/best-google-analytics-alternatives).
+
+## Plausible
+
+**The standard-bearer for simple, privacy-first analytics.**
+
+One page of stats, a tiny script (their claim: ~54Γ— smaller than GA's), cookieless by design, EU-owned and EU-hosted. Plausible proved a paid GA alternative could be a real business, and a decade of polish shows. Its scope is deliberately narrow β€” traffic analytics, goals, basic funnels β€” which is either its best feature or its dealbreaker depending on your needs. **From $9/month** (10k pageviews), 30-day no-card trial, free self-hosted Community Edition. [Rybbit vs Plausible β†’](/compare/plausible)
+
+## Matomo
+
+**The open-source veteran with the largest feature list.**
+
+Heatmaps, A/B tests, a tag manager, hundreds of plugins, and a free on-premise edition with unlimited hits β€” Matomo (ex-Piwik) is what "we replaced Google Analytics" meant for a decade, and it's still the compliance-department favorite (cloud data lives in Frankfurt, no sampling). The cost is a dated interface and pricing complexity on-premise, where advanced features come in paid plugin bundles from €275. **Cloud from €29/month** for 50k hits; no-card trial. [Rybbit vs Matomo β†’](/compare/matomo)
+
+## PostHog
+
+**The product-analytics suite that swallowed web analytics.**
+
+PostHog bundles product analytics, session replay, feature flags, experiments, surveys, and a SQL-queryable event warehouse β€” with a web analytics dashboard on the side. For engineering-led product teams it's the most capable platform here, and the free tier is the market's most generous: **1M events every month, no card**. Past that it's usage-based (from $0.00005/event), which needs monitoring at scale. The trade: GA4-class complexity, because it's solving a much bigger problem than "how's my traffic." [Rybbit vs PostHog β†’](/compare/posthog)
+
+## Fathom Analytics
+
+**Simple stats from one of the original privacy-analytics companies.**
+
+Cookieless, one clean dashboard, forever data retention, and at least 50 sites on every plan. Fathom's pitch is stability β€” a profitable independent company that's been doing exactly this since before it was a category. Pricing is a pageview slider (**$45/month at 500k pageviews**; smaller tiers cost less), 7-day trial, no free tier, no self-hosting. [Rybbit vs Fathom β†’](/compare/fathom)
+
+## Umami
+
+**Free, minimal, MIT-licensed β€” the developer's hobby-project default.**
+
+Umami is the easiest analytics tool to self-host (a small Node app), and its cloud **Hobby plan is free forever**, with Pro at **$20/month for 1M events**. Reporting is deliberately minimal β€” pageviews, referrers, events β€” and that's the point. If your need is "decent stats on my side projects for $0," this is the answer. [Rybbit vs Umami β†’](/compare/umami)
+
+## Simple Analytics
+
+**The most privacy-conservative option, made and hosted in the EU.**
+
+Simple Analytics collects the least data of any paid tool here and wears it proudly. In 2026 it's also carved out a clever niche: positioning itself as the *fix* for GA4's consent-loss problem (their number: GA can miss up to 60% of traffic). **Free for hobby sites** (5 sites, 1 month history); paid from **$20/month per user** with usage sliders; 14-day no-card trial. No self-hosting. [Rybbit vs Simple Analytics β†’](/compare/simpleanalytics)
+
+## Pirsch
+
+**The lowest-cost paid entry in privacy analytics.**
+
+German-built, cookieless, with first-class server-side tracking SDKs and importers for GA, Plausible, and Fathom. **$6/month** buys 10k pageviews across up to 50 sites with unlimited team members and retention; $12/month adds funnels and A/B testing; 30-day no-card trial. Self-hosting exists but only behind the Enterprise tier. For tight budgets it's the best dollar-for-dollar deal on this list.
+
+## Cloudflare Web Analytics
+
+**Free and instant β€” as long as you understand what it isn't.**
+
+If your site is behind Cloudflare, this is one toggle. It's cookieless and costs nothing, but Cloudflare's own docs note the dashboard is built on a ~10% sample of page-load events with roughly 30-day retention, and there are no goals, events, or funnels. Use it as a free second opinion, not as your analytics.
+
+## What we'd actually do
+
+- **Under 10k visits/month, $0 budget:** Umami's free cloud tier, or self-host if you enjoy it.
+- **A business site where decisions ride on the data:** [Rybbit](/pricing) β€” you'll use the funnels and replay within the first week, and cookieless tracking means the numbers are actually complete.
+- **A content site that just needs clean traffic stats:** Plausible or Fathom; Pirsch if price wins.
+- **An engineering-led product team:** PostHog, or Rybbit if you want your PMs and marketers to actually open the dashboard.
+- **Regulated/self-host-only environment:** Rybbit or Matomo, both [free to run on your own infrastructure](/docs/self-hosting).
+
+## FAQ
+
+**What's the difference between web analytics and product analytics?**
+Web analytics answers traffic questions (visitors, sources, pages); product analytics answers behavior questions (activation, retention, funnels) usually tied to identified users. GA4 and PostHog are product-analytics tools wearing web-analytics clothes; Plausible and Fathom are pure web analytics; Rybbit deliberately covers both sides for websites and apps.
+
+**Are free web analytics tools good enough?**
+Often, yes β€” Umami and PostHog's free tiers are real products, and self-hosting an open-source tool costs only your server. The free options to be wary of are the ones with invisible costs: GA4 (consent loss, complexity, your users' data) and Cloudflare (sampling, 30-day window).
+
+**Can I run two analytics tools at once?**
+Yes, and during any migration you should. Scripts from different vendors don't conflict, and a few weeks of parallel data is the only honest way to compare them. It's also the standard way to [leave Google Analytics](/blog/best-google-analytics-alternatives) without losing your bearings.
+
+**Do cookieless analytics tools comply with GDPR?**
+The cookieless tools here (Rybbit, Plausible, Fathom, Umami, Simple Analytics, Pirsch) are built to run without consent banners β€” no cookies, no cross-site identifiers, no personal profiles. Self-hosting adds the strongest guarantee, since data never touches a third party at all.
+
+---
+
+*Want the deep version of any matchup? Every comparison above links to a feature-by-feature breakdown β€” or start with [Rybbit vs Google Analytics](/compare/google-analytics), the switch most teams are weighing.*
diff --git a/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/comparison-data.tsx
index c6ee39acd..8fdbd8ab2 100644
--- a/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const cloudflareAnalyticsComparisonData: ComparisonSection[] = [
{
@@ -96,6 +97,82 @@ export const cloudflareAnalyticsExtendedData = {
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Cloudflare Analytics vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "What β€œfree” costs you here",
+ paragraphs: [
+ <>
+ Cloudflare Web Analytics is genuinely free, and it&apos;s honest about how it manages that. Per
+ Cloudflare&apos;s developer docs, the dashboard is built on a roughly 10% sample of page-load events:
+ unsampled data is kept for about seven days before being aggregated, and retention is limited to around 30
+ days, even though the UI exposes date ranges up to six months. For a high-traffic site a 10% sample still
+ traces the broad shape of things. For a small or medium site it means noisy, incomplete numbers &mdash; a
+ page that got 40 visits yesterday might show 20 or 70, and thin segments like a single campaign or country
+ can disappear entirely.
+ </>,
+ <>
+ The retention window is the quieter limitation. With unsampled data measured in days and aggregates in
+ weeks, there is no year-over-year comparison, no &ldquo;how did this launch compare to the last one,&rdquo;
+ and no long baseline to judge a slow trend against. Rybbit stores every event unsampled at any traffic
+ level, so the number on the dashboard is the number that happened &mdash; this month and long after.
+ </>,
+ ],
+ },
+ {
+ heading: "A signal vs something you can act on",
+ paragraphs: [
+ <>
+ The deeper difference isn&apos;t accuracy, it&apos;s the kind of question each tool can answer. Cloudflare
+ Web Analytics answers &ldquo;is traffic roughly up or down?&rdquo; &mdash; and for that, it&apos;s fine.
+ But it has no custom events, no goals, and no funnels, so it can&apos;t tell you whether visitors signed
+ up, where they dropped out of checkout, or which campaign actually converted.
+ </>,
+ <>
+ Rybbit is built for the follow-up question: &ldquo;what should we change?&rdquo; Custom events with
+ attributes and conversion goals tell you what visitors did;{" "}
+ <Link href="/features/funnels">funnels</Link> and user journeys show where they stalled; session replay and
+ error tracking show why; <Link href="/features/web-vitals">Web Vitals monitoring</Link> and user profiles
+ round out the picture. All of it ships on every plan, from a ~18KB script that stays cookieless with a
+ daily-rotating salt &mdash; so you keep the privacy posture that likely drew you to Cloudflare in the first
+ place.
+ </>,
+ ],
+ },
+ {
+ heading: "The actually-free alternative",
+ paragraphs: [
+ <>
+ If free is the requirement rather than a nice-to-have, the honest comparison point isn&apos;t
+ Rybbit&apos;s cloud plans &mdash; it&apos;s{" "}
+ <Link href="/docs/self-hosting">self-hosting the open-source version</Link>. Rybbit&apos;s code is open
+ source and self-hosting costs $0 in licenses: you pay only for your own server, and you get unsampled
+ data, full retention under your control, and the complete feature set, with events never leaving your
+ infrastructure. If you&apos;d rather not run it yourself, cloud{" "}
+ <Link href="/pricing">starts at $19/mo for 100k events</Link> with a 7-day trial and every feature on
+ every plan.
+ </>,
+ ],
+ },
+ {
+ heading: "When Cloudflare Analytics is enough",
+ paragraphs: [
+ <>
+ Plenty of sites don&apos;t need more than a pulse, and Cloudflare Web Analytics is a good pulse. It fits
+ when the budget is zero and self-hosting isn&apos;t on the table, when your tolerance for setup is a
+ single copy-pasted beacon (or none at all, if your DNS is already proxied through Cloudflare), and when a
+ rough sense of traffic direction is all anyone will ever ask of it. It also runs happily alongside any
+ other analytics tool, so there&apos;s no cost to keeping it while you evaluate something deeper. If
+ you&apos;re weighing more options, our{" "}
+ <Link href="/blog/best-web-analytics-tools">guide to the best web analytics tools</Link> covers the wider
+ field.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "Why is Cloudflare Analytics data inaccurate?",
diff --git a/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/page.tsx b/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/page.tsx
index 1ceecaeae..cdc13229e 100644
--- a/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/cloudflare-analytics/page.tsx
@@ -102,6 +102,7 @@ export default function CloudflareAnalytics() {
chooseCompetitor={cloudflareAnalyticsExtendedData.chooseCompetitor}
rybbitPricing={cloudflareAnalyticsExtendedData.rybbitPricing}
competitorPricing={cloudflareAnalyticsExtendedData.competitorPricing}
+ deepDive={cloudflareAnalyticsExtendedData.deepDive}
faqItems={cloudflareAnalyticsExtendedData.faqItems}
relatedResources={cloudflareAnalyticsExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/components/ComparisonPage.tsx b/docs/src/app/[locale]/(home)/compare/components/ComparisonPage.tsx
index 37aa18046..5a8f7b2fb 100644
--- a/docs/src/app/[locale]/(home)/compare/components/ComparisonPage.tsx
+++ b/docs/src/app/[locale]/(home)/compare/components/ComparisonPage.tsx
@@ -41,6 +41,16 @@ export interface RelatedResource {
description: string;
}
+export interface DeepDiveSection {
+ heading: string;
+ paragraphs: React.ReactNode[];
+}
+
+export interface DeepDive {
+ title: string;
+ sections: DeepDiveSection[];
+}
+
export interface ComparisonPageProps {
competitorName: string;
sections: ComparisonSection[];
@@ -52,6 +62,7 @@ export interface ComparisonPageProps {
chooseCompetitor?: string[];
rybbitPricing?: PricingInfo;
competitorPricing?: PricingInfo;
+ deepDive?: DeepDive;
faqItems?: FAQItem[];
relatedResources?: RelatedResource[];
}
@@ -67,6 +78,7 @@ export function ComparisonPage({
chooseCompetitor,
rybbitPricing,
competitorPricing,
+ deepDive,
faqItems,
relatedResources,
}: ComparisonPageProps) {
@@ -244,6 +256,40 @@ export function ComparisonPage({
</section>
)}
+ {deepDive && (
+ <section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="deep-dive-title">
+ <div className="mx-auto grid max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800 lg:grid-cols-12">
+ <div className="border-b border-neutral-200 px-5 py-12 dark:border-neutral-800 sm:px-8 lg:col-span-4 lg:border-b-0 lg:border-r lg:px-10 lg:py-16">
+ <div className="lg:sticky lg:top-24">
+ <h2 id="deep-dive-title" className="text-3xl font-semibold tracking-[-0.03em] md:text-4xl">
+ {deepDive.title}
+ </h2>
+ </div>
+ </div>
+ <div className="lg:col-span-8">
+ {deepDive.sections.map((section) => (
+ <div
+ key={section.heading}
+ className="border-b border-neutral-200 px-5 py-10 last:border-b-0 dark:border-neutral-800 sm:px-8 lg:px-10"
+ >
+ <h3 className="text-xl font-semibold tracking-[-0.02em]">{section.heading}</h3>
+ <div className="mt-5 space-y-4">
+ {section.paragraphs.map((paragraph, paragraphIndex) => (
+ <div
+ key={paragraphIndex}
+ className="max-w-3xl text-base leading-7 text-neutral-600 dark:text-neutral-300 [&_a]:font-medium [&_a]:text-emerald-600 [&_a]:underline [&_a]:underline-offset-4 dark:[&_a]:text-emerald-400 [&_ul]:list-disc [&_ul]:space-y-2 [&_ul]:pl-5 [&_ol]:list-decimal [&_ol]:space-y-2 [&_ol]:pl-5"
+ >
+ {paragraph}
+ </div>
+ ))}
+ </div>
+ </div>
+ ))}
+ </div>
+ </div>
+ </section>
+ )}
+
{!hasNewSections && comparisonContent && (
<section className="border-b border-neutral-200 dark:border-neutral-800">
<div className="mx-auto max-w-[1200px] border-x border-neutral-200 px-5 py-12 dark:border-neutral-800 sm:px-8 lg:px-10 lg:py-16">
diff --git a/docs/src/app/[locale]/(home)/compare/fathom/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/fathom/comparison-data.tsx
index 7ce241f71..ed1a5baea 100644
--- a/docs/src/app/[locale]/(home)/compare/fathom/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/fathom/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const fathomComparisonData: ComparisonSection[] = [
{
@@ -95,6 +96,98 @@ export const fathomExtendedData = {
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Fathom vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "Two privacy-first tools, two philosophies",
+ paragraphs: [
+ <>
+ Fathom deserves real credit: it&apos;s one of the founders of the privacy-analytics category, and it has
+ run as a profitable, independent company for years while bigger players came and went. If you&apos;re
+ leaving Google Analytics for something cookieless and simple, Fathom is a legitimate destination &mdash;
+ we&apos;ve said as much in our roundup of{" "}
+ <Link href="/blog/best-google-analytics-alternatives">the best Google Analytics alternatives</Link>.
+ </>,
+ <>
+ The two products just make different bets. Fathom bets that most site owners want one clean page of
+ traffic numbers from the most stable, boring vendor possible &mdash; and deliberately stops there. Rybbit
+ starts from the same privacy foundation (cookieless tracking, no personal data, visitor hashes rotated
+ daily) but bets that once you see the numbers move, you&apos;ll want to know <em>why</em>. Which bet is
+ right depends on you, not on either product being wrong.
+ </>,
+ ],
+ },
+ {
+ heading: "Deliberate simplicity vs. behavioral depth",
+ paragraphs: [
+ <>
+ Fathom&apos;s simplicity is a feature, not a gap &mdash; pageviews, referrers, UTM tracking, and
+ conversion goals on a single screen, with a tracking script around 2KB. If that&apos;s the whole job,
+ Fathom does it very well.
+ </>,
+ <>
+ Rybbit covers the same dashboard basics, then adds the layer Fathom deliberately leaves out:{" "}
+ <Link href="/features/session-replay">session replay</Link> to watch real sessions, funnels to find where
+ signups stall, user journey (Sankey) visualization, <Link href="/features/error-tracking">error
+ tracking</Link>, Web Vitals monitoring, and user profiles. Rybbit&apos;s script is bigger (~18KB) because
+ it does more &mdash; that&apos;s the honest trade. There&apos;s also an ownership difference with no
+ trade-off attached: Rybbit is open source and can be{" "}
+ <Link href="/docs/self-hosting">self-hosted for free</Link>, while Fathom is closed-source and SaaS-only
+ &mdash; there is no way to run it on your own infrastructure.
+ </>,
+ ],
+ },
+ {
+ heading: "Pricing shape: a pageview slider vs. events with everything included",
+ paragraphs: [
+ <>
+ Fathom prices on a pageview slider: you pick a monthly pageview tier and pay more as traffic grows &mdash;
+ at 500k pageviews it&apos;s $45/month. There&apos;s a 7-day trial but explicitly no free tier
+ (&ldquo;Do you have a lower/free option? Nope&rdquo; is a real answer on their FAQ). The generous parts are
+ real, too: every plan includes at least 50 sites (extra sites are $10/month per 50), data is retained
+ forever, and paying annually gets you two months free. For an agency running dozens of low-traffic sites,
+ that 50-site allowance is genuinely hard to beat.
+ </>,
+ <>
+ Rybbit prices on events instead, starting at{" "}
+ <Link href="/pricing">$19/month for 100k events</Link> with a 7-day trial &mdash; and every feature,
+ including session replay, funnels, and error tracking, is on every plan, so you never move up a tier to
+ unlock a capability. And if the subscription ever stops making sense, the open-source version is a real
+ exit: self-host it and pay nothing. Fathom, being closed-source, can&apos;t offer that pressure valve.
+ </>,
+ ],
+ },
+ {
+ heading: "Switching from Fathom to Rybbit",
+ paragraphs: [
+ <>
+ Rybbit&apos;s historical-data importers currently cover Plausible, Umami, and Simple Analytics &mdash;
+ there is no Fathom importer yet. So the switch is the classic parallel run:
+ </>,
+ <ol>
+ <li>
+ Add the Rybbit <Link href="/docs/script">tracking script</Link> alongside Fathom&apos;s &mdash; the two
+ don&apos;t conflict, and data appears in minutes.
+ </li>
+ <li>
+ Recreate your Fathom events and conversions as Rybbit <Link href="/docs/goals">goals</Link> and{" "}
+ <Link href="/docs/track-events">custom events</Link>.
+ </li>
+ <li>
+ Compare a few weeks of numbers. Since both tools are cookieless and resistant to ad blockers, expect
+ them to track closely &mdash; this is mostly a sanity check, not a reconciliation project.
+ </li>
+ <li>
+ Remove the Fathom script when you&apos;re confident. Your history stays in your Fathom account for
+ reference as long as you keep it.
+ </li>
+ </ol>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "Is Rybbit open source while Fathom is not?",
diff --git a/docs/src/app/[locale]/(home)/compare/fathom/page.tsx b/docs/src/app/[locale]/(home)/compare/fathom/page.tsx
index a4f5e3af1..f59abb89a 100644
--- a/docs/src/app/[locale]/(home)/compare/fathom/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/fathom/page.tsx
@@ -102,6 +102,7 @@ export default function Fathom() {
chooseCompetitor={fathomExtendedData.chooseCompetitor}
rybbitPricing={fathomExtendedData.rybbitPricing}
competitorPricing={fathomExtendedData.competitorPricing}
+ deepDive={fathomExtendedData.deepDive}
faqItems={fathomExtendedData.faqItems}
relatedResources={fathomExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/google-analytics/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/google-analytics/comparison-data.tsx
index 4ed32f92f..413738a0a 100644
--- a/docs/src/app/[locale]/(home)/compare/google-analytics/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/google-analytics/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const googleAnalyticsComparisonData: ComparisonSection[] = [
{
@@ -96,6 +97,92 @@ export const googleAnalyticsExtendedData = {
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Google Analytics vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "What β€œfree” actually costs you",
+ paragraphs: [
+ <>
+ GA4 is free because your visitors&apos; data feeds Google&apos;s advertising business. The practical costs
+ show up elsewhere. Because GA4 relies on cookies, GDPR and ePrivacy require a consent banner in most of the
+ world &mdash; and a large share of visitors decline or ignore it, so the sessions they represent never reach
+ your reports. Teams switching to cookieless analytics routinely discover their real traffic is 30&ndash;60%
+ higher than GA4 showed.
+ </>,
+ <>
+ On top of consent loss, GA4 applies sampling to complex reports on busy properties, holds standard-property
+ event data for at most 14 months, and locks unsampled exploration behind GA360 &mdash; which starts around
+ $50,000 per year. Rybbit&apos;s <Link href="/pricing">pricing</Link> is a flat, events-based subscription:
+ every feature on every plan, no sampling at any traffic level, and your data is never used for anything
+ except showing you your analytics.
+ </>,
+ ],
+ },
+ {
+ heading: "Feature depth is closer than you'd think",
+ paragraphs: [
+ <>
+ The common objection to leaving Google Analytics is losing capability. In 2026 the gap mostly runs the
+ other way for product and marketing teams: Rybbit ships{" "}
+ <Link href="/features/session-replay">session replay</Link>, <Link href="/features/funnels">funnels</Link>,{" "}
+ <Link href="/features/user-journeys">user journey (Sankey) visualization</Link>,{" "}
+ <Link href="/features/error-tracking">error tracking</Link>, and{" "}
+ <Link href="/features/web-vitals">Web Vitals monitoring</Link> as part of the core product. GA4 offers none
+ of these; Google&apos;s answer to replay and heatmaps has always been third-party tools.
+ </>,
+ <>
+ What GA4 genuinely does better is the Google ecosystem: bidirectional Google Ads integration, BigQuery
+ export, and advanced attribution modeling for paid campaigns. If your team lives in Google Ads, keeping GA4
+ for ad attribution while running Rybbit as your source of truth for real traffic is a reasonable setup
+ &mdash; the two scripts don&apos;t conflict.
+ </>,
+ ],
+ },
+ {
+ heading: "How to switch from Google Analytics to Rybbit",
+ paragraphs: [
+ <>
+ There is no historical-data import from GA4 (Google&apos;s export goes to BigQuery, not to other analytics
+ tools), so the standard path is to run both in parallel:
+ </>,
+ <ol>
+ <li>
+ Add the Rybbit <Link href="/docs/script">tracking script</Link> &mdash; one tag, and data appears in
+ minutes. Keep GA4 running alongside it.
+ </li>
+ <li>
+ Recreate your conversions as Rybbit <Link href="/docs/goals">goals</Link> and{" "}
+ <Link href="/docs/track-events">custom events</Link>. Most teams find they need far fewer events than
+ GA4&apos;s model pushed them into.
+ </li>
+ <li>
+ Compare a few weeks of numbers. Expect Rybbit to report noticeably more traffic &mdash; that&apos;s the
+ consent-banner and ad-blocker loss GA4 never showed you.
+ </li>
+ <li>
+ If you need the history, export your GA4 property to BigQuery for archival before Google&apos;s retention
+ window trims it. Then remove the GA tag &mdash; and the cookie banner with it.
+ </li>
+ </ol>,
+ ],
+ },
+ {
+ heading: "The compliance angle",
+ paragraphs: [
+ <>
+ Multiple EU data-protection authorities (Austria, France, and Italy among them) have ruled that Google
+ Analytics transfers violated GDPR, and enforcement keeps tightening. Rybbit sidesteps the whole category of
+ risk: no cookies, no persistent identifiers, no personal data collection, with visitor hashes rotated
+ daily. You can run it with no consent banner at all &mdash; or go further and{" "}
+ <Link href="/docs/self-hosting">self-host the open-source version</Link> so analytics data never leaves
+ your own infrastructure.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "Is it hard to migrate from Google Analytics to Rybbit?",
@@ -120,6 +207,11 @@ export const googleAnalyticsExtendedData = {
] satisfies FAQItem[],
relatedResources: [
+ {
+ title: "The 9 Best Google Analytics Alternatives in 2026",
+ href: "/blog/best-google-analytics-alternatives",
+ description: "How Rybbit and 8 other GA4 alternatives compare on pricing, privacy, and features",
+ },
{
title: "Rybbit vs Plausible",
href: "/compare/plausible",
diff --git a/docs/src/app/[locale]/(home)/compare/google-analytics/page.tsx b/docs/src/app/[locale]/(home)/compare/google-analytics/page.tsx
index 5a5ce636e..390cc0475 100644
--- a/docs/src/app/[locale]/(home)/compare/google-analytics/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/google-analytics/page.tsx
@@ -103,6 +103,7 @@ export default function GoogleAnalytics() {
chooseCompetitor={googleAnalyticsExtendedData.chooseCompetitor}
rybbitPricing={googleAnalyticsExtendedData.rybbitPricing}
competitorPricing={googleAnalyticsExtendedData.competitorPricing}
+ deepDive={googleAnalyticsExtendedData.deepDive}
faqItems={googleAnalyticsExtendedData.faqItems}
relatedResources={googleAnalyticsExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/matomo/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/matomo/comparison-data.tsx
index bb9dbb5c1..8ced399fa 100644
--- a/docs/src/app/[locale]/(home)/compare/matomo/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/matomo/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const matomoComparisonData: ComparisonSection[] = [
{
@@ -40,7 +41,7 @@ export const matomoComparisonData: ComparisonSection[] = [
{ name: "Script size", rybbitValue: "18KB", competitorValue: "20-50KB" },
{ name: "Bypasses ad blockers", rybbitValue: true, competitorValue: false },
{ name: "API access", rybbitValue: true, competitorValue: true },
- { name: "Starting price", rybbitValue: "$19/mo", competitorValue: "\u20AC19/mo" },
+ { name: "Starting price", rybbitValue: "$19/mo", competitorValue: "\u20AC29/mo (50k hits)" },
],
},
];
@@ -52,7 +53,7 @@ export const matomoExtendedData = {
introParagraphs: [
"Matomo (formerly Piwik) has been around since 2007 and positions itself as the open-source Google Analytics alternative. It's feature-rich with 70+ reports, heatmaps, A/B testing, and form analytics. But that breadth comes with Google Analytics-level complexity, and most teams need training just to find the metrics they care about, and the PHP/MySQL stack feels increasingly dated.",
"Rybbit is built the way a modern analytics tool should be. A single-page dashboard shows all essential metrics on one screen, with no training required. Privacy works by default: no cookies, no consent banners, no configuration needed. The stack (TypeScript, ClickHouse) is built for performance, and the managed cloud option means zero server maintenance. You get session replay, user journeys, Web Vitals, and error tracking without installing plugins.",
- "Matomo's cloud pricing starts at €19/month for just 50k hits, and many useful features require paid plugins on top of that. Rybbit starts at $19/month with all features included. If you're tired of Matomo's complexity, maintenance burden, or plugin costs, Rybbit is a much simpler path to the analytics your team actually needs.",
+ "Matomo's cloud pricing starts at €29/month for just 50k hits, and many useful features require paid plugins on top of that. Rybbit starts at $19/month with all features included. If you're tired of Matomo's complexity, maintenance burden, or plugin costs, Rybbit is a much simpler path to the analytics your team actually needs.",
],
chooseRybbit: [
@@ -86,8 +87,8 @@ export const matomoExtendedData = {
competitorPricing: {
name: "Matomo Cloud",
- model: "Pageview-based pricing",
- startingPrice: "\u20AC19/mo",
+ model: "Hit-based pricing",
+ startingPrice: "\u20AC29/mo",
highlights: [
"Starts at 50k hits/month",
"On-Premise edition available for free (self-host)",
@@ -96,6 +97,93 @@ export const matomoExtendedData = {
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Matomo vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "Two decades of analytics, and it shows",
+ paragraphs: [
+ <>
+ Matomo deserves respect. Launched as Piwik nearly two decades ago, it proved that self-hosted, open-source
+ analytics could be a real Google Analytics alternative, and today it has the largest feature surface in the
+ category: heatmaps, A/B testing, a tag manager, and hundreds of plugins. It&apos;s the tool compliance
+ departments already know, with no data sampling, EU hosting in Frankfurt, 24 months of raw data retention
+ on cloud, and report data kept forever. If your requirement is the broadest possible self-hosted suite with
+ the longest audit trail, Matomo is a defensible default.
+ </>,
+ <>
+ But two decades of accretion show up in the product. Matomo&apos;s interface spreads dozens of report types
+ across many sections, and its architecture predates the tooling that makes modern analytics fast and
+ pleasant. Rybbit is what this category looks like when it&apos;s designed in the 2020s: a single-page
+ dashboard, an ~18KB script, and <Link href="/features/funnels">funnels</Link>,{" "}
+ <Link href="/features/session-replay">session replay</Link>, user journeys, error tracking, Web Vitals, and
+ user profiles built into the core product rather than bolted on over the years.
+ </>,
+ ],
+ },
+ {
+ heading: "β€œFree self-hosting” and the plugin-bundle math",
+ paragraphs: [
+ <>
+ Matomo&apos;s On-Premise Community Edition is genuinely free forever, with unlimited users and hits &mdash;
+ a real point in its favor. The catch is what happens when you want the advanced features. On self-hosted
+ Matomo, those come as paid plugin bundles: the Team bundle starts at &euro;275 for 4 users and 5M hits per
+ month, Business runs &euro;1,450, and Enterprise &euro;3,400. &ldquo;Free&rdquo; quietly becomes a
+ line-item negotiation over which capabilities your deployment is licensed for.
+ </>,
+ <>
+ Rybbit&apos;s model is simpler on both sides. <Link href="/docs/self-hosting">Self-hosting</Link> is free,
+ open source, deploys with Docker, and includes every feature &mdash; there are no plugin bundles to buy.
+ Cloud <Link href="/pricing">pricing</Link> starts at $19/month for 100k events with all features on every
+ plan and a 7-day trial. Matomo Cloud scales through hit-based tiers from 50k up past 10M (contact sales
+ above that), with Business-tier caps of 30 websites, 30 team members, and 100 segments.
+ </>,
+ ],
+ },
+ {
+ heading: "Cookieless by design vs cookieless by configuration",
+ paragraphs: [
+ <>
+ Matomo can run without cookies &mdash; it&apos;s a supported configuration, and the company takes privacy
+ seriously. But it&apos;s a configuration, not the default posture, and many real-world Matomo deployments
+ (especially older ones) still set cookies and still ship a consent flow. Rybbit doesn&apos;t have a
+ cookie mode to turn off: it&apos;s cookieless only, identifying visitors with a salted hash whose salt
+ rotates daily, so there&apos;s no persistent identifier to consent to in the first place. That difference
+ matters less for the compliance paperwork and more for the data: no consent banner means no consent-decline
+ gap in your numbers.
+ </>,
+ ],
+ },
+ {
+ heading: "Switching from Matomo to Rybbit",
+ paragraphs: [
+ <>
+ Rybbit doesn&apos;t currently import Matomo data (its importers cover Plausible, Umami, and Simple
+ Analytics), so the practical path is to run both in parallel:
+ </>,
+ <ol>
+ <li>
+ Add the Rybbit tracking script alongside your existing Matomo tag &mdash; the two don&apos;t conflict,
+ and data appears in minutes.
+ </li>
+ <li>
+ Recreate your Matomo goals and key events in Rybbit, and compare a few weeks of numbers side by side.
+ </li>
+ <li>
+ When you&apos;re confident, remove the Matomo tag &mdash; but keep your Matomo instance (or a database
+ archive) queryable rather than deleting it, so historical reports stay available.
+ </li>
+ </ol>,
+ <>
+ If you&apos;re evaluating the wider field before deciding, our rundown of the{" "}
+ <Link href="/blog/best-google-analytics-alternatives">best Google Analytics alternatives</Link> covers how
+ Matomo, Rybbit, and the rest of the category compare.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "Is Rybbit really simpler than Matomo?",
diff --git a/docs/src/app/[locale]/(home)/compare/matomo/page.tsx b/docs/src/app/[locale]/(home)/compare/matomo/page.tsx
index 85e105ba6..fe05cdd84 100644
--- a/docs/src/app/[locale]/(home)/compare/matomo/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/matomo/page.tsx
@@ -102,6 +102,7 @@ export default function Matomo() {
chooseCompetitor={matomoExtendedData.chooseCompetitor}
rybbitPricing={matomoExtendedData.rybbitPricing}
competitorPricing={matomoExtendedData.competitorPricing}
+ deepDive={matomoExtendedData.deepDive}
faqItems={matomoExtendedData.faqItems}
relatedResources={matomoExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/plausible/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/plausible/comparison-data.tsx
index 9ca504356..6d6e19948 100644
--- a/docs/src/app/[locale]/(home)/compare/plausible/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/plausible/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const plausibleComparisonData: ComparisonSection[] = [
{
@@ -6,7 +7,7 @@ export const plausibleComparisonData: ComparisonSection[] = [
features: [
{ name: "Real-time analytics", rybbitValue: true, competitorValue: true },
{ name: "Custom events", rybbitValue: "With attributes", competitorValue: "Basic" },
- { name: "Funnels", rybbitValue: true, competitorValue: false },
+ { name: "Funnels", rybbitValue: "All plans", competitorValue: "Business plan only" },
{ name: "User journeys (Sankey)", rybbitValue: true, competitorValue: false },
{ name: "Conversion goals", rybbitValue: true, competitorValue: true },
{ name: "UTM tracking", rybbitValue: true, competitorValue: true },
@@ -96,6 +97,92 @@ export const plausibleExtendedData = {
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Plausible vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "Two philosophies of privacy-first analytics",
+ paragraphs: [
+ <>
+ Plausible deserves real credit here: it pioneered the modern privacy-first analytics category and proved
+ that teams would pay for cookieless traffic stats instead of tolerating Google Analytics. Its scope is
+ deliberately minimal &mdash; a clean dashboard of pageviews, sources, and goals, with no session replay, no
+ error tracking, and no user profiles. That restraint is a feature, not an oversight; Plausible has never
+ pretended to be a product-analytics tool.
+ </>,
+ <>
+ Rybbit starts from the same privacy foundation &mdash; cookieless tracking with a daily-rotating salt, open
+ source, free to <Link href="/docs/self-hosting">self-host</Link> &mdash; but takes the opposite position on
+ scope. It ships <Link href="/features/session-replay">session replay</Link>,{" "}
+ <Link href="/features/funnels">funnels</Link>,{" "}
+ <Link href="/features/user-journeys">user journeys</Link>, error tracking, Web Vitals, and user profiles as
+ part of the core product. The honest framing: Plausible tells you how much traffic you got and where it
+ came from; Rybbit also shows you what visitors did once they arrived, where they dropped off, and what
+ broke.
+ </>,
+ ],
+ },
+ {
+ heading: "Pageviews with per-site caps vs events with everything included",
+ paragraphs: [
+ <>
+ Plausible prices by monthly pageviews, with plan tiers gating sites and seats: Starter is $9/month for 10k
+ pageviews and a single site, Growth is $14/month for 3 sites and 3 team members, and Business is $19/month
+ for 10 sites and 10 members, with 2 months free if you pay annually. It&apos;s cheap to start, but growing
+ past a site or seat cap means a plan change even if your traffic hasn&apos;t moved.
+ </>,
+ <>
+ Rybbit prices by events &mdash; from $19/month for 100k events &mdash; and every plan includes every
+ feature, with session replay available on Pro. There are no per-site or per-seat tiers to outgrow; you pay
+ for volume, not for unlocks. At low traffic Plausible is the cheaper bill; once you&apos;d otherwise be
+ paying for replay, funnels, and error tracking as separate tools, the math flips. Full details are on the{" "}
+ <Link href="/pricing">pricing page</Link>. And both products keep an honest exit: Plausible&apos;s
+ Community Edition and Rybbit&apos;s open-source version are each free to self-host.
+ </>,
+ ],
+ },
+ {
+ heading: "Switching from Plausible to Rybbit",
+ paragraphs: [
+ <>
+ This is one migration where you don&apos;t start from zero: Rybbit has a built-in data importer for
+ Plausible, so your historical traffic comes with you instead of living in an old dashboard forever.
+ </>,
+ <ol>
+ <li>
+ Add the Rybbit tracking script alongside Plausible&apos;s &mdash; both are lightweight, and running them
+ in parallel for a while costs nothing but a few kilobytes.
+ </li>
+ <li>
+ Import your Plausible history with the <Link href="/docs">data importer</Link>, so year-over-year
+ comparisons keep working from day one.
+ </li>
+ <li>Recreate your goals as Rybbit goals and custom events; the setup is similarly simple.</li>
+ <li>
+ Compare a few weeks of live numbers &mdash; they should track closely, since both tools are cookieless
+ &mdash; then remove the Plausible script.
+ </li>
+ </ol>,
+ ],
+ },
+ {
+ heading: "When Plausible is the better choice",
+ paragraphs: [
+ <>
+ If a traffic dashboard is genuinely all you want, Plausible is an excellent one &mdash; arguably the best
+ at being exactly that. It has the longest track record in the category, an EU-owned and EU-hosted cloud, a
+ famously tiny script (Plausible advertises it as 54&times; smaller than Google Analytics; Rybbit&apos;s is
+ around 18KB), and a 30-day trial with no card required versus Rybbit&apos;s 7 days. Choosing it means
+ deliberately not having session replay, funnels, or error tracking &mdash; and for plenty of content sites
+ and blogs, that&apos;s the right call. If you&apos;re weighing more options than these two, our roundup of
+ the <Link href="/blog/best-google-analytics-alternatives">best Google Analytics alternatives</Link> covers
+ the wider field.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "How is Rybbit different from Plausible?",
diff --git a/docs/src/app/[locale]/(home)/compare/plausible/page.tsx b/docs/src/app/[locale]/(home)/compare/plausible/page.tsx
index 8596e8857..e9817b86e 100644
--- a/docs/src/app/[locale]/(home)/compare/plausible/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/plausible/page.tsx
@@ -102,6 +102,7 @@ export default function Plausible() {
chooseCompetitor={plausibleExtendedData.chooseCompetitor}
rybbitPricing={plausibleExtendedData.rybbitPricing}
competitorPricing={plausibleExtendedData.competitorPricing}
+ deepDive={plausibleExtendedData.deepDive}
faqItems={plausibleExtendedData.faqItems}
relatedResources={plausibleExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/posthog/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/posthog/comparison-data.tsx
index 11ed7c647..17546909b 100644
--- a/docs/src/app/[locale]/(home)/compare/posthog/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/posthog/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const posthogComparisonData: ComparisonSection[] = [
{
@@ -97,6 +98,80 @@ export const posthogExtendedData = {
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "PostHog vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "Two different products in the same category",
+ paragraphs: [
+ <>
+ Let&apos;s be clear: PostHog is genuinely excellent at what it does. It isn&apos;t really an analytics tool
+ &mdash; it&apos;s a full product platform: product analytics, session replay, feature flags, experiments,
+ surveys, and a SQL-queryable event warehouse, with 2026&apos;s headline push being agentic AI that works
+ toward &ldquo;self-driving&rdquo; product decisions. For an engineering-led product team that wants all of
+ that in one place, it&apos;s one of the best tools on the market.
+ </>,
+ <>
+ The cost of that breadth is complexity in the same class as GA4: insights, query builders, a SQL layer, and
+ a lot of menus between you and &ldquo;how much traffic did we get this week?&rdquo; Rybbit makes the
+ opposite bet &mdash; web analytics your whole team actually opens. One dashboard covers traffic,{" "}
+ <Link href="/features/funnels">funnels</Link>,{" "}
+ <Link href="/features/session-replay">session replay</Link>, user journeys, error tracking, Web Vitals, and
+ user profiles, from an ~18KB script, with nothing to configure and no query language to learn.
+ </>,
+ ],
+ },
+ {
+ heading: "Flat subscription vs per-event metering",
+ paragraphs: [
+ <>
+ PostHog&apos;s free tier is genuinely huge: 1 million events per month, no card required, one project, one
+ year of data retention, unlimited team members &mdash; and the free allowance keeps applying after you
+ upgrade. If you&apos;re a small site, you may pay nothing for a long time, and that&apos;s a real point in
+ PostHog&apos;s favor.
+ </>,
+ <>
+ Past the free tier, web analytics is billed together with product analytics on usage-based pricing: from
+ $0.0000500 per event on the 1&ndash;2M tier, scaling down to $0.0000090 per event at 250M+. Per-event
+ metering means the invoice moves with your traffic &mdash; a launch spike, a viral post, or
+ autocapture-heavy pages all show up on the bill, so teams at scale end up watching billing limits alongside
+ their dashboards. Rybbit&apos;s <Link href="/pricing">pricing</Link>{" "}
+ is a flat subscription from $19/mo for
+ 100k events, every feature on every plan, with a 7-day trial &mdash; and if you&apos;d rather pay nothing,
+ the open-source version is <Link href="/docs/self-hosting">free to self-host</Link>.
+ </>,
+ ],
+ },
+ {
+ heading: "Privacy: defaults matter",
+ paragraphs: [
+ <>
+ Both tools are open source, but their out-of-the-box privacy postures differ. Rybbit is cookieless by
+ default: no consent banner needed, no persistent identifiers, and visitor hashes rotate with a daily salt.
+ PostHog can be configured for cookieless tracking, but its default configuration generally needs a consent
+ banner in the EU &mdash; and every visitor who declines is a session your product data never sees. If
+ &ldquo;accurate traffic numbers without a banner&rdquo; is the goal, the tool that does it with zero
+ configuration wins by default.
+ </>,
+ ],
+ },
+ {
+ heading: "Running PostHog and Rybbit together",
+ paragraphs: [
+ <>
+ This doesn&apos;t have to be an either/or decision. A setup we see often: keep PostHog for what it&apos;s
+ uniquely good at &mdash; feature flags, experiments, and SQL access to raw events &mdash; and run Rybbit as
+ the source of truth for traffic. Marketing, founders, and support get a dashboard they can read without
+ training, with cookieless numbers that aren&apos;t gated behind consent, while the product team keeps its
+ full PostHog toolkit. The two scripts don&apos;t conflict, and Rybbit&apos;s flat plan means the second
+ tool doesn&apos;t add a second metered bill. For a wider look at the landscape, see our{" "}
+ <Link href="/blog/best-web-analytics-tools">guide to the best web analytics tools</Link>.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "How is Rybbit different from PostHog?",
diff --git a/docs/src/app/[locale]/(home)/compare/posthog/page.tsx b/docs/src/app/[locale]/(home)/compare/posthog/page.tsx
index 91591a025..de292a499 100644
--- a/docs/src/app/[locale]/(home)/compare/posthog/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/posthog/page.tsx
@@ -102,6 +102,7 @@ export default function PostHog() {
chooseCompetitor={posthogExtendedData.chooseCompetitor}
rybbitPricing={posthogExtendedData.rybbitPricing}
competitorPricing={posthogExtendedData.competitorPricing}
+ deepDive={posthogExtendedData.deepDive}
faqItems={posthogExtendedData.faqItems}
relatedResources={posthogExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/simpleanalytics/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/simpleanalytics/comparison-data.tsx
index 24344b8af..3e5b10b61 100644
--- a/docs/src/app/[locale]/(home)/compare/simpleanalytics/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/simpleanalytics/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const simpleAnalyticsComparisonData: ComparisonSection[] = [
{
@@ -40,7 +41,7 @@ export const simpleAnalyticsComparisonData: ComparisonSection[] = [
{ name: "Script size", rybbitValue: "18KB", competitorValue: "~6KB" },
{ name: "Bypasses ad blockers", rybbitValue: true, competitorValue: true },
{ name: "API access", rybbitValue: true, competitorValue: true },
- { name: "Starting price", rybbitValue: "$19/mo", competitorValue: "$19/mo" },
+ { name: "Starting price", rybbitValue: "$19/mo", competitorValue: "$20/mo per user" },
],
},
];
@@ -66,7 +67,7 @@ export const simpleAnalyticsExtendedData = {
chooseCompetitor: [
"You want built-in AI-powered analytics assistant",
- "You want a Mini plan with unlimited websites",
+ "You want a free tier for hobby sites without entering a card",
"You prefer a longer-established product",
"You don't need advanced features like funnels or session replay",
"You want country-level data only for maximum privacy",
@@ -86,16 +87,102 @@ export const simpleAnalyticsExtendedData = {
competitorPricing: {
name: "Simple Analytics",
- model: "Pageview-based pricing",
- startingPrice: "$19/mo",
+ model: "Per-user + pageview pricing",
+ startingPrice: "$20/mo",
highlights: [
- "Starts at 100k pageviews/month",
- "No free tier, 14-day trial only",
- "AI assistant included on all plans",
+ "Free tier for hobby sites: 1 user, 5 websites, 1 month of history",
+ "$20/mo for 1 user; each extra team member is +$20/mo",
+ "14-day free trial, no card required",
"Cloud-only, no self-hosting option",
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Simple Analytics vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "Per-seat pricing vs unlimited team members",
+ paragraphs: [
+ <>
+ Simple Analytics prices by user. Paid plans start at $20 per month for one user, with a usage slider that
+ scales the price by pageviews (the slider runs from 100k up to 2.5M), and every additional team member
+ costs another $20 per month. Annual billing gives you two months free, and there&apos;s a genuinely useful
+ free tier for hobby sites &mdash; one user, five websites, one month of history, no card required.
+ </>,
+ <>
+ For a solo founder that model works fine. For a team it compounds quickly: five people looking at the same
+ dashboard is $100 per month before you&apos;ve touched the pageview slider. Rybbit&apos;s{" "}
+ <Link href="/pricing">pricing</Link> starts at $19 per month for 100k events and includes unlimited team
+ members on every plan, so adding your designer, your marketer, and your co-founder costs nothing extra.
+ </>,
+ ],
+ },
+ {
+ heading: "Minimal by design, and what that leaves out",
+ paragraphs: [
+ <>
+ Simple Analytics deserves credit for being exactly what it says. The Amsterdam-based team collects the
+ least data of any paid analytics tool in this category, hosts everything in the EU end to end, and ships a
+ clean dashboard with an AI chat over your stats. In 2026 it also repositioned itself: rather than pitching
+ a full GA replacement, it now markets itself as a complement that fixes consent loss &mdash; arguing that
+ Google Analytics can miss up to 60% of traffic and telling you &ldquo;Don&apos;t replace your analytics.
+ Fix it.&rdquo; If you want the most conservative data collection available in a managed EU service, or you
+ plan to keep GA and run a privacy-friendly counter next to it, that&apos;s a coherent offer.
+ </>,
+ <>
+ The trade-off is depth. There&apos;s no <Link href="/features/session-replay">session replay</Link>, no{" "}
+ <Link href="/features/funnels">funnel analysis</Link>, no user journeys, no error tracking, no Web Vitals,
+ and no user profiles &mdash; when a conversion drops, Simple Analytics can tell you that it happened, but
+ not where in the flow or what the user saw. Rybbit stays cookieless with a daily-rotating salt while
+ shipping all of those, so you don&apos;t have to choose between privacy and being able to answer
+ &ldquo;why.&rdquo;
+ </>,
+ ],
+ },
+ {
+ heading: "EU hosting is good; owning the stack is better",
+ paragraphs: [
+ <>
+ EU hosting end to end is a real advantage over analytics vendors running on US clouds, and Simple
+ Analytics is rightly proud of it. But it&apos;s still someone else&apos;s SaaS: the code is closed source,
+ there&apos;s no self-hosting option, and your data lives on their infrastructure under their terms.
+ </>,
+ <>
+ Rybbit is open source, so you can audit exactly how visitor data is handled &mdash; and you can{" "}
+ <Link href="/docs/self-hosting">self-host it for free</Link>, which beats even the best EU hosting for data
+ sovereignty: analytics data never leaves infrastructure you control. If you&apos;d rather not run servers,
+ the cloud version keeps the same cookieless, no-personal-data model.
+ </>,
+ ],
+ },
+ {
+ heading: "Switching from Simple Analytics to Rybbit",
+ paragraphs: [
+ <>
+ Unusually for an analytics migration, you don&apos;t have to start from zero: Rybbit ships a data importer
+ for Simple Analytics, so you can bring your historical stats with you. See the{" "}
+ <Link href="/docs">docs</Link> for the import walkthrough.
+ </>,
+ <ol>
+ <li>
+ Add the Rybbit tracking script &mdash; one tag, and data appears within minutes. The 7-day trial covers
+ every feature, so you can evaluate replay and funnels on real traffic.
+ </li>
+ <li>Run the Simple Analytics importer to backfill your history, then compare the two dashboards.</li>
+ <li>
+ Once the numbers line up, remove the Simple Analytics script &mdash; or keep both during a transition
+ period; the scripts don&apos;t conflict.
+ </li>
+ </ol>,
+ <>
+ Still weighing options? Our roundup of the{" "}
+ <Link href="/blog/best-web-analytics-tools">best web analytics tools</Link> covers where each tool fits.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "Is Rybbit open source while Simple Analytics is not?",
diff --git a/docs/src/app/[locale]/(home)/compare/simpleanalytics/page.tsx b/docs/src/app/[locale]/(home)/compare/simpleanalytics/page.tsx
index 6a27143c1..921456c8a 100644
--- a/docs/src/app/[locale]/(home)/compare/simpleanalytics/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/simpleanalytics/page.tsx
@@ -102,6 +102,7 @@ export default function SimpleAnalytics() {
chooseCompetitor={simpleAnalyticsExtendedData.chooseCompetitor}
rybbitPricing={simpleAnalyticsExtendedData.rybbitPricing}
competitorPricing={simpleAnalyticsExtendedData.competitorPricing}
+ deepDive={simpleAnalyticsExtendedData.deepDive}
faqItems={simpleAnalyticsExtendedData.faqItems}
relatedResources={simpleAnalyticsExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/compare/umami/comparison-data.tsx b/docs/src/app/[locale]/(home)/compare/umami/comparison-data.tsx
index c0e26ec60..29f79d7be 100644
--- a/docs/src/app/[locale]/(home)/compare/umami/comparison-data.tsx
+++ b/docs/src/app/[locale]/(home)/compare/umami/comparison-data.tsx
@@ -1,4 +1,5 @@
-import { ComparisonSection, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
+import Link from "next/link";
+import { ComparisonSection, DeepDive, FAQItem, PricingInfo, RelatedResource } from "../components/ComparisonPage";
export const umamiComparisonData: ComparisonSection[] = [
{
@@ -40,7 +41,7 @@ export const umamiComparisonData: ComparisonSection[] = [
{ name: "Script size", rybbitValue: "18KB", competitorValue: "~2KB" },
{ name: "Bypasses ad blockers", rybbitValue: true, competitorValue: true },
{ name: "API access", rybbitValue: true, competitorValue: true },
- { name: "Starting price", rybbitValue: "$19/mo", competitorValue: "$20/mo" },
+ { name: "Starting price", rybbitValue: "$19/mo", competitorValue: "Free (Hobby)" },
],
},
];
@@ -86,16 +87,109 @@ export const umamiExtendedData = {
competitorPricing: {
name: "Umami",
- model: "Usage-based + flat fee",
- startingPrice: "$20/mo",
+ model: "Free tier + paid cloud",
+ startingPrice: "Free",
highlights: [
- "Hobby plan at $20/mo for 100k events",
- "Self-hosted version is completely free",
- "Cloud plans scale with usage",
- "No free cloud tier available",
+ "Cloud Hobby plan is free forever",
+ "Pro plan at $20/mo for 1M events",
+ "14-day free trial on paid plans",
+ "Self-hosted version is completely free (MIT)",
],
} satisfies PricingInfo,
+ deepDive: {
+ title: "Umami vs Rybbit, in depth",
+ sections: [
+ {
+ heading: "Both open source, built for different jobs",
+ paragraphs: [
+ <>
+ This isn&apos;t an open-vs-proprietary comparison &mdash; both tools are open source and self-hostable, and
+ that shapes what the real question is. Umami is a deliberately minimal analytics tool: a small,
+ MIT-licensed Node app with a database behind it, famously easy to run yourself, with reporting that stays
+ intentionally lean &mdash; pageviews, referrers, custom events, and a set of basic reports. That
+ minimalism is a philosophy, not a shortcoming, and it&apos;s why Umami is so widely deployed on personal
+ sites and side projects.
+ </>,
+ <>
+ Rybbit makes the other bet: a full analytics platform that happens to also be open source. Alongside the
+ traffic stats you&apos;d expect, it ships <Link href="/features/session-replay">session replay</Link>,{" "}
+ <Link href="/features/funnels">funnels</Link>, user journey visualization, error tracking, Web Vitals
+ monitoring, and user profiles. Both tools can show you a funnel; the difference appears when a number
+ raises a question. In Umami the report is where the trail ends. In Rybbit you can open the sessions behind
+ a drop-off, watch the replays, and see whether a JavaScript error or a confusing form is the culprit.
+ </>,
+ ],
+ },
+ {
+ heading: "Pricing and self-hosting, honestly",
+ paragraphs: [
+ <>
+ Umami&apos;s cloud has a Hobby plan that is free forever, and the Pro plan is $20/mo for 1M events with a
+ 14-day trial &mdash; though most Umami adoption is the free tier or self-hosting, and for basic traffic
+ stats at $0 that is genuinely hard to beat. Rybbit starts at $19/mo for 100k events with a 7-day trial,
+ and every plan includes every feature. Per event, Umami Pro is cheaper; what you&apos;re paying Rybbit for
+ is depth of reporting, not the traffic counting. See the full breakdown on the{" "}
+ <Link href="/pricing">pricing page</Link>.
+ </>,
+ <>
+ Both self-host for free. Umami is the lighter operational lift &mdash; a small Node app plus a Postgres or
+ MySQL database you probably already know how to run. Rybbit&apos;s{" "}
+ <Link href="/docs/self-hosting">self-hosted deployment</Link> is a Docker Compose stack with more moving
+ parts, because features like session replay and fast queries over large event volumes need more
+ infrastructure behind them. If your goal is the smallest possible thing to maintain, Umami wins that
+ trade; if you want the full platform on your own hardware, Rybbit&apos;s setup is still a single Docker
+ install.
+ </>,
+ ],
+ },
+ {
+ heading: "Switching from Umami to Rybbit",
+ paragraphs: [
+ <>
+ Unlike most analytics migrations, you don&apos;t have to start from zero: Rybbit ships a data importer for
+ Umami (imports are supported for Plausible, Umami, and Simple Analytics), so your historical traffic comes
+ with you. A low-risk path looks like this:
+ </>,
+ <ol>
+ <li>
+ Add the Rybbit tracking script and leave Umami running. Both are lightweight and cookieless, and the two
+ scripts don&apos;t conflict, so running them side by side costs you nothing.
+ </li>
+ <li>
+ Import your Umami history with the built-in importer &mdash; see the{" "}
+ <Link href="/docs">docs</Link> for the walkthrough &mdash; so your Rybbit dashboard starts with
+ continuity instead of a blank chart.
+ </li>
+ <li>
+ Recreate your custom events and goals. Umami&apos;s event model maps cleanly onto Rybbit&apos;s custom
+ events with attributes.
+ </li>
+ <li>
+ Compare the two dashboards for a week or two. Once the numbers line up, remove the Umami script &mdash;
+ or keep the instance around; a self-hosted Umami costs nothing to leave running.
+ </li>
+ </ol>,
+ ],
+ },
+ {
+ heading: "When Umami is the better choice",
+ paragraphs: [
+ <>
+ Plenty of sites should just use Umami. If you&apos;re running a personal blog or hobby project and your
+ analytics budget is $0, Umami&apos;s free-forever cloud tier or a tiny self-hosted instance is the right
+ answer &mdash; Rybbit&apos;s extra features would sit unused. The same goes if you want the lightest
+ possible footprint (Umami&apos;s ~2KB script is about as small as tracking gets), or if you specifically
+ want an MIT license for your stack. Where the calculus changes is when a project becomes a business:
+ the moment you need to know <em>why</em> a conversion rate dropped &mdash; not just that it did &mdash;
+ you&apos;ve outgrown minimal analytics. For a wider survey of the options, see our guide to the{" "}
+ <Link href="/blog/best-web-analytics-tools">best web analytics tools</Link>.
+ </>,
+ ],
+ },
+ ],
+ } satisfies DeepDive,
+
faqItems: [
{
question: "How is Rybbit different from Umami?",
diff --git a/docs/src/app/[locale]/(home)/compare/umami/page.tsx b/docs/src/app/[locale]/(home)/compare/umami/page.tsx
index 4cdb7cb81..97739abcf 100644
--- a/docs/src/app/[locale]/(home)/compare/umami/page.tsx
+++ b/docs/src/app/[locale]/(home)/compare/umami/page.tsx
@@ -102,6 +102,7 @@ export default function Umami() {
chooseCompetitor={umamiExtendedData.chooseCompetitor}
rybbitPricing={umamiExtendedData.rybbitPricing}
competitorPricing={umamiExtendedData.competitorPricing}
+ deepDive={umamiExtendedData.deepDive}
faqItems={umamiExtendedData.faqItems}
relatedResources={umamiExtendedData.relatedResources}
/>
diff --git a/docs/src/app/[locale]/(home)/for-agencies/page.tsx b/docs/src/app/[locale]/(home)/for-agencies/page.tsx
index ff620490d..072ec9826 100644
--- a/docs/src/app/[locale]/(home)/for-agencies/page.tsx
+++ b/docs/src/app/[locale]/(home)/for-agencies/page.tsx
@@ -10,7 +10,7 @@ import Link from "next/link";
const pageTitle = "Rybbit for Agencies | Client-Friendly Web Analytics";
const pageDescription =
- "Run every client site from one workspace. Dashboards clients can read without a training call, automated email reports, share links without accounts, and unlimited websites on Pro.";
+ "Run every client site from one workspace. Dashboards clients can read without a training call, teams and roles that keep each client in their lane, history imports from Plausible and Umami, and unlimited websites on Pro.";
export const metadata = createMetadata({
title: pageTitle,
@@ -37,25 +37,45 @@ const faqItems = [
answer:
"Yes. Share any dashboard with a secret link or make it fully public. People with the link see that site's dashboard and nothing else β€” no account required.",
},
+ {
+ question: "Can a client accidentally see another client's numbers?",
+ answer:
+ "No. Members can be restricted to specific sites, so a client you invite sees only their own site. Share links are scoped to one site each. Only your own admins and owners see the whole workspace.",
+ },
{
question: "How many websites can I add?",
answer:
"The Standard plan includes up to 5 websites. Pro includes unlimited websites, so every client site fits under one subscription.",
},
+ {
+ question: "Can I import a client's analytics history?",
+ answer:
+ "Yes. Rybbit imports historical data from Plausible, Umami, and Simple Analytics β€” up to 36 months on Standard and 60 months on Pro, with no limits when self-hosting. Clients switching to you don't lose their history.",
+ },
{
question: "Can I give a client or teammate limited access?",
answer:
- "Yes. Organizations support member roles, so you control who can view dashboards and who can manage sites and settings.",
+ "Yes. Organizations support owner, admin, and member roles. Members can be limited to specific sites, and teams let you group sites β€” for example, one team per client β€” so access follows the roster automatically.",
+ },
+ {
+ question: "Can clients change settings or break anything?",
+ answer:
+ "No. Members can view analytics for their assigned sites but can't manage settings, sites, or other members. Configuration stays with your admins and owners.",
},
{
question: "Do client sites need a cookie consent banner for Rybbit?",
answer:
"No. Rybbit doesn't use cookies or collect personal data, so it's GDPR and CCPA compliant without a consent banner.",
},
+ {
+ question: "Do clients get reports automatically?",
+ answer:
+ "Yes. Rybbit sends automatic weekly email reports summarizing analytics performance, so clients get their numbers in the inbox without you exporting anything.",
+ },
{
question: "Can I white-label Rybbit for my clients?",
answer:
- "White-labeling is available on the Enterprise plan, along with dedicated instances and on-premise installation. Contact us to talk through your setup.",
+ "You can embed read-only dashboards in your own portal on any plan, and full white-labeling β€” rebranding, custom domain, dedicated instance β€” is available on Enterprise. See the white-label page for the full range.",
},
{
question: "What happens if a client wants to take over their analytics?",
@@ -71,12 +91,85 @@ const workspaceRows = [
{ domain: "fernwood.studio", visitors: "9.8k", delta: "+4%" },
];
+const teamRows = [
+ { team: "Acme Cycles", detail: "3 sites Β· 2 members" },
+ { team: "Harbor Dental", detail: "1 site Β· 1 member" },
+ { team: "Retainer clients", detail: "9 sites Β· 4 members" },
+];
+
+const onboardingSteps = [
+ {
+ step: "01",
+ title: "Add the site",
+ body: "One script tag, or a plugin for WordPress, Webflow, Shopify, and the rest of the stack you build on. Live data in minutes.",
+ },
+ {
+ step: "02",
+ title: "Bring the history",
+ body: "Import up to five years of data from Plausible, Umami, or Simple Analytics, so the first dashboard the client sees isn't empty.",
+ },
+ {
+ step: "03",
+ title: "Set the access",
+ body: "Invite the client as a member scoped to their site β€” or skip accounts entirely and send a share link.",
+ },
+ {
+ step: "04",
+ title: "Turn on reports",
+ body: "Automatic weekly email reports put the numbers in the client's inbox before they think to ask for them.",
+ },
+];
+
+// Feature rows: the depth pitch, each linking into the feature pages.
+const depthRows = [
+ {
+ href: "/features/funnels",
+ title: "Funnels",
+ fact: "Show which step of a client's checkout or signup flow loses people, and how many",
+ },
+ {
+ href: "/features/goals",
+ title: "Goals",
+ fact: "Track the conversions each client actually cares about: purchases, bookings, form fills",
+ },
+ {
+ href: "/features/session-replay",
+ title: "Session replay",
+ fact: "Watch the session behind a complaint instead of guessing what went wrong",
+ },
+ {
+ href: "/features/error-tracking",
+ title: "Error tracking",
+ fact: "Catch the JavaScript error breaking a client's form before the client does",
+ },
+ {
+ href: "/features/web-vitals",
+ title: "Web vitals",
+ fact: "Prove the site you shipped is fast β€” and catch regressions after every release",
+ },
+ {
+ href: "/features/user-journeys",
+ title: "User journeys",
+ fact: "Show clients how visitors actually move through the site you built for them",
+ },
+];
+
const tierFacts = [
{ tier: "Standard", fact: "Up to 5 websites and 3 team members" },
{ tier: "Pro", fact: "Unlimited websites, unlimited team members" },
{ tier: "Enterprise", fact: "White-labeling, SSO, dedicated instance" },
];
+const tocItems = [
+ { href: "#agency-problem-title", label: "The problem" },
+ { href: "#agency-onboarding-title", label: "Client onboarding" },
+ { href: "#agency-toolkit", label: "The toolkit" },
+ { href: "#agency-migration-title", label: "Migrating clients" },
+ { href: "#agency-depth-title", label: "Beyond pageviews" },
+ { href: "#agency-pricing-title", label: "Pricing" },
+ { href: "#agency-faq", label: "FAQ" },
+];
+
export default function ForAgenciesPage() {
return (
<div className="overflow-x-clip">
@@ -87,6 +180,26 @@ export default function ForAgenciesPage() {
eventLocation="for_agencies_hero"
/>
+ <nav
+ aria-label="On this page"
+ className="border-b border-neutral-200 dark:border-neutral-800"
+ >
+ <div className="relative mx-auto flex max-w-[1200px] flex-wrap items-baseline gap-x-6 gap-y-2 border-x border-neutral-200 px-5 py-4 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <span className="text-xs font-medium uppercase tracking-wider text-neutral-400 dark:text-neutral-500">
+ On this page
+ </span>
+ {tocItems.map(item => (
+ <a
+ key={item.href}
+ href={item.href}
+ className="rounded-sm text-sm text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ {item.label}
+ </a>
+ ))}
+ </div>
+ </nav>
+
<section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="agency-problem-title">
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
@@ -100,7 +213,7 @@ export default function ForAgenciesPage() {
<SectionKicker>The client problem</SectionKicker>
<h2
id="agency-problem-title"
- className="mt-5 max-w-2xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
Your clients don&apos;t want analytics. They want answers.
</h2>
@@ -114,10 +227,77 @@ export default function ForAgenciesPage() {
</p>
</div>
</div>
+ <div className="border-t border-neutral-200 px-5 py-10 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <div className="grid grid-cols-1 gap-10 lg:grid-cols-2">
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ The hidden cost of GA4 on a client roster isn&apos;t the price β€” it&apos;s the explaining. Every
+ report needs a translation layer, every dashboard needs a walkthrough, and every walkthrough is
+ unbilled time. An analytics tool a client can read on their own takes the walkthrough off the
+ calendar.
+ </p>
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ There&apos;s a compliance angle too. Every GA-instrumented site you hand over ships with a cookie
+ banner and a consent-declined blind spot in its numbers. Rybbit is cookieless, so the sites you
+ build need neither β€” and the traffic you report is the traffic that actually happened.{" "}
+ <Link
+ href="/compare/google-analytics"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ See the full GA4 comparison
+ </Link>
+ .
+ </p>
+ </div>
+ </div>
</div>
</section>
- <section className="border-b border-neutral-200 dark:border-neutral-800" aria-label="Agency workflow">
+ <section
+ className="border-b border-neutral-200 dark:border-neutral-800"
+ aria-labelledby="agency-onboarding-title"
+ >
+ <div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
+ <GridCrosses />
+ <div className="grid grid-cols-1 lg:grid-cols-12">
+ <div className="relative border-b border-neutral-200 bg-plate-accent px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <div
+ aria-hidden="true"
+ className="pointer-events-none absolute inset-0 bg-graph-accent [mask-image:linear-gradient(to_bottom,black,transparent_92%)]"
+ />
+ <div className="relative">
+ <SectionKicker>The first afternoon</SectionKicker>
+ <h2
+ id="agency-onboarding-title"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ New client to first report, in four steps.
+ </h2>
+ </div>
+ </div>
+ <div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
+ Onboarding a client onto analytics shouldn&apos;t be a project with a kickoff meeting. This is the
+ whole workflow β€” most of it is done before the coffee goes cold.
+ </p>
+ </div>
+ </div>
+ <div className="grid grid-cols-1 gap-px border-t border-neutral-200 bg-neutral-200 p-px dark:border-neutral-800 dark:bg-neutral-800 sm:grid-cols-2 lg:grid-cols-4">
+ {onboardingSteps.map(item => (
+ <article key={item.step} className="bg-white px-5 py-8 dark:bg-neutral-950 sm:px-6">
+ <span className="font-mono text-xs text-neutral-400 dark:text-neutral-500">{item.step}</span>
+ <h3 className="mt-3 text-base font-semibold tracking-tight">{item.title}</h3>
+ <p className="mt-2 text-sm leading-6 text-neutral-600 dark:text-neutral-400">{item.body}</p>
+ </article>
+ ))}
+ </div>
+ </div>
+ </section>
+
+ <section
+ id="agency-toolkit"
+ className="scroll-mt-24 border-b border-neutral-200 dark:border-neutral-800"
+ aria-label="Agency workflow"
+ >
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
<div className="grid grid-cols-1 gap-px bg-neutral-200 p-px dark:bg-neutral-800 lg:grid-cols-12">
@@ -144,27 +324,53 @@ export default function ForAgenciesPage() {
</article>
<article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-5 lg:px-10">
- <h3 className="text-lg font-semibold tracking-tight">Reports that send themselves</h3>
+ <h3 className="text-lg font-semibold tracking-tight">One team per client</h3>
<p className="mt-2 max-w-md text-sm leading-6 text-neutral-600 dark:text-neutral-400">
- Weekly or monthly email reports per site. Clients get their numbers in the inbox without you
- exporting a PDF on the last Friday of the month.
+ Teams group sites and the people responsible for them. Set up a team per client β€” or per retainer
+ tier β€” and access follows the roster instead of being managed site by site.
</p>
- <div className="mt-6 flex max-w-sm items-center gap-3 rounded-md border border-neutral-200 px-3.5 py-3 dark:border-neutral-800">
- <Mail aria-hidden="true" className="size-4 shrink-0 text-neutral-400 dark:text-neutral-500" />
- <div className="min-w-0 text-xs leading-5">
- <p className="truncate font-medium text-neutral-700 dark:text-neutral-300">
- Weekly report β€” acme-cycles.com
- </p>
- <p className="text-neutral-500 dark:text-neutral-400">Arrives Monday, 9:00</p>
+ <ul className="mt-6 max-w-sm divide-y divide-neutral-200 rounded-md border border-neutral-200 dark:divide-neutral-800 dark:border-neutral-800">
+ {teamRows.map(row => (
+ <li key={row.team} className="flex items-center justify-between gap-3 px-3.5 py-2.5 text-sm">
+ <span className="font-medium">{row.team}</span>
+ <span className="text-xs text-neutral-500 dark:text-neutral-400">{row.detail}</span>
+ </li>
+ ))}
+ </ul>
+ </article>
+
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-5 lg:px-10">
+ <h3 className="text-lg font-semibold tracking-tight">Clients stay in their lane</h3>
+ <p className="mt-2 max-w-md text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ Invite a client as a member restricted to their own site: they see their numbers, and only their
+ numbers. Settings, billing, and the rest of the roster stay with your admins.
+ </p>
+ <div className="mt-6 max-w-sm rounded-md border border-neutral-200 px-3.5 py-3 dark:border-neutral-800">
+ <div className="flex items-center justify-between gap-3 text-sm">
+ <span className="truncate font-mono text-xs text-neutral-700 dark:text-neutral-300">
+ </span>
+ <span className="shrink-0 rounded-sm border border-neutral-200 px-1.5 py-0.5 text-xs text-neutral-500 dark:border-neutral-800 dark:text-neutral-400">
+ Member
+ </span>
</div>
+ <p className="mt-1.5 text-xs text-neutral-500 dark:text-neutral-400">Access: acme-cycles.com only</p>
</div>
</article>
- <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-5 lg:px-10">
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-7 lg:px-10">
<h3 className="text-lg font-semibold tracking-tight">Share a dashboard, not a login</h3>
- <p className="mt-2 max-w-md text-sm leading-6 text-neutral-600 dark:text-neutral-400">
- Any dashboard can be shared with a secret link or made fully public. Clients see their site&apos;s
- numbers without creating an account β€” and never anyone else&apos;s.
+ <p className="mt-2 max-w-lg text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ Any dashboard can be shared with a secret link or made fully public β€” and read-only dashboards can be
+ embedded straight into your own client portal. Clients see their site&apos;s numbers without creating
+ an account, and never anyone else&apos;s.{" "}
+ <Link
+ href="/features/dashboard-sharing"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ More on dashboard sharing
+ </Link>
+ .
</p>
<div className="mt-6 flex max-w-sm items-center gap-2.5 rounded-md border border-neutral-200 bg-neutral-50 px-3.5 py-2.5 dark:border-neutral-800 dark:bg-neutral-900">
<Link2 aria-hidden="true" className="size-3.5 shrink-0 text-neutral-400 dark:text-neutral-500" />
@@ -174,6 +380,23 @@ export default function ForAgenciesPage() {
</div>
</article>
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-5 lg:px-10">
+ <h3 className="text-lg font-semibold tracking-tight">Reports that send themselves</h3>
+ <p className="mt-2 max-w-md text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ Automatic weekly email reports summarize performance and land in the inbox. Clients get their numbers
+ without you exporting a PDF on the last Friday of the month.
+ </p>
+ <div className="mt-6 flex max-w-sm items-center gap-3 rounded-md border border-neutral-200 px-3.5 py-3 dark:border-neutral-800">
+ <Mail aria-hidden="true" className="size-4 shrink-0 text-neutral-400 dark:text-neutral-500" />
+ <div className="min-w-0 text-xs leading-5">
+ <p className="truncate font-medium text-neutral-700 dark:text-neutral-300">
+ Weekly report β€” acme-cycles.com
+ </p>
+ <p className="text-neutral-500 dark:text-neutral-400">Arrives Monday, 9:00</p>
+ </div>
+ </div>
+ </article>
+
<article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-7 lg:px-10">
<h3 className="text-lg font-semibold tracking-tight">No cookie banner on any client site</h3>
<p className="mt-2 max-w-lg text-sm leading-6 text-neutral-600 dark:text-neutral-400">
@@ -208,6 +431,130 @@ export default function ForAgenciesPage() {
</div>
</section>
+ <section
+ className="border-b border-neutral-200 dark:border-neutral-800"
+ aria-labelledby="agency-migration-title"
+ >
+ <div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
+ <GridCrosses />
+ <div className="grid grid-cols-1 lg:grid-cols-12">
+ <div className="relative border-b border-neutral-200 bg-plate-accent px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <div
+ aria-hidden="true"
+ className="pointer-events-none absolute inset-0 bg-graph-accent [mask-image:linear-gradient(to_bottom,black,transparent_92%)]"
+ />
+ <div className="relative">
+ <SectionKicker>Switching a roster</SectionKicker>
+ <h2
+ id="agency-migration-title"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ Move clients over without losing their history.
+ </h2>
+ </div>
+ </div>
+ <div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
+ The worst part of switching analytics for a whole roster is the empty dashboards on day one. Rybbit
+ imports the history, so year-over-year comparisons survive the migration.
+ </p>
+ </div>
+ </div>
+ <div className="border-t border-neutral-200 px-5 py-10 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <div className="grid grid-cols-1 gap-10 lg:grid-cols-2">
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ Clients coming from <span className="font-medium text-neutral-800 dark:text-neutral-200">Plausible</span>,{" "}
+ <span className="font-medium text-neutral-800 dark:text-neutral-200">Umami</span>, or{" "}
+ <span className="font-medium text-neutral-800 dark:text-neutral-200">Simple Analytics</span> bring
+ their data with them: up to 36 months of history on Standard, 60 months on Pro, and no limits if you
+ self-host. Upload the export, and the past shows up in the same dashboard as the present.{" "}
+ <Link
+ href="/docs/data-import"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ How data import works
+ </Link>
+ .
+ </p>
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ Moving clients off Google Analytics? GA4 history can&apos;t be imported β€” no tool maps its event
+ model honestly β€” so those clients start fresh with numbers they can finally read. The comparison
+ pages cover how the metrics line up, so you can answer &ldquo;why don&apos;t these match GA?&rdquo;
+ before it&apos;s asked:{" "}
+ <Link
+ href="/compare/google-analytics"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ vs. Google Analytics
+ </Link>
+ ,{" "}
+ <Link
+ href="/compare/plausible"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ vs. Plausible
+ </Link>
+ ,{" "}
+ <Link
+ href="/compare/matomo"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ vs. Matomo
+ </Link>
+ .
+ </p>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="agency-depth-title">
+ <div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
+ <GridCrosses />
+ <div className="grid grid-cols-1 border-b border-neutral-200 dark:border-neutral-800 lg:grid-cols-12">
+ <div className="relative border-b border-neutral-200 bg-plate-accent px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <div
+ aria-hidden="true"
+ className="pointer-events-none absolute inset-0 bg-graph-accent [mask-image:linear-gradient(to_bottom,black,transparent_92%)]"
+ />
+ <div className="relative">
+ <SectionKicker>Beyond pageviews</SectionKicker>
+ <h2
+ id="agency-depth-title"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ When the client asks &ldquo;why?&rdquo;, have more than traffic.
+ </h2>
+ </div>
+ </div>
+ <div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
+ Simple to read doesn&apos;t mean shallow. The same script that counts visitors powers the tools that
+ justify a retainer β€” one layer down, never in the way.
+ </p>
+ </div>
+ </div>
+ <div>
+ {depthRows.map(item => (
+ <Link
+ key={item.href}
+ href={item.href}
+ className="group grid border-b border-neutral-200 px-5 py-6 transition-colors last:border-b-0 hover:bg-neutral-50 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-inset focus-visible:ring-neutral-500 dark:border-neutral-800 dark:hover:bg-neutral-900/60 sm:grid-cols-[190px_1fr_auto] sm:items-center sm:gap-6 sm:px-8 lg:px-10"
+ >
+ <span className="font-semibold tracking-tight">{item.title}</span>
+ <span className="mt-1 text-sm leading-6 text-neutral-500 dark:text-neutral-400 sm:mt-0">
+ {item.fact}
+ </span>
+ <ArrowRight
+ className="mt-3 size-4 text-neutral-400 transition-transform group-hover:translate-x-1 motion-reduce:transition-none sm:mt-0"
+ aria-hidden="true"
+ />
+ </Link>
+ ))}
+ </div>
+ </div>
+ </section>
+
<section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="agency-pricing-title">
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
@@ -221,7 +568,7 @@ export default function ForAgenciesPage() {
<SectionKicker>Pricing for a roster</SectionKicker>
<h2
id="agency-pricing-title"
- className="mt-5 max-w-2xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
Unlimited client websites on Pro.
</h2>
@@ -251,6 +598,19 @@ export default function ForAgenciesPage() {
/>
</Link>
))}
+ <div className="flex flex-wrap items-center justify-between gap-3 border-t border-neutral-200 px-5 py-5 text-sm text-neutral-500 dark:border-neutral-800 dark:text-neutral-400 sm:px-8 lg:px-10">
+ <span>Want your own brand on the dashboards?</span>
+ <Link
+ href="/white-label"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ White-label options
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </div>
<div className="flex flex-wrap items-center justify-between gap-3 border-t border-neutral-200 px-5 py-5 text-sm text-neutral-500 dark:border-neutral-800 dark:text-neutral-400 sm:px-8 lg:px-10">
<span>Referring clients instead of hosting them?</span>
<Link
@@ -311,7 +671,9 @@ export default function ForAgenciesPage() {
</div>
</section>
- <PersonaFaqSection heading="Agency questions, answered plainly." items={faqItems} />
+ <div id="agency-faq" className="scroll-mt-24">
+ <PersonaFaqSection heading="Agency questions, answered plainly." items={faqItems} />
+ </div>
<PersonaCrossLinks current="for-agencies" />
<CTASection
diff --git a/docs/src/app/[locale]/(home)/for-saas/page.tsx b/docs/src/app/[locale]/(home)/for-saas/page.tsx
index 2dc026e90..e1b735229 100644
--- a/docs/src/app/[locale]/(home)/for-saas/page.tsx
+++ b/docs/src/app/[locale]/(home)/for-saas/page.tsx
@@ -5,12 +5,12 @@ import { PersonaCrossLinks } from "@/components/persona/PersonaCrossLinks";
import { PersonaFaqSection } from "@/components/persona/PersonaFaqSection";
import { SectionKicker } from "@/components/deco/SectionKicker";
import { createMetadata, createOGImageUrl } from "@/lib/metadata";
-import { ArrowRight } from "lucide-react";
+import { ArrowRight, ExternalLink } from "lucide-react";
import Link from "next/link";
const pageTitle = "Rybbit for SaaS | Funnels, Retention, and Sessions in One Tool";
const pageDescription =
- "Signup funnels, retention cohorts, user profiles, session replay, and error tracking β€” the product-analytics surface without the enterprise setup project. Cookieless and GDPR compliant.";
+ "Signup funnels, retention cohorts, user profiles, session replay, feature flags, and A/B experiments β€” the product-analytics surface without the enterprise setup project. Cookieless and GDPR compliant.";
export const metadata = createMetadata({
title: pageTitle,
@@ -29,6 +29,8 @@ export const metadata = createMetadata({
},
});
+// Rendered in the accordion AND emitted as FAQPage JSON-LD from the same
+// array, so the schema can never drift from the visible answers.
const faqItems = [
{
question: "Is Rybbit web analytics or product analytics?",
@@ -40,6 +42,16 @@ const faqItems = [
answer:
"No. Autocapture records pageviews, clicks, form submits, and errors from the moment the script loads. Custom events are there when you want to name specific product moments, and the Node SDK covers server-side events.",
},
+ {
+ question: "Can I tie sessions to actual user accounts?",
+ answer:
+ "Yes. Identify logged-in users with your own user IDs and their sessions, events, and errors roll up into one profile β€” so 'what did this customer experience' has an answer.",
+ },
+ {
+ question: "Does Rybbit do feature flags and A/B tests?",
+ answer:
+ "Yes. Feature flags handle gradual rollouts, remote config, and variant targeting, and experiments run A/B tests on flag variants and measure conversion lift β€” in the same tool that already tracks the conversions.",
+ },
{
question: "Can I see what an individual user experienced?",
answer:
@@ -55,11 +67,21 @@ const faqItems = [
answer:
"No. Rybbit is cookieless and doesn't collect personal data that could identify visitors, so it's GDPR and CCPA compliant without a consent banner β€” in the app and on the marketing site.",
},
+ {
+ question: "We're on Plausible or Umami. Do we lose our history?",
+ answer:
+ "No. Rybbit imports historical data from Plausible, Umami, and Simple Analytics β€” up to 36 months on Standard and 60 months on Pro β€” so your growth charts keep their past.",
+ },
{
question: "Can we pull the data into our own systems?",
answer:
"Yes. The Stats API exposes metrics, sessions, funnels, goals, errors, and events over HTTP with bearer-key auth, and there's an API playground in the dashboard that generates ready-to-use snippets.",
},
+ {
+ question: "Can we self-host it?",
+ answer:
+ "Yes. Rybbit is open source under AGPL v3 β€” self-host the full product on your own infrastructure with unlimited events, or start on cloud and move later. The workflow is identical either way.",
+ },
];
const funnelSteps = [
@@ -78,6 +100,39 @@ const cohortRows = [
{ cohort: "Jun 22", cells: [100, 61, 47] },
];
+const setupSteps = [
+ {
+ step: "01",
+ title: "Install the script",
+ body: "One tag in your app and marketing site. Autocapture starts recording pageviews, clicks, form submits, and errors immediately.",
+ },
+ {
+ step: "02",
+ title: "Identify your users",
+ body: "Pass your own user IDs for logged-in users, and sessions, events, and errors roll up into per-user profiles.",
+ },
+ {
+ step: "03",
+ title: "Name the moments",
+ body: "Add custom events for the steps that define activation β€” from the browser, or server-side with the Node SDK.",
+ },
+ {
+ step: "04",
+ title: "Build the funnel",
+ body: "Assemble signup and activation funnels from pages and events in a few clicks, and set goals for the conversions that matter.",
+ },
+];
+
+const tocItems = [
+ { href: "#saas-problem-title", label: "The problem" },
+ { href: "#saas-setup-title", label: "The first hour" },
+ { href: "#saas-funnel-title", label: "Funnels" },
+ { href: "#saas-retention-title", label: "Retention" },
+ { href: "#saas-ship-title", label: "Flags & experiments" },
+ { href: "#saas-toolkit", label: "Day to day" },
+ { href: "#saas-faq", label: "FAQ" },
+];
+
export default function ForSaasPage() {
return (
<div className="overflow-x-clip">
@@ -88,6 +143,23 @@ export default function ForSaasPage() {
eventLocation="for_saas_hero"
/>
+ <nav aria-label="On this page" className="border-b border-neutral-200 dark:border-neutral-800">
+ <div className="relative mx-auto flex max-w-[1200px] flex-wrap items-baseline gap-x-6 gap-y-2 border-x border-neutral-200 px-5 py-4 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <span className="text-xs font-medium uppercase tracking-wider text-neutral-400 dark:text-neutral-500">
+ On this page
+ </span>
+ {tocItems.map(item => (
+ <a
+ key={item.href}
+ href={item.href}
+ className="rounded-sm text-sm text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ {item.label}
+ </a>
+ ))}
+ </div>
+ </nav>
+
<section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="saas-problem-title">
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
@@ -101,7 +173,7 @@ export default function ForSaasPage() {
<SectionKicker>One connected surface</SectionKicker>
<h2
id="saas-problem-title"
- className="mt-5 max-w-2xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
Web analytics and product analytics were never two products.
</h2>
@@ -114,6 +186,113 @@ export default function ForSaasPage() {
</p>
</div>
</div>
+ <div className="border-t border-neutral-200 px-5 py-10 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <div className="grid grid-cols-1 gap-10 lg:grid-cols-2">
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ The usual stack is GA4 for marketing plus a product-analytics suite for the app: two scripts, two event
+ schemas, two logins, and an integration that quietly drifts. Rybbit covers the whole path β€” first visit
+ to retained account β€” in one schema, so answering &ldquo;which channel brings users who stick?&rdquo;
+ takes one filter. If you&apos;re weighing the heavier route, see how Rybbit compares to{" "}
+ <Link
+ href="/compare/posthog"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ PostHog
+ </Link>{" "}
+ and{" "}
+ <Link
+ href="/compare/google-analytics"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Google Analytics
+ </Link>
+ .
+ </p>
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ There&apos;s also the banner problem. Cookie-based analytics inside a product means a consent prompt in
+ your own app and a tracking gap wherever users decline. Rybbit is cookieless and collects no personal
+ data by default, so it&apos;s GDPR and CCPA compliant without consent UI β€” your onboarding flow stays
+ clean, and the numbers cover everyone.{" "}
+ <Link
+ href="/privacy"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ How Rybbit handles privacy
+ </Link>
+ .
+ </p>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="saas-setup-title">
+ <div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
+ <GridCrosses />
+ <div className="grid grid-cols-1 lg:grid-cols-12">
+ <div className="relative border-b border-neutral-200 bg-plate-accent px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <div
+ aria-hidden="true"
+ className="pointer-events-none absolute inset-0 bg-graph-accent [mask-image:linear-gradient(to_bottom,black,transparent_92%)]"
+ />
+ <div className="relative">
+ <SectionKicker>The first hour</SectionKicker>
+ <h2
+ id="saas-setup-title"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ From script tag to signup funnel, before standup ends.
+ </h2>
+ </div>
+ </div>
+ <div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
+ Product analytics tools fail at the instrumentation-plan stage β€” the meeting happens, the spreadsheet
+ gets made, the events never ship. Rybbit inverts it: autocapture first, naming later.
+ </p>
+ </div>
+ </div>
+ <div className="grid grid-cols-1 gap-px border-t border-neutral-200 bg-neutral-200 p-px dark:border-neutral-800 dark:bg-neutral-800 sm:grid-cols-2 lg:grid-cols-4">
+ {setupSteps.map(item => (
+ <article key={item.step} className="bg-white px-5 py-8 dark:bg-neutral-950 sm:px-6">
+ <span className="font-mono text-xs text-neutral-400 dark:text-neutral-500">{item.step}</span>
+ <h3 className="mt-3 text-base font-semibold tracking-tight">{item.title}</h3>
+ <p className="mt-2 text-sm leading-6 text-neutral-600 dark:text-neutral-400">{item.body}</p>
+ </article>
+ ))}
+ </div>
+ <div className="flex flex-wrap items-center gap-x-6 gap-y-3 border-t border-neutral-200 px-5 py-5 text-sm dark:border-neutral-800 sm:px-8 lg:px-10">
+ <Link
+ href="/docs/autocapture"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Autocapture docs
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ <Link
+ href="/docs/identify-users"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ Identifying users
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ <Link
+ href="/docs/track-events"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ Custom events
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </div>
</div>
</section>
@@ -125,7 +304,7 @@ export default function ForSaasPage() {
<SectionKicker>Funnels</SectionKicker>
<h2
id="saas-funnel-title"
- className="mt-5 max-w-sm text-4xl font-semibold leading-[1.04] tracking-[-0.035em] md:text-5xl"
+ className="mt-5 max-w-sm scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] md:text-5xl"
>
Find the step that loses trials.
</h2>
@@ -218,7 +397,7 @@ export default function ForSaasPage() {
<SectionKicker>Retention</SectionKicker>
<h2
id="saas-retention-title"
- className="mt-5 max-w-sm text-4xl font-semibold leading-[1.04] tracking-[-0.035em] md:text-5xl"
+ className="mt-5 max-w-sm scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] md:text-5xl"
>
Know if this month&apos;s users stick better than last month&apos;s.
</h2>
@@ -241,7 +420,76 @@ export default function ForSaasPage() {
</div>
</section>
- <section className="border-b border-neutral-200 dark:border-neutral-800" aria-label="SaaS workflow">
+ <section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="saas-ship-title">
+ <div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
+ <GridCrosses />
+ <div className="grid grid-cols-1 lg:grid-cols-12">
+ <div className="relative border-b border-neutral-200 bg-plate-accent px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <div
+ aria-hidden="true"
+ className="pointer-events-none absolute inset-0 bg-graph-accent [mask-image:linear-gradient(to_bottom,black,transparent_92%)]"
+ />
+ <div className="relative">
+ <SectionKicker>Ship and measure</SectionKicker>
+ <h2
+ id="saas-ship-title"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ Roll it out to 10%. Then prove it worked.
+ </h2>
+ </div>
+ </div>
+ <div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
+ The measure-ship-measure loop usually spans three tools. In Rybbit, the flag that gates the feature and
+ the funnel that judges it live on the same dashboard.
+ </p>
+ </div>
+ </div>
+ <div className="grid grid-cols-1 gap-px border-t border-neutral-200 bg-neutral-200 p-px dark:border-neutral-800 dark:bg-neutral-800 lg:grid-cols-2">
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:px-10">
+ <h3 className="text-lg font-semibold tracking-tight">Feature flags</h3>
+ <p className="mt-2 max-w-lg text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ Gate features, roll out gradually, serve remote config, and target variants β€” without a separate flags
+ vendor or another SDK in the bundle.
+ </p>
+ <Link
+ href="/docs/feature-flags"
+ className="group mt-5 inline-flex items-center gap-1.5 rounded-sm text-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Feature flags docs
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </article>
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:px-10">
+ <h3 className="text-lg font-semibold tracking-tight">Experiments</h3>
+ <p className="mt-2 max-w-lg text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ Run A/B tests on flag variants and measure conversion lift against the goals you already track β€” no
+ exporting events to a separate testing platform to find out who won.
+ </p>
+ <Link
+ href="/docs/experiments"
+ className="group mt-5 inline-flex items-center gap-1.5 rounded-sm text-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Experiments docs
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </article>
+ </div>
+ </div>
+ </section>
+
+ <section
+ id="saas-toolkit"
+ className="scroll-mt-24 border-b border-neutral-200 dark:border-neutral-800"
+ aria-label="SaaS workflow"
+ >
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
<div className="grid grid-cols-1 gap-px bg-neutral-200 p-px dark:bg-neutral-800 lg:grid-cols-12">
@@ -282,11 +530,114 @@ export default function ForSaasPage() {
with the Node SDK when the moment doesn&apos;t happen in a click.
</p>
</article>
+
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-5 lg:px-10">
+ <h3 className="text-lg font-semibold tracking-tight">The release-day watch</h3>
+ <p className="mt-2 max-w-md text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ Errors and web vitals sit next to traffic, so a deploy that breaks a form or slows a page shows up in
+ the same place you&apos;re already looking β€” not in a separate monitoring tab.
+ </p>
+ <div className="mt-5 flex flex-wrap gap-x-6 gap-y-3 text-sm">
+ <Link
+ href="/features/error-tracking"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Error tracking
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ <Link
+ href="/features/web-vitals"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ Web vitals
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </div>
+ </article>
+
+ <article className="bg-white px-5 py-10 dark:bg-neutral-950 sm:px-8 lg:col-span-7 lg:px-10">
+ <h3 className="text-lg font-semibold tracking-tight">Ask your analytics, in your editor</h3>
+ <p className="mt-2 max-w-lg text-sm leading-6 text-neutral-600 dark:text-neutral-400">
+ The MCP server puts your analytics in reach of your AI assistant β€” ask &ldquo;what changed in signups
+ this week?&rdquo; from the same place you write code, and get answers backed by the real numbers.
+ </p>
+ <Link
+ href="/features/mcp"
+ className="group mt-5 inline-flex items-center gap-1.5 rounded-sm text-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ MCP server
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </article>
+ </div>
+ </div>
+ </section>
+
+ <section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="saas-own-title">
+ <div className="relative mx-auto grid max-w-[1200px] grid-cols-1 border-x border-neutral-200 dark:border-neutral-800 lg:grid-cols-12">
+ <GridCrosses />
+ <div className="border-b border-neutral-200 px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <h2
+ id="saas-own-title"
+ className="max-w-xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ Your product data, on your terms.
+ </h2>
+ <p className="mt-6 max-w-xl text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ Rybbit is 100% open source under AGPL v3, with API access and data export on every plan. Start on cloud
+ and self-host later β€” or the other way around β€” and the funnels, cohorts, and profiles come with you.
+ For a product team, that means the analytics layer is a dependency you can read, patch, and pin.
+ </p>
+ </div>
+ <div className="flex flex-col justify-center gap-4 px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <Link
+ href="/docs/self-hosting"
+ className="group inline-flex items-center gap-1.5 rounded-sm text-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Self-hosting guide
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ <Link
+ href="/docs/api/getting-started"
+ className="group inline-flex items-center gap-1.5 rounded-sm text-sm font-medium text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ API documentation
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ <a
+ href="https://github.com/rybbit-io/rybbit"
+ target="_blank"
+ rel="noopener noreferrer"
+ className="group inline-flex items-center gap-1.5 rounded-sm text-sm font-medium text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ Open source on GitHub
+ <ExternalLink
+ className="size-3.5 transition-transform duration-200 group-hover:-translate-y-0.5 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </a>
</div>
</div>
</section>
- <PersonaFaqSection heading="SaaS questions, answered plainly." items={faqItems} />
+ <div id="saas-faq" className="scroll-mt-24">
+ <PersonaFaqSection heading="SaaS questions, answered plainly." items={faqItems} />
+ </div>
<PersonaCrossLinks current="for-saas" />
<CTASection
diff --git a/docs/src/app/[locale]/(home)/for-small-business/page.tsx b/docs/src/app/[locale]/(home)/for-small-business/page.tsx
index 6af8125b8..7f25a7abc 100644
--- a/docs/src/app/[locale]/(home)/for-small-business/page.tsx
+++ b/docs/src/app/[locale]/(home)/for-small-business/page.tsx
@@ -10,7 +10,7 @@ import Link from "next/link";
const pageTitle = "Web Analytics for Small Businesses | Rybbit";
const pageDescription =
- "The handful of numbers your business actually needs β€” visitors, sources, top pages, and goals β€” on one screen you can read in thirty seconds. No GA4 setup, no cookie banner, free to start.";
+ "The handful of numbers your business actually needs β€” visitors, sources, top pages, and goals β€” on one screen you can read in thirty seconds. No GA4 setup, no cookie banner, and a free trial to start.";
export const metadata = createMetadata({
title: pageTitle,
@@ -45,9 +45,9 @@ export const metadata = createMetadata({
// array, so the schema can never drift from the visible answers.
const faqItems = [
{
- question: "Is there really a free plan?",
+ question: "Can I try Rybbit before paying?",
answer:
- "Yes. Rybbit is free for one website up to 3,000 events a month, with no credit card required. When you outgrow it, the Standard plan adds more sites and traffic.",
+ "Yes. Every plan starts with a 7-day free trial with all features included, and you won't be charged until the trial ends. Rybbit is also open source, so self-hosting it yourself is always free.",
},
{
question: "Do I need a cookie consent banner?",
@@ -85,7 +85,7 @@ const numberRows = [
];
const planFacts = [
- { tier: "Free", fact: "1 website, 3,000 events a month, no credit card" },
+ { tier: "Trial", fact: "7 days free, every feature included, cancel anytime" },
{ tier: "Standard", fact: "Up to 5 websites and 3 team members, priced by traffic" },
{ tier: "Pro", fact: "Unlimited websites and team members" },
];
@@ -96,7 +96,7 @@ export default function ForSmallBusinessPage() {
<InteriorPageHero
eyebrow="Rybbit for small businesses"
title="The numbers your business needs. Nothing you don't."
- description="You don't need a data team to know if your website is working. Rybbit puts visitors, sources, top pages, and goals on one screen you can read in thirty seconds β€” no GA4 maze, no cookie banner, free to start."
+ description="You don't need a data team to know if your website is working. Rybbit puts visitors, sources, top pages, and goals on one screen you can read in thirty seconds β€” no GA4 maze, no cookie banner, and a free trial to start."
eventLocation="for_small_business_hero"
/>
@@ -229,14 +229,14 @@ export default function ForSmallBusinessPage() {
id="smb-pricing-title"
className="mt-5 max-w-2xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
- Start free. Upgrade when you grow.
+ Start small. Upgrade when you grow.
</h2>
</div>
</div>
<div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
<p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
- No enterprise sales call, no per-seat surprises. The free plan is genuinely free, and paid plans are
- priced by traffic β€” so you only pay more once your site is actually busier.
+ No enterprise sales call, no per-seat surprises. Every plan starts with a 7-day free trial, and
+ pricing scales by traffic β€” so you only pay more once your site is actually busier.
</p>
</div>
</div>
@@ -309,7 +309,7 @@ export default function ForSmallBusinessPage() {
<CTASection
title="Know if your website is working β€” in thirty seconds."
- description="Free for your first site, no cookie banner, and a dashboard you'll actually open."
+ description="A 7-day free trial, no cookie banner, and a dashboard you'll actually open."
eventLocation="for_small_business_bottom_cta"
/>
</div>
diff --git a/docs/src/app/[locale]/(home)/security/page.tsx b/docs/src/app/[locale]/(home)/security/page.tsx
index 35848d817..94b9b91e2 100644
--- a/docs/src/app/[locale]/(home)/security/page.tsx
+++ b/docs/src/app/[locale]/(home)/security/page.tsx
@@ -76,7 +76,7 @@ export default function Security() {
<h3 className="text-xl font-semibold mt-6 mb-3">Data Deletion</h3>
<p>
- After cancellation or downgrade to free tier, your analytics data will be permanently deleted within 60 days.
+ After cancellation, your analytics data will be permanently deleted within 60 days.
We recommend exporting your data before cancellation if you wish to retain it. Once deleted, data cannot be
recovered.
</p>
diff --git a/docs/src/app/[locale]/(home)/terms-and-conditions/page.tsx b/docs/src/app/[locale]/(home)/terms-and-conditions/page.tsx
index ca2a3cbaa..e1c799af3 100644
--- a/docs/src/app/[locale]/(home)/terms-and-conditions/page.tsx
+++ b/docs/src/app/[locale]/(home)/terms-and-conditions/page.tsx
@@ -95,14 +95,14 @@ export default function TermsAndConditions() {
<h3 className="text-xl font-semibold mt-6 mb-3">Downgrading Your Plan</h3>
<p>
- You may downgrade to a lower-tier plan or the free tier at any time. Downgrades take effect at the end of your
+ You may downgrade to a lower-tier plan at any time. Downgrades take effect at the end of your
current billing period. If your usage exceeds the limits of the downgraded plan, you may need to reduce your
websites or accept data retention limitations.
</p>
<h3 className="text-xl font-semibold mt-6 mb-3">Data After Cancellation</h3>
<p>
- After cancellation or downgrade to free tier, your analytics data will be permanently deleted within 60 days.
+ After cancellation, your analytics data will be permanently deleted within 60 days.
We recommend exporting your data before cancellation if you wish to retain it. Once deleted, data cannot be
recovered.
</p>
diff --git a/docs/src/app/[locale]/(home)/tools/components/ToolCTA.tsx b/docs/src/app/[locale]/(home)/tools/components/ToolCTA.tsx
index 7fd640af8..6f4dd15fc 100644
--- a/docs/src/app/[locale]/(home)/tools/components/ToolCTA.tsx
+++ b/docs/src/app/[locale]/(home)/tools/components/ToolCTA.tsx
@@ -1,7 +1,6 @@
import { ArrowRight } from "lucide-react";
import { GridCrosses } from "@/components/GridCrosses";
import { TrackedButton } from "@/components/TrackedButton";
-import { DEFAULT_EVENT_LIMIT } from "@/lib/const";
interface ToolCTAProps {
title: string;
@@ -24,7 +23,7 @@ export function ToolCTA({ title, description, eventLocation, buttonText = "Start
<div className="relative z-10 flex flex-col justify-center px-5 py-12 sm:px-8 lg:col-span-4 lg:px-10">
<p className="max-w-md text-base leading-7 text-emerald-100/80">
- {description} Get started for free with up to {DEFAULT_EVENT_LIMIT.toLocaleString()} pageviews per month.
+ {description} Start with a 7-day free trial β€” setup takes about five minutes.
</p>
<div className="mt-8">
diff --git a/docs/src/app/[locale]/(home)/white-label/page.tsx b/docs/src/app/[locale]/(home)/white-label/page.tsx
index 7d3ca39f3..317b983ef 100644
--- a/docs/src/app/[locale]/(home)/white-label/page.tsx
+++ b/docs/src/app/[locale]/(home)/white-label/page.tsx
@@ -54,6 +54,21 @@ const faqItems = [
answer:
"Yes. Embed a read-only dashboard with a private-link iframe, or share a dashboard with a secret or public link. Anyone with the link sees that one site's numbers and nothing else β€” no login required.",
},
+ {
+ question: "Can I control what the embed looks like?",
+ answer:
+ "Yes. Choose a light, dark, or system theme, hide the dashboard sidebar to keep viewers on the main page, and the Rybbit footer is removed automatically in embed mode.",
+ },
+ {
+ question: "Is the embedded dashboard live?",
+ answer:
+ "Yes. The embed is the real read-only analytics dashboard served through a private link, so it shows the same up-to-date numbers your team sees β€” it isn't a static export or a cached report.",
+ },
+ {
+ question: "What's the difference between the embed and the API?",
+ answer:
+ "The embed is the fastest path: the full dashboard inside your portal with one iframe. The Stats API returns the raw numbers instead, for teams that want to render their own charts in their own UI. Many start with the embed and move to the API as the product grows.",
+ },
{
question: "Can I build my own reporting UI instead of embedding?",
answer:
@@ -69,6 +84,11 @@ const faqItems = [
answer:
"No. The Pro plan includes unlimited websites under a single subscription, priced by traffic β€” so adding another client site doesn't add another bill.",
},
+ {
+ question: "Can I charge my clients for analytics?",
+ answer:
+ "That's the model. Analytics you resell under your brand is your product at your price β€” Rybbit charges you by traffic, not per client, so the margin math stays yours as the roster grows.",
+ },
{
question: "What does full white-label on Enterprise include?",
answer:
@@ -88,6 +108,29 @@ Authorization: Bearer rb_β€’β€’β€’β€’β€’β€’β€’
{ "visitors": 12408, "sessions": 15230,
"pageviews": 41902, "bounce_rate": 0.38 }`;
+const workflowSteps = [
+ {
+ step: "01",
+ title: "Add the client sites",
+ body: "Every client site lives in your workspace, under one subscription. Unlimited websites on Pro, so the roster can grow without a new bill.",
+ },
+ {
+ step: "02",
+ title: "Generate private links",
+ body: "Each site gets its own private-link key β€” a read-only, scoped route that shows that site's dashboard and nothing else.",
+ },
+ {
+ step: "03",
+ title: "Drop in the iframe",
+ body: "Paste the embed snippet into your portal. Pick light, dark, or system theme, hide the sidebar, and the Rybbit footer disappears on its own.",
+ },
+ {
+ step: "04",
+ title: "Or skip the iframe",
+ body: "Pull the same numbers from the Stats API and render them in your own UI β€” your charts, your components, your brand throughout.",
+ },
+];
+
const labelDepth = [
{
tier: "Embed & share",
@@ -106,6 +149,15 @@ const labelDepth = [
},
];
+const tocItems = [
+ { href: "#wl-problem-title", label: "The problem" },
+ { href: "#wl-workflow-title", label: "The first afternoon" },
+ { href: "#wl-toolkit", label: "Four ways in" },
+ { href: "#wl-depth-title", label: "How far to go" },
+ { href: "#wl-own-title", label: "Owning the stack" },
+ { href: "#wl-faq", label: "FAQ" },
+];
+
export default function WhiteLabelPage() {
return (
<div className="overflow-x-clip">
@@ -116,6 +168,23 @@ export default function WhiteLabelPage() {
eventLocation="white_label_hero"
/>
+ <nav aria-label="On this page" className="border-b border-neutral-200 dark:border-neutral-800">
+ <div className="relative mx-auto flex max-w-[1200px] flex-wrap items-baseline gap-x-6 gap-y-2 border-x border-neutral-200 px-5 py-4 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <span className="text-xs font-medium uppercase tracking-wider text-neutral-400 dark:text-neutral-500">
+ On this page
+ </span>
+ {tocItems.map(item => (
+ <a
+ key={item.href}
+ href={item.href}
+ className="rounded-sm text-sm text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ {item.label}
+ </a>
+ ))}
+ </div>
+ </nav>
+
<section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="wl-problem-title">
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
@@ -129,7 +198,7 @@ export default function WhiteLabelPage() {
<SectionKicker>The branding problem</SectionKicker>
<h2
id="wl-problem-title"
- className="mt-5 max-w-2xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
Clients should see their numbers, not your vendor&apos;s logo.
</h2>
@@ -143,10 +212,103 @@ export default function WhiteLabelPage() {
</p>
</div>
</div>
+ <div className="border-t border-neutral-200 px-5 py-10 dark:border-neutral-800 sm:px-8 lg:px-10">
+ <div className="grid grid-cols-1 gap-10 lg:grid-cols-2">
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ The build-versus-buy math on client analytics is ugly on both ends. Building it in-house is months of
+ chart plumbing that isn&apos;t your product. Reselling a branded third-party tool works β€” until every
+ dashboard you deliver teaches the client which vendor to cut you out for. The missing option is an
+ analytics layer that does the work and stays invisible.
+ </p>
+ <p className="max-w-lg text-base leading-7 text-neutral-600 dark:text-neutral-400">
+ Rybbit is priced to be that layer: unlimited websites on Pro under one traffic-priced subscription, so
+ onboarding the next client doesn&apos;t open the margin conversation again. If you&apos;re running a
+ client roster rather than a product, the{" "}
+ <Link
+ href="/for-agencies"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ agencies page
+ </Link>{" "}
+ covers that workflow β€” and{" "}
+ <Link
+ href="/features/dashboard-sharing"
+ className="font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ dashboard sharing
+ </Link>{" "}
+ shows everything a link or embed can do.
+ </p>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <section className="border-b border-neutral-200 dark:border-neutral-800" aria-labelledby="wl-workflow-title">
+ <div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
+ <GridCrosses />
+ <div className="grid grid-cols-1 lg:grid-cols-12">
+ <div className="relative border-b border-neutral-200 bg-plate-accent px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
+ <div
+ aria-hidden="true"
+ className="pointer-events-none absolute inset-0 bg-graph-accent [mask-image:linear-gradient(to_bottom,black,transparent_92%)]"
+ />
+ <div className="relative">
+ <SectionKicker>The first afternoon</SectionKicker>
+ <h2
+ id="wl-workflow-title"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ >
+ Branded analytics in your portal, in four steps.
+ </h2>
+ </div>
+ </div>
+ <div className="flex items-end px-5 py-10 sm:px-8 md:py-20 lg:col-span-5 lg:px-10">
+ <p className="max-w-md text-lg leading-8 text-neutral-600 text-pretty dark:text-neutral-400">
+ No SDK integration project, no data pipeline. The embed path is an iframe and a private link β€” the API
+ path is one bearer key more.
+ </p>
+ </div>
+ </div>
+ <div className="grid grid-cols-1 gap-px border-t border-neutral-200 bg-neutral-200 p-px dark:border-neutral-800 dark:bg-neutral-800 sm:grid-cols-2 lg:grid-cols-4">
+ {workflowSteps.map(item => (
+ <article key={item.step} className="bg-white px-5 py-8 dark:bg-neutral-950 sm:px-6">
+ <span className="font-mono text-xs text-neutral-400 dark:text-neutral-500">{item.step}</span>
+ <h3 className="mt-3 text-base font-semibold tracking-tight">{item.title}</h3>
+ <p className="mt-2 text-sm leading-6 text-neutral-600 dark:text-neutral-400">{item.body}</p>
+ </article>
+ ))}
+ </div>
+ <div className="flex flex-wrap items-center gap-x-6 gap-y-3 border-t border-neutral-200 px-5 py-5 text-sm dark:border-neutral-800 sm:px-8 lg:px-10">
+ <Link
+ href="/docs/embeds/dashboard"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-emerald-700 transition-colors duration-200 hover:text-emerald-600 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-emerald-500 dark:text-emerald-400 dark:hover:text-emerald-300"
+ >
+ Dashboard embed docs
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ <Link
+ href="/docs/api/getting-started"
+ className="group inline-flex items-center gap-1.5 rounded-sm font-medium text-neutral-600 transition-colors duration-200 hover:text-neutral-950 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-500 dark:text-neutral-400 dark:hover:text-white"
+ >
+ API getting started
+ <ArrowRight
+ className="size-3.5 transition-transform duration-200 group-hover:translate-x-0.5 motion-reduce:transition-none"
+ aria-hidden="true"
+ />
+ </Link>
+ </div>
</div>
</section>
- <section className="border-b border-neutral-200 dark:border-neutral-800" aria-label="White label options">
+ <section
+ id="wl-toolkit"
+ className="scroll-mt-24 border-b border-neutral-200 dark:border-neutral-800"
+ aria-label="White label options"
+ >
<div className="relative mx-auto max-w-[1200px] border-x border-neutral-200 dark:border-neutral-800">
<GridCrosses />
<div className="grid grid-cols-1 gap-px bg-neutral-200 p-px dark:bg-neutral-800 lg:grid-cols-12">
@@ -244,7 +406,7 @@ export default function WhiteLabelPage() {
<SectionKicker>How white is your label?</SectionKicker>
<h2
id="wl-depth-title"
- className="mt-5 max-w-2xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ className="mt-5 max-w-2xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
Go as far as your brand needs.
</h2>
@@ -297,7 +459,7 @@ export default function WhiteLabelPage() {
<div className="border-b border-neutral-200 px-5 py-14 dark:border-neutral-800 sm:px-8 lg:col-span-7 lg:border-b-0 lg:border-r lg:px-10 md:py-20">
<h2
id="wl-own-title"
- className="max-w-xl text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
+ className="max-w-xl scroll-mt-24 text-4xl font-semibold leading-[1.04] tracking-[-0.035em] text-balance md:text-5xl"
>
Own the whole stack.
</h2>
@@ -334,7 +496,9 @@ export default function WhiteLabelPage() {
</div>
</section>
- <PersonaFaqSection heading="White-label questions, answered plainly." items={faqItems} />
+ <div id="wl-faq" className="scroll-mt-24">
+ <PersonaFaqSection heading="White-label questions, answered plainly." items={faqItems} />
+ </div>
<PersonaCrossLinks current="white-label" />
<CTASection
diff --git a/docs/src/components/LandingPageTemplate.tsx b/docs/src/components/LandingPageTemplate.tsx
index 638f9e253..8841b4766 100644
--- a/docs/src/components/LandingPageTemplate.tsx
+++ b/docs/src/components/LandingPageTemplate.tsx
@@ -172,9 +172,11 @@ export function LandingPageTemplate({ title, subtitle, showEUFlag = true }: Land
},
];
+ // Note: only include tweets whose claims about the product are accurate
+ // (e.g. no "free plan/tier" tweets β€” Rybbit has a trial, not a free tier).
const tweetColumns = [
- ["1991296442611184125", "1921928423284629758", "2000974573005889706", "1927817460993884321", "1977471983278535071"],
- ["1920899082253434950", "2000788904778326334", "2015102995789381815", "1980082738934993142", "1976495558480232672"],
+ ["1991296442611184125", "1921928423284629758", "2000974573005889706", "1927817460993884321"],
+ ["1920899082253434950", "2000788904778326334", "1976495558480232672", "1977471983278535071"],
["1982378431166963982", "2009548405488615871", "1920470706761929048", "1979830490006974510", "1970265809122705759"],
];