From SMTP relay to a modern email API
An API-first transactional email provider, EU-hosted. Structured delivery events, 90-day log retention, and a DPA on every plan. No SMTP credentials to manage.
API-first, not SMTP-first
SMTP2GO is built around SMTP relay. Envello is API-first: a JSON HTTP endpoint with structured responses, webhook events, and delivery status you can query. No SMTP connection pooling, no relay credentials to rotate.
EU data residency by default
API, database, logs, and backups run in the EU. A signed DPA ships on every plan at signup, including free. Your data doesn't leave the EU unless you send it there yourself via a webhook endpoint.
Structured delivery events
Every send produces typed webhook events: delivered, bounced, opened, clicked, complained. No parsing SMTP logs to figure out what happened. Query delivery history in the dashboard or via API for up to 90 days on Pro.
SMTP relay vs. email API
Why API over SMTP relay?+
An HTTP API gives you structured request/response pairs, typed webhook events, and delivery status you can query programmatically. SMTP relay works, but debugging a failed send means parsing server logs instead of calling an endpoint. Most modern frameworks make an HTTP call easier than configuring an SMTP transport.
Can I still use SMTP with Envello?+
Envello is API-only by design. If your application requires an SMTP interface (legacy systems, hardware devices), SMTP2GO or a similar relay may be the better fit. For application code in any modern framework, the HTTP API is simpler and gives you better observability.
How does pricing compare?+
Envello starts free with 3,000 emails/month and no daily cap. Paid plans are priced by volume, starting at 18 EUR/month for 50,000 emails. Check the pricing page for a direct comparison against your current SMTP2GO tier.
Check your own GDPR/DPA gaps before you switch
8 questions covering data residency, retention, and subprocessor documentation, the same things a security questionnaire asks.
Run the free checklist →