Brands I back / PostHog

Open source product analytics: events, session replay, feature flags, A/B tests and surveys in one platform, with a real free tier.

PostHog is an open source product analytics platform. It covers event analytics, session replay, feature flags, A/B testing, surveys and error tracking in one product, on one data model. You can use their cloud or self host it, and the free tier covers around a million events a month before any payment is required.

The company launched in 2020 through Y Combinator and develops the whole platform in the open; the code is public on GitHub. One snippet feeds every tool, so a funnel, the replay of the sessions inside it and the flag that fixes the problem all live in the same place, joined on the same user.

What earned it a page here is the consolidation. Analytics, replays, flags and experiments usually mean three or four subscriptions, as many SDKs, and identity stitching between them. Replacing that stack with one product removes integration work that nobody bills for but everybody pays. Pricing is usage based, billing limits can be capped from the dashboard, and the free tier is large enough that a small product can run on it for a long time.

Save months.

Products, marketing, tools: I test a lot, sum up what works, you avoid my mistakes.

Build articles

An OpenClaw alternative is worth switching to only if it keeps the part you wanted, an agent that acts while you are asleep, and drops the part that should worry you, one always-on assistant holding every credential you own. Three shapes are on offer: another general assistant, a self-hosted workflow runner, or a narrow agent with a scheduled trigger and a single exit door.

Marketing articles

LinkedIn's Post Inspector, at linkedin.com/post-inspector, reads a URL the way LinkedIn's crawler does and clears the preview LinkedIn had stored for it, so your next share picks up the tags currently on the page. That is the whole job: it refreshes, it does not validate. When the preview is still wrong after you run it, the cache was never the problem. The image you shipped is.

Follow up on a cold email only when you can add one fact that did not exist when you sent the first one. Not a bump, not a polite reminder that you are still waiting: something the reader did not know before. Two follow-ups written that way beat six written in advance, because a sequence drafted before you send can only ever report that time has passed.

Projects