Experimental
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 · Auth.js provider sign-in · OAuth connections
Experimental
Model organizations, memberships, invitations, ownership, active-account switching, and fail-closed data scope.
Invitations · Active-account switching
Render typed application email and deliver it through explicit SES, Mailgun, Postmark, Resend, SendGrid, SMTP, or capture-test providers.
Rendered application email
Experimental
Carry typed domain events, operation context, transactional delivery, and replay-safe processing across application boundaries.
Background jobs and workflows
Experimental
Publish RSS, Atom, JSON Feed, sitemaps, and related discovery surfaces from portable feed contracts.
RSS, Atom, and JSON Feed · Sitemaps and discovery
Experimental
Collect consent-aware application events and deliver them through explicit browser and server boundaries.
Browser analytics
Authorize, encrypt, refresh, and revoke third-party credentials without moving provider APIs or product workflows into a generic abstraction.
OAuth connections · AT Protocol sessions
Register application devices, manage push destinations, establish bounded trust, and revoke device-backed access from one explicit identity boundary.
Device registration and inventory · Trusted-device sessions
Experimental
Authenticate browser extensions, CLIs, desktop apps, and mobile clients through system-browser authorization, PKCE, rotation, and device-aware revocation.
Authorization code with PKCE · Native and extension callbacks · Token rotation and revocation
Planned
Establish same-user peer trust across mobile, desktop, and extension surfaces through a versioned protocol with selectable discovery and transport profiles.
Peer trust establishment (planned) · Transport profiles (planned)
Experimental
Build Playstack-connected browser extensions with MV3-safe runtime state, typed messaging, portable storage, and system-browser authentication.
Extension authentication
Define typed notifications, resolve recipient preferences, deliver across explicit channels, and retain one provider-independent history of every send.
Typed notification definitions · In-app inbox
Build waitlists, newsletters, release lists, and preference centers with explicit consent, segmentation, confirmation, and delivery boundaries.
Subscription lifecycle
Model portable content operations and compose AI-assisted generation through explicit providers, schemas, policy, and application-owned publication workflows.
Content contracts · Structured AI generation · Content workflows
Use namespaced portable caches with typed serialization, tag invalidation, and explicit stampede-protection capabilities across Redis, Workers, and local runtimes.
Namespaced key-value caching · Stampede-protected remember · Tag invalidation
Store and retrieve application objects through explicit filesystem, S3, or R2 providers with validated keys, metadata, streaming bodies, and signed access.
Portable object storage · Signed download and upload access · Local and test storage
Build product-specific search on portable query, ranking, transport, and framework contracts without coupling records to a provider.
Weighted lexical search · MiniSearch indexing · Next and Nest bindings
Share durable local mutations and synchronization semantics across web, Expo, and desktop clients while keeping product policy explicit.
Atomic local mutations · Portable synchronization · Platform storage
Verify provider requests from raw bytes, claim events transactionally, enqueue normalized work exactly once, and keep provider parsing outside domain handlers.
Raw-request verification · Provider normalization
Carry stable application errors across server and client boundaries, report normalized failures, and retain framework-native recovery without leaking sensitive context.
Stable application errors · React recovery boundaries · Provider-independent reporting
Planned
Compose authenticated realtime channels, resumable client state, WebRTC session control, and ICE or relay infrastructure without conflating events, signalling, and media.
Authenticated realtime channels (planned) · WebRTC sessions and signalling (planned)
Planned
Compose installability, application-shell caching, update coordination, and push registration without confusing a service worker with local-first application data.
Manifest and installation (planned) · Application-shell caching (planned) · Safe update coordination (planned) · Web Push registration (planned)
Experimental
Compose application-owned React and Next surfaces from Chakra themes, controlled App UI and scoped account/audience operator sections.
Prebuilt and custom administration
Experimental
Share locale policy and message catalogs across application UI, APIs and delivery without choosing a translation vendor.
UI and API composition