RTK

Infinite - OS runtime unifying GA4, PostHog, + Stripe into a local db

by
Your growth data is trapped in too many dashboards that don't talk to each other. Infinite pulls GA4, Meta, PostHog, + Stripe into one place on your own machine. Now you can finally ask one question across your whole stack and connect the dots: how traffic, signups and revenue move together. Data is stored locally + never leaves your machine. Open source, bring your own LLM, use Claude or Codex.

Add a comment

Replies

Best
RTK
Maker
📌
Hey everyone! My first personal launch on Product Hunt! I built Infinite because I got annoyed wiring up data across multiple analytics tools for different parts of the sales funnel for my own products. I had Klaviyo for email, GA4 for site analytics, meta CAPI for ad conversions, PostHog for user behaviour and Stripe for revenue. It was a pain in the ass to just understand WTF was going on. Were specific ads bringing in higher LTV users than others? My emails brought in site views, but how many went to my site and then abandoned cart? And so on. I ended up building out a local db + aggregated all of my data to it and just queried Codex/Claude myself. And it worked surprisingly well! Better than every individual tool I used. I showed a few friends and they started using it too, and eventually I. realised I had something on my hands and decided to open source it for everyone to use. Hope you enjoy using the tool! You're all welcome to join the Discord + if you have any ideas yourself, open up a PR and feel free to contribute! I wanna build something that all of us growth engineers can benefit from. - RTK
Somdip Roy

The "attribution is limited to what the source reports natively" caveat in your TUI is the part that builds trust — most analytics unification tools paper over this and pretend the joined data is ground truth. Naming the limitation makes

the rest of the output more believable.

Question on schema-drift: when GA4 / PostHog change their event schemas (which they do, often without warning), does Infinite hold the old shape in the local db and surface a "schema changed, here's what diverged" alert, or auto-migrate?


The former preserves historical comparability; the latter is easier UX.


Local-first analytics for indie scale is genuinely underbuilt — following 🚀

RTK

@somdip_roy1 Good question!

For now it would drift from the local db, but they don't do major changes without announcing them well in advance for this very reason. I have an agent keeping an eye on all their blogs/announcement pages for exactly this reason!

Abdullah Bin Asad

aggregating ga4, meta, posthog, and stripe keys into one local db that an AI agent queries directly is a lot of surface area in one place. first launch is solid work, just means if that local setup ever gets exposed its not one leak, its four

RTK

@abdullah_bin_asad 

Fair point!

Two clarifications though: The connector creds are encrypted at rest with a key only you hold; nothing (keys or data) ever leaves your machine.

Currently most connectors are read only in terms of the tools they have, so and you can also scope the keys for specific perms too. I'm gonna look into adding password protection to access the cli + db.