framework
Next.js
Compose Playstack server contracts, React bindings, SSR handoff, and route adapters at the Next.js application edge.
Email delivery
Render typed application email and deliver it through explicit SES, Mailgun, Postmark, Resend, SendGrid, SMTP, or capture-test providers.
Supported approaches
Rendered application email
available
Produce typed subject, HTML, and text before provider I/O.
Packages
Provider templates
available
Use provider-owned templates only when the selected driver declares that capability.
Packages
Frameworks and integrations
Frameworks and integrations
framework
NestJS
Connect portable Playstack capabilities to dependency injection, guards, decorators, request context, workers, and lifecycle hooks.
integration
Amazon SES
Deliver rendered messages and SES templates through an application-configured AWS SDK client.
integration
Mailgun
Deliver rendered messages or stored Mailgun templates through an explicit regional provider client.
integration
Postmark
Deliver rendered Playstack mail or Postmark provider templates through an explicit driver and native client escape hatch.
integration
Resend
Deliver transactional mail and synchronize consent-aware audience contacts through explicit Resend adapters.
integration
SendGrid
Deliver rendered messages and dynamic templates through an isolated SendGrid mail client.
integration
SMTP
Deliver portable rendered email through an application-configured Nodemailer transport.
Package reference
Rendering belongs to the application
Playstack validates envelopes and separates rendering failure from provider failure. Chakra Email or another renderer can implement the typed template without becoming a dependency of the mail contract.
Delivery remains swappable
Choose SES, Mailgun, Postmark, Resend, or SendGrid for rendered mail and provider templates; SMTP for portable rendered delivery; or the capture provider for deterministic tests. Every provider exposes its exact native client when the portable surface is deliberately smaller than the provider.
