PostHog VS Metabase

Posthog is pretty good but very pushy towards using their SaaS (understandably). Self hosting is not really advertised on their main site however is buried in their gh repo as a footnote [1] with indications of vague issues past 100K events/month. Haven’t delved into how to scale it past that though and they do provide some docs that I have yet to review.

Also the primary repo is not FOSS, and that "100% FOSS" repo is buried in yet another footnote [2].

Plausible follows in PH footsteps but is not fully faithful to open source. If you want to self host, you won’t have same set of features as their SaaS and need to rely on long term releases for their "community edition" [3]

On "Ahrefs", is there even an open source version of their product? I couldn’t easily find it (on mobile). [4]

Maybe I’ll take a look at others you mentioned later but if rybbit can remain faithful to their FOSS roots then I think there’s a real chance of it becoming huge.

For thosw that don’t want to self host (mostly corporate shitholes), rybbit can milk them with their managed SaaS product.

[1] https://github.com/PostHog/posthog?tab=readme-ov-file#self-h...

[2] https://github.com/PostHog/posthog?tab=readme-ov-file#open-s...

[3] https://github.com/plausible/analytics?tab=readme-ov-file#ca...

[4] https://ahrefs.com/

I'm unable to see their website

https://posthog.com

Is it just me?

Website link: PostHog

Send events to analytics tools like PostHog.

For SaaS startups looking for a powerful, privacy-conscious analytics platform, PostHog provides an all-in-one solution designed for modern product teams.

The next rung up are User recordings. For users that are having issues, we have concrete recorded data for their flow. The flows would include anything relevant to the application, how they used it, what actions they took. All so we can actually see what happened in context for when there is a problem. No one wants to spend any time looking at recordings if they don't have to. It is also very difficult to identify the root cause of problems by reviewing a recording, but having them is indispensable to your support engineers when they need them, when a user has reported a issue. Solutions include PostHog, FullStory, Sentry. If you don't have these recordings, then the next best alternative (which is very far away) is getting a live screencast from the user. These are less useful, and more expensive to obtain. Worst of all, they can and have been used to breach sensitive systems.

Posthog. Posthog has a lot of sub products but I use it mainly for analytics and session replays. I have to say Posthog is an impressive product. Everything from dev experience to dashboards is just awesome. Great to see GA finally got some real competition. I'm looking forward to try all the other products from them.

Visit Posthog Website and signup to create your account using either email, google, or github etc.

We use tools like Posthog to measure how users are using our products. This allows us to see what features are being used and which ones are not.

I've found the Metabase test suite[0] to be very good considering it's real-world software written by a for-profit company. Coverage is good, the correct tests usually break when doing a refactor (stuff like "Oh, I thought this change was harmless but actually it breaks the permissions model"), etcetera. But the most important thing is that there's a strong team culture of a) demanding good tests on each PR b) hunting down flaky tests and other sources of friction.

Another neat thing was that there used to be a full-time SDET who spent a lot of time writing Cypress reproductions for known bugs. When you picked up the bug, you could un-skip the test that was right there waiting for you.

All that said, of course it's far from perfect!

0: https://github.com/metabase/metabase/ Backend unit tests are in test/, Frontend unit tests are in frontend/test, end-to-end tests (Cypress) are in e2e.

I've seen something that looks like AI-assisted root cause analysis on PRs: https://github.com/metabase/metabase/pull/57503#issuecomment...

Hope you enjoy the release. If you want to get into the nitty-gritty, check out our release notes in GitHub. To see what other features we have in the works, see our product roadmap.

The Web UI over DB is also the motivation of more BI oriented tool https://github.com/metabase/metabase

Or if you want to get into the nitty-gritty, check out our release notes in GitHub.

metabase

Metabase is a popular open-source business intelligence tool. A vulnerability was discovered around July 2023 and assigned CVE-2023–38646 (you can find the full write-up here) which had a devastating impact of pre-auth RCE (Remote code execution) which means an unauthenticated user with network access to any instance of the web application could run code on the servers the application is running on. So Let’s discover what went wrong!

Metabase | https://metabase.com | REMOTE | Full-time | Backend Engineers, Frontend Engineers, and Engineering Managers

Metabase is open source analytics software that lets anyone in your company rummage around in the databases you have. It connects to a number of databases / data warehouses (BigQuery, Redshift, Snowflake, Postgres, MySQL, etc).

People rather like the product (https://metabase.com/love). We're a remote team full of people who care about user experience, making complicated things as simple as possible and building things. We have a deeply pragmatic engineering culture and value building things that people actually use vs whatever closes a deal or makes for a good press release.

Tech stack: Clojure, Typescript, React, Redux, AWS https://github.com/metabase/metabase

Please apply here https://www.metabase.com/jobs and then email me at vamsi@metabase, I'll find your application internally and review it