Who builds Ploxir

Ploxir is built by Chaara, working alone from Spain. Not a team, not a company with a marketing department — one person who had this problem and got tired of it.

I run several SaaS products and a few other things alongside them. Every one of them keeps its numbers somewhere else: Stripe for one, an app store for another, analytics in a third place, ad spend in a fourth. Checking how things were actually going meant opening a dozen tabs and holding the total in my head — and I never once had a single number for everything I run, only a number for each piece of it.

So I started building Ploxir in 2025. It connects each business to the platforms it actually uses, then adds them up: combined revenue, combined costs, and a per-business breakdown whenever you want to see which one is carrying the others. That is the whole idea. Everything else — the 50+ integrations, the widgets, the currency conversion — exists to make that one number correct.

Where it stands

Ploxir is in public beta. That is stated plainly because it is true: every paid plan is free right now, and things are still being fixed and added weekly. You can see exactly what has shipped and when on the changelog, and whether it is running right now on the status page. Both are generated from the real thing, not written by hand.

On trusting one person with your revenue data

Connecting Ploxir means handing over read access to platforms that hold your money. That is a real thing to ask, and it deserves a real answer rather than a badge. Credentials are encrypted before they are stored, read-only access is used wherever a platform offers it, and you can disconnect a source at any time — which deletes what was stored for it. The specifics, including how the encryption works and how to report a vulnerability, are written out on the security page.

If something is wrong, or a number does not look right, email [email protected] — it reaches me directly, and a wrong number is the thing I most want to hear about.