Plans

Free

Plus

Pro

Playstack documentation
Getting started
CLIFree plan
1. ConfigurationFree plan
2. Artifact synchronizationFree plan
3. Existing schema adoptionFree plan
4. Integration planningFree plan
5. Ejection and mergingFree plan
6. Lint and SkillsFree plan
7. Updates and CIFree plan
Frameworks
Playstack + Megamono
Accounts, registry tokens, and upgrades
Packages
1. Foundation
  1. CoreFree plan
  2. ErrorsFree plan
  3. Errors ReactFree plan
  4. Nest ErrorsFree plan
  5. ValidationFree plan
  6. CryptoFree plan
  7. Prisma RuntimeFree plan
  8. SkillsFree plan
  9. LintFree plan
  10. LocalizationFree plan
  11. React localizationFree plan
  12. Nest localizationFree plan
2. Identity
  1. AuthFree plan
  2. Auth ContractsFree plan
  3. Auth ReactFree plan
  4. Auth NextFree plan
  5. Nest AuthFree plan
  6. AccountsPro plan
  7. Accounts ReactPro plan
  8. Nest AccountsPro plan
  9. DevicesPro plan
  10. MFAFree plan
  11. API KeysFree plan
  12. Nest API KeysFree plan
  13. ConnectionsFree plan
  14. AT ProtocolPro plan
  15. AuditPro plan
  16. Nest AuditPro plan
  17. Auth.js bridgeFree plan
  18. BillingFree plan
  19. EntitlementsPro plan
  20. GitHub AppPro plan
  21. Client AuthFree plan
  22. Nest BillingFree plan
  23. ExtensionPro plan
  24. Nest EntitlementsPro plan
  25. Extension ReactPro plan
  26. Nest GitHub AppPro plan
  27. LicensingPro plan
  28. Licensing IssuerPro plan
  29. Nest LicensingPro plan
3. Commerce
  1. CatalogPro plan
  2. PaymentsPro plan
  3. InventoryPro plan
  4. FulfillmentPro plan
  5. CommercePro plan
  6. Nest CatalogPro plan
  7. Nest PaymentsPro plan
  8. Nest InventoryPro plan
  9. Nest FulfillmentPro plan
  10. Nest CommercePro plan
4. Events and operations
  1. EventsFree plan
  2. Events PrismaFree plan
  3. Nest EventsFree plan
  4. Event StorePro plan
  5. Nest Event StorePro plan
  6. Rate LimitFree plan
  7. Rate Limit RedisFree plan
  8. Rate Limit PrismaFree plan
  9. Rate Limit DOFree plan
  10. Nest Rate LimitFree plan
  11. AnalyticsPro plan
  12. Analytics ReactPro plan
  13. Nest AnalyticsPro plan
  14. FeedbackPaid · allocation pending
  15. Nest FeedbackPaid · allocation pending
5. Communication
  1. AudiencesPro plan
  2. Audiences ReactPro plan
  3. Nest AudiencesPro plan
  4. Audiences ResendPro plan
  5. NotificationsFree plan
  6. Notifications ReactFree plan
  7. Nest NotificationsFree plan
  8. DeliveryFree plan
  9. Delivery HistoryPro plan
  10. Nest DeliveryFree plan
  11. WebhooksPro plan
6. Infrastructure
  1. CacheFree plan
  2. Cache Next.jsFree plan
  3. StorageFree plan
  4. MailFree plan
  5. QueuesFree plan
  6. Local FirstPro plan
  7. Local First IndexedDBPro plan
  8. Local First ExpoPro plan
  9. Nest QueuesFree plan
  10. Nest StorageFree plan
  11. RegistryPro plan
  12. Registry SwiftPro plan
  13. Nest RegistryPro plan
7. Content and intelligence
  1. ContentPro plan
  2. Content NextPro plan
  3. FeedsPro plan
  4. Feeds NextPro plan
  5. Nest FeedsPro plan
  6. AIFree plan
  7. SearchFree plan
  8. Search MiniSearchFree plan
  9. Search Next.jsFree plan
  10. Nest SearchFree plan
8. Application UI
  1. ChakraPro plan
  2. App UIPro plan
  3. Admin UIPro plan
FreeFree plan
PaidPro plan
PlusPlus plan
ProPro plan
Architecture
Compatibility
Native and multi-account authentication
Durable security decisions and projections
Data-only background sync hints

On this page

Available React bindings
Provider order
Security boundary
Framework composition
Optional application UI

React

Add Playstack session, account, audience, notification, analytics, and error state to React without treating client providers as security boundaries.

Playstack domain React packages are headless bindings over portable services. They carry safe state through a component tree and expose application-neutral hooks; they do not configure a router, render branded UI, initialize vendor SDKs, or authorize server operations.

Start with the React guide to add session state and an application error boundary.

Available React bindings

Binding	Core capability	Responsibility
`@playstack/auth-react`	`@playstack/auth`	Session state, auth actions, revalidation, and cross-tab synchronization.
`@playstack/accounts-react`	`@playstack/accounts`	Visible-account loading and active-account selection.
`@playstack/errors-react`	`@playstack/errors`	Reporter context and resettable render error boundaries.
`@playstack/analytics-react`	`@playstack/analytics`	Analytics context, reactive consent, and explicit route tracking.
`@playstack/audiences-react`	`@playstack/audiences`	Subscribe and preference-center state with safe public responses.
`@playstack/notifications-react`	`@playstack/notifications`	In-app inbox state, unread counts, pagination, and optimistic mutations.

The binding accepts an already configured core service or transport. This keeps provider initialization, API origins, consent persistence, and framework routing in the application.

Provider order

A useful default places operational reporting outside stateful product providers:

ErrorsProvider
└── ErrorsBoundary
    └── PlaystackAnalyticsProvider
        └── PlaystackAuthProvider
            ├── AccountsProvider when account switching is needed
            └── Audience or notification providers where their UI is rendered

This is not a mandatory global provider stack. Mount providers only around the subtrees that consume them, and keep server-derived initial state as narrow as possible.

Security boundary

RequireSession and account-aware navigation prevent confusing client transitions; they do not establish authorization. The server must revalidate authentication, membership, roles, entitlements, and API-key scopes for every protected operation.

Framework composition

Use these same bindings beneath Next.js, another React meta-framework, or a client-rendered application. Router-specific behavior is opt-in: analytics exposes dedicated Pages and App Router helpers, while other routers call analytics.page() after their own completed-navigation signal.

Optional application UI

Chakra, App UI and Admin UI add themes, controlled application compositions and the initial scoped members section. These are independent of auth/backend adoption. The host owns routes, data, mutations and authorization; Next Client Components hold callbacks and the Chakra system. See Application interfaces.

By