Runlight vs PostHog
PostHog is a product analytics platform with replays, feature flags, experiments, and surveys, free for a million events a month. Runlight does web analytics only, without cookies, and runs inside your own app for free at any size.
PostHog and Runlight answer different questions. PostHog helps a product team understand what known users do inside an app, with replays, feature flags, experiments, and surveys around one stream of events. Runlight tells you how many people visit a site, where they came from, and what they read, without knowing who anyone is.
Choose
The short answer
Choose Runlight if
- You want web analytics for a site, with one page of numbers anyone can read
- You want no cookies and no identifier that lasts past a day, with nothing to configure
- You want to self-host on SQLite or the database your app already uses, at any traffic
- You want short links on your own domain, or a WordPress, Drupal, or Craft plugin
Choose PostHog if
- You build a product and want to follow signed-in users through it
- You want session replay, feature flags, A/B tests, surveys, or error tracking alongside analytics
- You want a hosted platform with a generous free allowance and nothing to run
At a glance
At a glance
| Runlight | PostHog | |
|---|---|---|
| Price | Free | Free for 1 million analytics events a month, then priced per event |
| Open source | Yes, MIT | Yes, MIT, apart from its ee directory |
| Self-hosted | Yes, in your app or as one server | Partly. A hobby deploy that PostHog does not support, for about 100,000 events a month |
| What self-hosting needs | Your app’s database, or one process with SQLite | 4 CPUs and 16 GB of memory, with ClickHouse, Kafka, Postgres, and Redis |
| Hosted option | Not yet. Interested? Email us | Yes, in the US or the EU |
| Without cookies | Yes | Partly. An id is kept for 365 days by default, and a cookieless mode is an option |
| Visitor identifier | A daily hash, gone after a day | A cookie, or a daily hash in cookieless mode |
| Identify known users | No | Yes |
| Web analytics dashboard | Yes | Yes |
| Funnels and journeys | Yes | Yes |
| Revenue | Yes, from goal values and events you send | Yes, with payment platform connections |
| AI referrals as a channel | Yes | Yes |
| AI crawler fetches | Yes, from your app, a CMS plugin, or access logs | Partly, from server logs you forward, in alpha |
| Short links | Yes, on your own domains | Not found in its docs |
| Session replay, heatmaps, flags, experiments, and surveys | No | Yes |
| Share a dashboard by link | Yes | Yes |
| Email reports | Yes, weekly or monthly | Yes. Up to 5 subscriptions on the free plan, and none when self-hosted |
| API and MCP server | Yes | Yes |
| Assistant in the dashboard | Yes, with your own AI provider | Yes, PostHog AI, with 500 free credits a month |
| Team access control | Owner, admin, member, and viewer, once accounts are turned on | Project access from US$250 a month, and roles on Enterprise |
| CMS plugins | WordPress, Drupal, and Craft | Install guides. WordPress uses a snippet or Tag Manager |
| Script size | Under 2 KB gzipped | Not published by PostHog |
Runlight
Where Runlight is better
Made for web analytics
Runlight is a dashboard for a website, with visitors, sources, pages, places, goals, and the live view on one page. PostHog’s web analytics sits inside a much larger product made for app teams, with more to learn and set up.
No cookies, with nothing to turn on
PostHog’s JavaScript library keeps an id in a cookie and local storage for 365 days, unless you turn on its cookieless mode in both the code and the project settings. Runlight sets no cookies at all, and counts a visitor with a hash whose salt is deleted after a day.
Self-hosting that is supported and small
Runlight runs inside your app on its own database, or as one server with SQLite, at any traffic. PostHog says its self-hosted deploy is unsupported, needs 4 CPUs and 16 GB of memory, and suits about 100,000 events a month.
Free at any size
Runlight is free for any number of events, sites, and people. PostHog’s free plan stops collecting at a million events, and pay-as-you-go prices each event after that.
AI agents that read your pages
AI agents such as GPTBot and ClaudeBot fetch pages without running JavaScript. Runlight counts them through its libraries, its CMS plugins, or your access logs. PostHog’s crawler report is in alpha and needs server logs forwarded to it.
Short links and CMS plugins
Runlight makes short links on your own domains and counts each click, and has plugins for WordPress, Drupal, and Craft that count AI agents where pages are served.
PostHog
Where PostHog is better
Many tools on one stream of events
PostHog puts product analytics, session replay, feature flags, experiments, surveys, error tracking, and a data warehouse on the same events, so you can go from a funnel to a replay of a visit that dropped out. Runlight does web analytics only.
Following known users
PostHog can identify signed-in users and follow them across visits, with person profiles, cohorts, retention, and SQL. Runlight never keeps an identifier past a day, so it cannot follow anyone.
Hosted, with a generous free plan
PostHog Cloud runs in the US or the EU and includes a million analytics events, 5,000 recordings, and a million feature flag requests free every month. Runlight is self-hosted only.
An MCP server that can act
PostHog’s hosted MCP server can query data and take actions, such as shipping a feature flag. Runlight’s MCP server reads reports.
Switching
Moving from PostHog to Runlight
Install Runlight in your app, or start the standalone server, and add Runlight’s script tag. If you use PostHog only for web analytics, you can remove its snippet. What to expect:
- PostHog’s history does not come across directly. Runlight takes a CSV in its own format, with a row for each pageview, so a script can convert an export you already have.
posthog.capture("signed_up")becomesrunlight("signed_up"), and its conversion goals become Runlight goals.- Identified users, replays, flags, and experiments have no place in Runlight, so keep PostHog for those if you need them.
Questions
Questions
Can I use Runlight and PostHog together?
Yes. Many teams use web analytics for the public site and product analytics for the signed-in app. Runlight on the marketing pages sets no cookies, so it adds nothing to a consent banner.
Is PostHog cookieless?
Not by default. Its JavaScript library stores an id in a cookie for 365 days. PostHog offers a cookieless mode that counts visitors with a daily hash, with fewer features. Runlight works that way from the start.
Can I self-host PostHog?
PostHog offers a hobby deploy under the MIT license. It says self-hosted deployments are officially unsupported, and that the hobby deploy suits about 100,000 events a month. Runlight is built to be self-hosted at any size.
Is Runlight really free?
Yes. Runlight is open source under the MIT license, with no paid plan. You pay only for wherever you run it.
Sources
Sources
Checked on 8 November 2026, from PostHog’s own pages:
- Pricing
- Prices behind the pricing calculator
- Platform packages
- Self-hosting
- Self-hosting disclaimer
- The repository
- Persistence and cookies
- Data collection and cookieless mode
- Cookieless tracking
- Data storage
- Web analytics
- Channel types
- Bot detection
- Sharing
- Subscriptions
- MCP
- Access control
- WordPress
And for Runlight, the documentation and how Runlight counts.
Runlight is free, open source, and runs inside the app you already have.