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

Good Worker starting points
Runtime rules
Deployment boundaries stay visible
Cloudflare queue bindings

Workers

Use Playstack's Web-standard domain contracts and edge adapters in Cloudflare Workers and other constrained runtimes.

Many Playstack domain packages target Web platform primitives so they can run in Node.js and Workers without separate business logic. Worker compatibility is tested per package; Node framework adapters and provider SDK assumptions remain outside the Worker bundle.

Start with the Workers guide to compose Web Crypto and a native streaming response inside a fetch handler.

Good Worker starting points

Capability	Package	Worker boundary
Shared errors, results, time, and operation context	`@playstack/core`	Dependency-free contracts.
Encryption, digests, signatures, and tokens	`@playstack/crypto`	Injects `globalThis.crypto`; key configuration remains application-owned.
Validation	`@playstack/validation`	Portable schemas and HTTP validation errors.
Domain events	`@playstack/events`	In-process bridge with application-owned durable delivery.
Authentication and accounts	`@playstack/auth`, `@playstack/accounts`	Portable services with injected persistence and request handling.
Rate limiting	`@playstack/rate-limit`	Atomic store contract with a `Durable Object adapter`.
Feeds and sitemaps	`@playstack/feeds`	Native streams, `Response`, and structural R2 storage.
Audit	`@playstack/audit`	Append-only chains with application-owned storage.

Check each package reference before importing infrastructure or framework adapters. A portable core package may be Worker-compatible while one of its database or NestJS bindings is intentionally Node-only.

Runtime rules

Prefer Web Request, Response, ReadableStream, and crypto.subtle at the boundary.
Construct services once at module scope when their dependencies are safe to reuse across requests.
Derive request-specific operation context inside fetch and pass it into domain commands.
Keep secrets in Worker bindings and parse them into narrow package configuration at composition time.
Use Durable Objects, queues, R2, or another service through explicit structural adapters.
Use ctx.waitUntil() only for observational work that is safe outside the response transaction.

Deployment boundaries stay visible

Playstack does not hide Cloudflare bindings behind ambient globals. The Worker entry receives env and decides which binding satisfies each package contract. Native clients or bindings remain exposed where an application needs provider-specific capabilities.

Cloudflare queue bindings

Use @playstack/queues/cloudflare for typed producers and Worker batch handlers. Cloudflare Queues documents individual acknowledgements, bounded JSON batches, durable quarantine and explicit unsupported operations. It does not replace arbitrary ingestion payloads automatically or install a Nest worker.

Localization also runs through the portable policy/catalog boundary; choose an ICU runtime compatible with the selected Worker deployment.

By