mrkr vs PostHog.
PostHog is a platform: analytics, replay, flags, experiments, surveys, warehouse. mrkr is one tool that answers where the traffic came from and what it did. Both are legitimate choices, for different teams.
In short
What is the difference between mrkr and PostHog?
PostHog is a product-analytics platform bundling analytics, session replay, feature flags, experiments, surveys, and a data warehouse. mrkr is a single privacy-first web analytics tool with session replay, funnels, and revenue attribution built in. PostHog is broader and heavier. mrkr is cookieless by default and narrower on purpose.
Nobody should choose between these on a feature count, because PostHog wins that count outright. The real question is whether a platform is something your team will operate. PostHog rewards an owner. Without one it becomes ten configured-but-unused products and a bill.
One screen instead of ten products.
Visitors, sources, pages, goals, and revenue on one range, with no project switcher and no module to enable first. That is a smaller surface than PostHog on purpose. If the surface is what you want, take PostHog.
Where mrkr is better.
Cookieless by default
PostHog's identity model assumes cookies. mrkr uses a rotating salted hash and writes nothing persistent.
Weight
Under 6 kB against a PostHog bundle carrying replay, flags, and surveys.
Traffic and revenue together
Referrers, campaigns, and AI assistants are classified for you, with revenue attached.
Nobody has to own it
A script tag and a dashboard. That is the entire operational commitment.
Compared
Side by side.
| Feature | mrkr | PostHog |
|---|---|---|
| Category | Privacy analytics with replay | Product analytics platform |
| Session replay | On every paid plan | Yes |
| Heatmaps | No | Yes |
| Funnels | Yes | Yes |
| Saved cohorts | No | Yes |
| Revenue attribution | Yes | Yes |
| Cookieless | By default (optional cookie mode) | Optional, cookies by default |
| Free plan | No, $1 for 14 days | A large monthly free allowance |
| Entry paid price | $5/mo, 100K pageviews, session replay included | Usage-based, Generous free tier, then per-event pricing |
| Feature flags | No | Yes |
| A/B experiments | No | Yes |
| On-site surveys | No | Yes |
| Data warehouse | No | Yes |
| Tracker size | Under 6 kB gzipped | Grows with the modules you enable |
| Setup surface | One script tag | A platform to configure |
PostHog details checked against the vendor's own pricing and feature pages on 2026-08-24. Where a vendor does not publish a fixed list price, this table says how they charge rather than guessing a number. Vendors change packaging often, so confirm before you buy.
Live demo
The whole product, in one demo. Every mrkr feature runs on the live demo dataset. It takes about a minute to see whether the narrower surface is the one you want.
Open the live demoWhere PostHog is genuinely better.
Feature flags and experiments
Ship behind a flag and measure it in the same tool. mrkr has no equivalent at any price.
The free tier
A large monthly allowance across its products. For a pre-revenue project that is hard to argue with.
Warehouse and SQL access
Query the raw data and join it to other sources. mrkr has no query API and no self-serve export; we pull your data for you on request.
FAQ
Is mrkr a PostHog replacement?
Only for the analytics and replay part. PostHog also ships feature flags, A/B experiments, surveys, and a data warehouse. mrkr has none of those and is not planning to. If you adopted PostHog for flags, mrkr does not replace it.
Is PostHog free?
PostHog has a large monthly free allowance across its products, which is genuinely generous and is the main reason small teams pick it. Above that allowance it prices per event and per recording, and bills can grow quickly on a busy site.
Does PostHog need a cookie banner?
By default yes, because it sets cookies to identify users. It can be configured to run without them, at the cost of the identity model that most of the platform assumes. mrkr is cookieless by default with cookie mode as an optional per-site setting.
Which is lighter on the page?
mrkr, by a wide margin. The mrkr tracker is under 6 kB gzipped. A PostHog bundle grows with the modules you switch on, because flags, surveys, and replay all ship client-side code.
Why would a team move from PostHog to mrkr?
Usually because they only ever used the web analytics and the replay, the interface presented ten products when they wanted one, and nobody on the team wanted to own the configuration. That is a real pattern, and it is also an argument for keeping PostHog if someone does own it.
Start with one line of HTML.Your first visitors show up within a minute.