Node SDK: a whole product, included.
Elsewhere this is server-side event capture from a CDP. Here it ships on every plan - never an add-on, never metered.
Published by AIOProductOS, the product management operating system for B2B SaaS teams. It joins customer feedback, revenue, delivery work, and code on one customer record, so teams prioritize by who is paying, not just what is loudest. Who builds it, and how we work.
npm install @aioproductoscom/node
import { ProductOS } from "@aioproductoscom/node";
const pos = new ProductOS({ productKey: "pk_live_..." });
pos.track({ userId: "u_123", event: "subscription_started" });Zero dependencies, Node 18+
What it does
What the Node SDK captures
-
Commercial events
The lifecycle your billing system sees - signup, payment, subscription, churn - captured where it actually happens.
-
Identity attached
Server-side events carry the real user id by construction; no anonymous guessing to resolve later.
-
Zero dependencies
One package, no transitive surface to audit, Node 18 or newer.
Why it beats the standalone version
Backend events are the revenue half of the join: when subscription_started from your server and feature usage from the app land on the same record, 'which paying accounts adopted what we shipped' stops needing a data team.
Where it stops, honestly
It captures and sends; it does not run your billing. The billing join on the spine comes from connectors (Stripe and peers) plus these events - the SDK is how your own backend's view of the customer reaches the record.
FAQ
The Node SDK, answered
What should I send from the server?
What are the requirements?
Does this replace my billing connector?
Every SDK, every plan, one spine.
Each of these is sold as its own product elsewhere. Here they all feed one customer record - feedback, revenue, work, and usage joined - on flat plans from $199/mo, every module included, with a 7-day free trial on your own data, no card required.