# Lampwick vs PostHog for product analytics > PostHog is a product analytics suite with autocapture, replay and flags. Lampwick monitors your app and adds funnels from its requests. Verified 12 Nov 2026. We make Lampwick. Here's where each tool is the better pick. These are different tools that overlap in one place. PostHog is a product analytics suite: autocapture in the browser and mobile apps, events you name, session replay, feature flags and experiments, plus error tracking and logs. Lampwick is application monitoring (errors, requests, jobs, uptime) that also gives you active users, retention and funnels from the requests it already receives. If product analytics is the job, PostHog is the stronger tool. If monitoring is the job and you'd like to see what errors and deploys do to your signed-in users, Lampwick covers that without a second tool. Last reviewed 12 Nov 2026. Competitor facts come from the vendor's own pages, linked in the footnotes and verified on 2026-11-12. ## Data, analytics features and prices side by side | | Lampwick | PostHog | |---|---|---| | What it is | Application monitoring, with product analytics of signed-in users from the same data | Product analytics suite with replay, flags, experiments, surveys, error tracking and logs[^ph-pricing] | | How data gets in | The requests and exceptions your monitoring already sends | A JavaScript or mobile SDK with autocapture, or `capture` calls with event names you choose; server SDKs for Node.js, Python, PHP, Ruby, Go, Java and more[^ph-capture] | | Who is counted | Signed-in users only | Anonymous and identified users[^ph-capture] | | Funnel steps | Server routes, such as `POST /checkout`, and custom events your server sends; browser page views and events only as anonymous counts | Events, pageviews filtered by URL, or actions[^ph-funnels] | | Insights | Active users, stickiness, weekly retention, funnels, user paths, usage per route | Trends, funnels, paths, stickiness, lifecycle, retention, SQL[^ph-analytics] | | Errors next to conversion | Per funnel step: how users who hit an error or a slow response went on; conversion by deploy; users an issue hit and who came back | Error tracking is a separate product in the same platform[^ph-pricing] | | Session replay | No | Yes, 5K recordings a month free[^ph-pricing] | | Feature flags, experiments | No | Yes, 1M flag requests a month free[^ph-pricing] | | Uptime, SSL, domain, cron | Yes | Not on the pricing page[^ph-pricing] | | Price model | Per team per month, by events; analytics included ([all plans](/pricing/)) | Per product by usage; first 1M analytics events a month free, then from $0.00005 per event[^ph-pricing-md] | | History | Records 3 to 60 days by plan; user activity 30 days to 13 months | Events 1 year on free, 2 years on pay-as-you-go, longer with platform packages[^ph-pricing] | | Data location | EU | US or EU cloud[^ph-pricing] | | MCP | Yes, OAuth or a personal token | Yes, at `mcp.posthog.com`, sign in with your PostHog account[^ph-mcp] | ## How the data gets in PostHog's web SDK captures pageviews, clicks, inputs and form submissions by default, and you add `posthog.capture('user_signed_up')` for events of your own. Backend-only setups send events, including `$pageview`, with a server SDK.[^ph-capture] PostHog also has a PHP SDK and an experimental Laravel SDK.[^ph-php] By default Lampwick adds nothing to your app for analytics. The [Laravel package](/docs/laravel/), [OpenTelemetry](/docs/opentelemetry/) or [HTTP ingest](/docs/http-ingest/) already send each request with the signed-in user to monitor it, and Lampwick counts users, retention and funnels from those: nothing to name, nothing to keep in sync with your code. If you want more, send custom events from your server with the user id. The [browser script](/docs/browser/#custom-events-and-page-views) can count page views and custom events (`lampwick.track(...)`) too, as anonymous totals: no cookies, nothing stored in the browser, so [no consent banner for Lampwick's analytics](/legal/dpa/#analytics-and-your-users-devices). The cost of that: Lampwick only sees what reaches your server, plus what you send it on purpose. Clicks and scrolls are never captured on their own, and an anonymous visitor on your landing page only counts, never as a person. ## Who wins on each topic ### Anonymous visitors and marketing: PostHog wins PostHog counts anonymous and identified users, and its web SDK captures pageviews by default.[^ph-capture] Lampwick counts signed-in users only, because a request needs a user id to be followed to the next one. For a signup funnel that starts on a public page, use PostHog. ### Autocapture and custom events: PostHog wins PostHog autocaptures interactions on the web and in some mobile SDKs, and takes any event you name, with properties to break funnels down by.[^ph-autocapture] Lampwick takes custom events too, but only the ones you send, with up to 20 properties, followed per user only when your server sends them, and without breakdowns by property ([custom events and page views](/docs/funnels/#custom-events-and-page-views)). It has no autocapture. ### Session replay, feature flags and experiments: PostHog wins PostHog has all three, each with a monthly free allowance.[^ph-pricing] Lampwick has none of them. ### Funnel analysis: PostHog, for depth PostHog funnels break down by event and person properties and cohorts, and its correlation analysis highlights what affects conversion; from a funnel you can open the sessions of users who dropped off.[^ph-funnels] Lampwick funnels have 2 to 8 route steps with a conversion window, and per step the users, conversion, drop-off and median time. ### What errors and deploys do to users: Lampwick wins, for signed-in users This is where Lampwick's analytics come from: the same data as your errors. Per funnel step it compares users who hit a server error, an exception or a slow response with everyone else, lists the issues on the step that loses the most users and groups conversion by deploy. Every issue shows how many users it hit and how many came back ([impact of an issue](/docs/users/#impact-of-an-issue)). On Team and up, a [funnel alert](/docs/funnels/#funnel-alerts) tells you when a step's conversion drops, with the deploy and the top issue on that step. PostHog has error tracking in the same platform;[^ph-pricing] we haven't found these per-step error comparisons in its funnel docs.[^ph-funnels] ### Monitoring: Lampwick wins Lampwick tracks requests with p95, queued jobs, queries and logs, and checks uptime, SSL certificates, domains, DNS and the scheduler, with [status pages](/docs/status-pages/) from Pro. Uptime and cron checks aren't on PostHog's pricing page.[^ph-pricing] ### History: PostHog wins PostHog keeps events 1 year on its free plan and 2 years on pay-as-you-go.[^ph-pricing] Lampwick keeps a user's active days for 30 days on Free, 90 on Pro and 13 months on Team and Business, and the requests funnels are built from for 3 to 60 days. ### Price: depends on what you need PostHog's free tier covers 1M analytics events, 5K recordings and 1M flag requests a month, with 1 project; pay-as-you-go raises that to 6 projects.[^ph-pricing] Lampwick's analytics are part of every plan and count no extra events, because they read requests you already send; funnels per project are 1 on Free, 3 on Pro, 20 on Team and unlimited on Business. You'd pay Lampwick for monitoring, not for analytics. ### MCP: tie Both have a hosted MCP server. PostHog's runs HogQL queries, manages feature flags and experiments, and works with its error tracking.[^ph-mcp] Lampwick's has `findDropOffs`, `getFunnel`, `getRetention` and `getIssueImpact` next to the monitoring tools ([MCP](/docs/mcp/)). ## Using both They don't exclude each other. PostHog for the marketing site, anonymous visitors, replay and flags; Lampwick for errors, uptime and what an error or a deploy does to signed-in users in your app. ## When to pick PostHog instead - You need to count anonymous visitors, such as a landing page or signup funnel. - You want autocapture, events you analyze by their properties, session replay, feature flags or A/B tests. - You want more than a year of event history, or SQL on your events. - You need funnels on clicks or screens in a mobile app, or on anonymous visitors. Read how Lampwick does it: [users, active users and retention](/docs/users/), or [Start free](https://app.lampwick.dev/signup). ## Try it with your agent Paste this into Claude Code, Cursor or Codex, in your app's repository: ```text Set up Lampwick monitoring for this app. Read https://lampwick.dev/docs/agents.md and follow it. Keep the tokens out of the chat, use a dev or staging environment, and give me the claim link when the first event has arrived. ``` The agent creates a trial workspace without an account and connects your app. You claim it from the link it gives you and choose what the agent may keep: [how it works](/docs/agents/). [^ph-pricing]: [PostHog pricing](https://posthog.com/pricing), verified on 2026-11-12. [^ph-pricing-md]: [PostHog pricing, per-unit rates](https://posthog.com/pricing.md), verified on 2026-11-12. The first paid tier is $0.00005 per event for 1M to 2M events a month; identified events cost more. [^ph-capture]: [PostHog: capturing events](https://posthog.com/docs/product-analytics/capture-events), verified on 2026-11-12. [^ph-autocapture]: [PostHog autocapture](https://posthog.com/docs/product-analytics/autocapture), verified on 2026-11-12. [^ph-php]: [PostHog PHP SDK](https://posthog.com/docs/libraries/php), verified on 2026-11-12. [^ph-funnels]: [PostHog funnels](https://posthog.com/docs/product-analytics/funnels), verified on 2026-11-12. [^ph-analytics]: [PostHog product analytics docs](https://posthog.com/docs/product-analytics), verified on 2026-11-12. [^ph-mcp]: [PostHog MCP server](https://posthog.com/docs/model-context-protocol), verified on 2026-11-12.