Send email from your framework.
Framework integration is where SDK quality meets runtime reality. This hub catalogs the right send patterns, the common pitfalls, and the provider picks for popular web frameworks. Each page lists patterns to copy and mistakes to avoid.
Next.js
typescriptServer actions and route handlers are the natural send points. Edge-runtime support varies by provider SDK.
Nuxt
typescriptNuxt server routes and Nitro handlers are the send points. Most provider SDKs work without modification.
Remix
typescriptLoaders and actions are the send points. Remix is comfortable with both Node and edge deploys.
SvelteKit
typescriptForm actions and server-only modules are the send points. Most Node SDKs work; edge support is provider-specific.
Django
pythonAnymail is the canonical bridge. Most providers ship Anymail backends; pick a provider with a maintained backend rather than a raw SDK.
FastAPI
pythonAsync-first. Provider SDKs without async support need an httpx wrapper or a thread pool.
Ruby on Rails
rubyAction Mailer is the canonical interface. Providers with a maintained Action Mailer adapter beat raw SDK use.
Laravel
phpLaravel Mail is the canonical interface. Providers with a maintained transport beat raw SDK use.