Persist Playstack capabilities through explicit application-owned Prisma clients, transactions, and managed schema fragments.
Visit Prisma ↗Compose credentials, magic links, sessions, passkeys, MFA, and connected-provider access without handing application identity to a framework.
Email and password · Magic links · Sessions · Passkeys and MFA · Auth.js provider sign-in · OAuth connections
Model organizations, memberships, invitations, ownership, active-account switching, and fail-closed data scope.
Memberships and roles · Invitations · Ownership transfer · Recoverable deletion
Carry typed domain events, operation context, transactional delivery, and replay-safe processing across application boundaries.
Event storage and replay
Apply fail-closed limits with trustworthy subjects and explicit Redis, Prisma, or Durable Object storage.
Distributed counters
Register application devices, manage push destinations, establish bounded trust, and revoke device-backed access from one explicit identity boundary.
Device registration and inventory · Push destinations · Trusted-device sessions
Synchronize subscription state, project purchased access into stable grants, and enforce capabilities without scattering plan-name checks through application code.
Subscription lifecycle · Entitlement projection · Request enforcement · No-card product trials · Billing operations
Issue scoped machine credentials, authenticate them at the server boundary, and record security-relevant actions without turning logs into policy.
API key lifecycle · Structured audit recording
Compose server-authored products, one-time checkout, finite stock, immutable orders, and physical fulfillment without turning one provider into the domain model.
Catalog and quotes · One-time checkout · Refunds and reconciliation · Physical fulfillment
Define typed notifications, resolve recipient preferences, deliver across explicit channels, and retain one provider-independent history of every send.
In-app inbox · Delivery history and feedback
Build waitlists, newsletters, release lists, and preference centers with explicit consent, segmentation, confirmation, and delivery boundaries.
Subscription lifecycle · Consent and preferences · Segmentation
Verify provider requests from raw bytes, claim events transactionally, enqueue normalized work exactly once, and keep provider parsing outside domain handlers.
Transactional receipt claims
Issue signed licenses, activate device-bound seats, verify access offline, rotate refresh credentials, and revoke grants without coupling product policy to the token protocol.
Issuance and activation · Refresh and revocation · Entitlement projection
Prisma adapters receive an existing client or transaction handle. Playstack does not create hidden global connections or take ownership of application migrations.
Capabilities that require atomic state and Tier 1 events expose transaction-kind requirements so persistence and event delivery can commit together.
Packages with managed Prisma fragments publish database-schema artifacts alongside structurally typed persistence adapters. playstack database sync copies those fragments into the application's named Prisma target; the application reviews the result, owns migrations, and supplies its existing client or transaction at runtime.
The current commerce and licensing schema surfaces include catalog, payments, inventory, commerce orders, fulfillment, and license issuance. Run playstack database compatibility before synchronization when an existing application schema may already satisfy those contracts.
Playstack supports multi-file schema artifacts with Prisma >=6.7.0 <8. Prisma 6 and Prisma 7 have separate verification coverage, and adoption preserves the application's installed major, generator provider, client output, and migration ownership. A version change is an explicit application operation rather than a side effect of adding a capability.
Compatibility checks inspect the complete datasource-bearing schema folder. An empty or nested target that excludes the configured schema entry fails closed instead of reporting a false compatible result.
By
