If you run a small SaaS or a couple of indie sites, you probably check three or four dashboards to answer one question: did that change make us money? Traffic sits in one tool, payments in Stripe, errors in another, and page speed in a fourth you open twice a year. Raah.dev tries to put all of that behind a single script and a single screen. It appeared on Product Hunt's 1 November 2026 leaderboard with the tagline "Track your revenue, analytics, and website performance". Here is what it does, what it costs, and whether it deserves a place in your stack.
What it is
Raah describes itself as "revenue analytics and real-user observability for humans and AI agents". In plain words, it is a website analytics tool that also watches how fast and how reliably your site behaves for real visitors, and then ties both to the money you take. Real-user observability means measuring what actual visitors experience (slow pages, failed requests, JavaScript errors) rather than running synthetic tests from a server somewhere. You add one script tag to your site, and that same beacon collects visits, page speed and request timings together.
The pitch for a small business is simple. When signups drop on a Tuesday, you want to know in one place whether traffic fell, checkout broke, or the pricing page got slow on mobile connections in one country. Raah is built to make that a single lookup.
Who it's for
The clearest fit is a solo founder or tiny team running one to five small products: a SaaS with a Stripe checkout, a paid newsletter site, a template shop, a side project with a waitlist. You care about revenue first, you have no ops person, and you do not want to stitch four tools together or pay for four subscriptions.
It is a weaker fit if you already have a working analytics and error-monitoring setup you trust, if you need deep session replay or feature flags, or if your alerts must land in Slack today. More on that below.
What it actually does
Every feature below is taken from Raah's own "Why Raah" documentation and product pages. I have not run it on a production site, so treat these as the company's claims.
Product analytics. It says it tracks "pageviews, visits, journeys, referrers, UTM campaigns, devices, geography, custom events, and revenue". That covers the usual questions: where people came from, which pages they saw, and which campaign brought them.
Revenue, including Stripe. You paste a restricted, read-only Stripe key into project settings. According to the revenue docs, Raah then backfills 90 days of payments and checks for new ones about every five minutes, with no webhook to set up. If you use Paddle, Lemon Squeezy, Polar, Razorpay or your own checkout, your server posts each confirmed payment to Raah instead. Your success page then calls a small browser function with the order ID, and Raah matches the payment to the visit, which lets it credit the money to a channel, campaign, landing page and country.
Core Web Vitals. These are standard measures of how a page feels to load and use: LCP (how fast the main content appears), INP (how quickly the page responds to a tap), CLS (how much the layout jumps around) and TTFB (how fast the server answers). Raah says it shows "LCP, INP, CLS, and TTFB distributions from actual sessions, not lab runners", broken down by device type, browser and region.
API latency and errors. It reports request volume, latency at p50/p95/p99, errors, third parties, ISPs and geography "from actual visitors". p95 means the speed that 95% of requests beat, so it shows what your slowest everyday customers feel rather than the average. It also catches JavaScript errors and unhandled promise rejections.
Alerts. You set thresholds on latency, error rate, volume, active users and more, "delivered by email or compatible webhooks". The pricing page also lists uptime monitors on paid plans.
Status pages. A public page showing your components, incidents and selected metrics. Every plan gets a hosted page; a custom domain such as status.yoursite.com needs Premium.
MCP server. MCP (Model Context Protocol) is the standard way AI coding assistants connect to outside tools. Raah's MCP docs say Cursor, Claude, Claude Code and OpenAI Codex can connect, read your telemetry, and (if you allow it) create projects. The docs also note that "MCP has limited availability", so expect gaps.
A light, cookie-free script. The features page calls the script "lightweight, deferred" and says it sets "no analytics cookies", using browser storage for random visitor IDs instead. Raah does not publish a script size, so I cannot confirm any figure. Its collected-data page is candid that "cookie-free does not remove applicable consent requirements", so you still owe visitors a privacy notice and, where the law requires it, a consent prompt.
Pricing (as of 3 Nov 2026)
These are the monthly prices shown on Raah's pricing page on 3 November 2026. A yearly toggle exists, but no yearly prices were displayed.
Plan | Price | Sites | Requests / events per month | Data kept | Extras |
|---|---|---|---|---|---|
Free | $0 | 1 | 100,000 / 100,000 | 30 days | 10 AI messages, hosted status page, 1 alert recipient |
Pro | $9/month | 5 | 1,000,000 / 1,000,000 | 90 days | 100 AI messages, 3 uptime monitors, webhooks, hide Raah branding, 3 alert recipients |
Premium | $25/month | 10 | 5,000,000 / 5,000,000 | 365 days | 500 AI messages, 10 uptime monitors, custom status domain, 5 alert recipients |
"Requests" are the network calls the beacon records; "events" are pageviews and the custom actions you track. As a rough estimate, a site with 20,000 visitors a month viewing four pages each sits near 80,000 events, which fits the free plan. Once you run two or three products, Pro at $9 is the natural tier.
Getting started
The quickstart says installation takes "under a minute". The steps are short:
Create a project for your public domain, for example example.com. Raah shows you a script snippet with your project ID.
Paste the script tag into the shared layout or document head of your site, so it loads on every page. There are guides for Next.js, React, Astro and WordPress.
Check that the domain in the snippet matches the project's saved domain exactly, or Raah rejects the traffic.
Open your browser's developer tools, go to the Network tab, filter by "raah.dev" and reload. You should see a request to t.raah.dev.
Connect revenue. For Stripe, create a restricted read-only key and paste it into project settings. For other providers, add a server-side post after each confirmed charge.
On your thank-you page, call the conversion function with the order ID so each payment links back to the visit that produced it.
Set two alerts to start: error rate on your checkout API and p95 latency on your signup endpoint, both sent to email.
A useful first test: after a week, open the revenue view by landing page and ask which page earns the most per visitor. That one number tells you where to send your next hour of marketing. If you also use a coding agent, our review of Faylee, which turns bug reports into something your coding agent can fix, pairs well with Raah's MCP connection.
Alternatives
Plausible is the pick if you only want simple, privacy-friendly traffic numbers and nothing else. Its Starter plan is $9 a month for one site and up to 10,000 monthly pageviews, and the page lists ecommerce revenue attribution only on its Business plan. Choose it when you want clean, mature analytics and do not need speed or error data.
PostHog is the pick if you are building a product and want depth: session replay, feature flags, experiments and error tracking. Its free tier includes 1 million analytics events and 100,000 exceptions a month. Choose it when you have the time to set it up properly and expect to grow into its extra tools.
Sentry is the pick if errors and performance are your main worry and analytics live elsewhere. It has a free Developer plan, and its Team plan costs $29 a month billed monthly. Choose it when you have a real backend, several developers, and need detailed stack traces.
If your bigger question is where visitors come from in the first place, including AI chat assistants, our review of Bear and AI chat traffic covers that angle.
Limitations
No native Slack alerts yet. The pricing page marks Slack as "Upcoming" on Pro and Premium, and the docs say the integration "is not ready for launch". For now you get email or webhooks.
It is new. Raah launched on Product Hunt on 1 November, so there is little independent track record on accuracy, uptime or support.
The MCP server is limited. Raah itself says it has "limited availability", and its MCP overview does not name individual tools.
Revenue needs some code. Stripe sync is easy, but exact attribution needs a conversion call on your success page, and other payment providers need a server-side post.
Breadth over depth. One tool covering six jobs will not match a specialist in each. Expect lighter error detail than Sentry and fewer analysis features than PostHog.
Consent still applies. Cookie-free does not mean consent-free, as Raah's own docs point out.
Verdict
Try it if you run a few small SaaS or indie sites and want revenue, traffic and speed in one cheap view. Skip it if you already pay for PostHog or Plausible plus Sentry. The free plan is enough to test it on one site for a month, and the decision rule is plain: if you open Raah more often than your other dashboards after two weeks, move up to Pro and cancel what it replaces. One small caution: if your team lives in Slack, wait until native alerts ship or route webhooks there yourself.
