Send email from your language or framework
Envello is a plain HTTP API, so it works from anywhere that can make a request. These guides show the direct integration for each stack, including where an SDK exists and where a fetch call is genuinely simpler.
Next.js
API routes and Server Actions, one fetch() call either way, plus edge vs. Node.js runtime notes.
NestJS
A dedicated EmailService and where dependency injection earns its keep.
Remix
Send from an action, not a loader, on Node or an edge runtime.
Nuxt.js
A server route using $fetch, plus runtime config and Vue component wiring.
SvelteKit
Form actions and API routes, with adapter-specific deployment notes.
Cloudflare Workers
No SDK dependency needed; a Worker's built-in fetch is the whole integration.
Deno
Built-in fetch and Deno's explicit permission model, no import surprises.
Supabase Edge Functions
A database webhook or trigger calling a Deno fetch, no extra dependency.
Django
Skip the SMTP EmailBackend for transactional sends; a plain HTTP call instead.
FastAPI
An async httpx call plus a background-task pattern so sending doesn't block the response.
Rails
Replace ActionMailer's SMTP delivery step, keep its templating.
Laravel
Swap the Mail facade's SMTP transport for a direct HTTP call.
Go
The Go SDK's current state, and the plain net/http version if you'd rather not wait on it.
ASP.NET Core
IHttpClientFactory over SmtpClient, with DI, async patterns, and IHostedService background sending.
Spring Boot
Skip JavaMail's SMTP abstraction for a direct HTTP call, with @Async sending and structured logging.
Elixir / Phoenix
Skip Bamboo's SMTP adapter for a direct HTTP call, with Task.Supervisor and Oban job queuing.
Don't see your stack? Email the founder directly → — the REST API works the same everywhere, and most guides are one HTTP client swap from any of the above.