FAQ

How do I use it?

Install @idhub/identity-core plus the adapter package for your framework (Next.js or Angular) and a provider package per vendor (Segment, LaunchDarkly, FullStory). Start with Getting Started for the install commands and a summary of what you get, then follow the full copy-pasteable integration for your framework: Next.js example or Angular example.

How does it work?

See Architecture for the full breakdown. In one paragraph: identity-core generates one canonical anonymous id in a first-party cookie, upstream of every vendor SDK, and owns a simple anonymous ⇄ identified state machine; one identity-provider-* package per vendor (Segment, LaunchDarkly, FullStory) implements a shared IdentityProvider interface, so a single identify() call from your app fans out consistently to every registered vendor; and one identity-adapter-* package per framework (Next.js, Angular) wires that state machine into framework-idiomatic middleware, context, and hooks/services, with zero vendor-specific code ever touching your application.

How much does it cost?

Free. @idhub is MIT licensed and published to the public npm registry. There is no paid tier, and none is planned.

What can it do for me?

Before @idhub, each vendor (Segment, LaunchDarkly) independently generated and tracked its own anonymous id and independently implemented the anonymous→known-user transition — leading to logic duplicated verbatim across separate apps, and to real drift between them (one integration had no anonymous-id or alias step implemented at all). That duplication meant every app had to solve the same identity-linking problem again, at a different maturity level each time, with no shared, independently-versioned unit to depend on instead. @idhub solves the anonymous → known-user transition once: one canonical anonymous id, one identify() call site per app, and consistent behavior across every registered vendor — so adding a new vendor or a new framework is additive, not a rewrite.