Headless domain bindings plus optional Chakra application and admin compositions, with server authority kept outside the client.
Visit React ↗Compose credentials, magic links, sessions, passkeys, MFA, and connected-provider access without handing application identity to a framework.
Email and password · Magic links · Sessions · Split-origin browser sessions · Passkeys and MFA
Model organizations, memberships, invitations, ownership, active-account switching, and fail-closed data scope.
Active-account switching
Collect consent-aware application events and deliver them through explicit browser and server boundaries.
Browser analytics
Authenticate browser extensions, CLIs, desktop apps, and mobile clients through system-browser authorization, PKCE, rotation, and device-aware revocation.
Build Playstack-connected browser extensions with MV3-safe runtime state, typed messaging, portable storage, and system-browser authentication.
Typed messaging and storage
Define typed notifications, resolve recipient preferences, deliver across explicit channels, and retain one provider-independent history of every send.
In-app inbox
Build waitlists, newsletters, release lists, and preference centers with explicit consent, segmentation, confirmation, and delivery boundaries.
Subscription lifecycle
Build product-specific search on portable query, ranking, transport, and framework contracts without coupling records to a provider.
Weighted lexical search
Share durable local mutations and synchronization semantics across web, Expo, and desktop clients while keeping product policy explicit.
Atomic local mutations · Portable synchronization
Carry stable application errors across server and client boundaries, report normalized failures, and retain framework-native recovery without leaking sensitive context.
React recovery boundaries
Compose authenticated realtime channels, resumable client state, WebRTC session control, and ICE or relay infrastructure without conflating events, signalling, and media.
Authenticated realtime channels · WebRTC sessions and signalling
Compose installability, application-shell caching, update coordination, and push registration without confusing a service worker with local-first application data.
Manifest and installation · Safe update coordination · Web Push registration
Compose application-owned React and Next surfaces from Chakra themes, controlled App UI and initial admin sections.
Theme composition · Prebuilt and custom administration
Share locale policy and message catalogs across application UI, APIs and delivery without choosing a translation vendor.
UI and API composition
React adapters expose application state and actions through providers and hooks for authentication, accounts, analytics, audiences, errors, and notifications. Server-side authentication, authorization, tenant scope, and persistence remain authoritative.
Install only the adapter for the feature being rendered, pass an application-owned transport, and hydrate it from a validated server projection when available.
The optional UI stack now includes Chakra themes, app shells/navigation, settings, tables, commands, Kanban and resizable panes, plus the first account-admin shell and members section. These are React DOM compositions, separate from the headless domain bindings.
Prebuilt and custom Next routes use an application-owned shell and server authorization. Create Chakra systems in client-owned modules; keep interactive callbacks behind Client Component boundaries. Global staff and impersonation flows are still to come; verify browser behavior in your own product. See UI packages.
i18n-react provides isolated typed catalog hooks and a package-message bridge. App UI and Admin UI consume the same application catalogs and formatter; English defaults work without a provider. Locale detection, routing and translations stay host-owned.
By
