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

Before ejecting
Select an artifact
Reconcile an upstream change
Conflict behavior
Updates and security

Ejection and merging

Transfer an eligible artifact to application ownership while retaining a reviewable path for upstream changes.

Ejection is the final customization option after configuration and replacing a runtime seam. It moves one eligible source artifact from package ownership to application ownership without disconnecting it from future upstream review.

Before ejecting

Use the smallest change that satisfies the application:

Configure the package through its public options.
Replace an explicit bridge or adapter seam.
Eject only when neither boundary can represent the required behavior.

Security-critical artifacts cannot be ejected. Signature verification, token validation, and similar package guarantees must remain package-managed so fixes arrive through version updates.

Select an artifact

npx playstack eject @playstack/example --target=example-source --dry-run
npx playstack eject @playstack/example --target=example-source

The package manifest must declare the artifact as ejectable. The CLI verifies the published hash, writes the application-owned target, saves the installed upstream base beneath .playstack/base, and records the relationship in .playstack/ejected.json.

After ejection, edit the application target normally. Do not edit the saved base; it exists solely to support deterministic three-way merges.

Reconcile an upstream change

npx playstack merge example-source
npx playstack merge --all

A merge compares three inputs:

Input	Ownership
Saved base	The exact upstream source present when the artifact was ejected or last merged.
Application target	The repository's current, application-owned implementation.
New upstream	The source shipped by the newly installed package version.

A clean merge updates the application target and advances the saved base. An unchanged upstream produces no write.

Conflict behavior

Conflicts never overwrite the application target with unresolved markers. The CLI writes a conflict report under .playstack/conflicts and returns the unsafe-conflict exit code so a human can review the competing changes.

When merging more than two ejected artifacts with --all, the CLI defaults to a dry run to avoid applying a large unreviewed ownership change at once.

Updates and security

playstack doctor --check reports when an ejected artifact's upstream hash has changed. Security-tagged upstream changes are called out distinctly.

playstack update attempts safe three-way merges after updating installed packages. In pull-request mode, package and managed changes form the primary branch, clean ejected merges form a dependent review branch, and each conflict receives a separate draft branch. Conflict markers are never committed.

Read Updates and CI before automating this workflow.

By