Why it exists
The established email APIs are good products, and almost all of them process European mail in the United States. That turns an ordinary password-reset email into a data-transfer question somebody on the team has to answer — usually late, usually during a procurement review, and usually by someone who did not choose the provider.
eusend removes the question. Email is accepted, queued, rendered, signed, delivered and logged on infrastructure located inside the European Union, and message content is not copied out of it. The trade we are making is deliberate: fewer regions, fewer knobs, and a smaller feature surface than a platform with a thousand engineers, in exchange for an answer to “where does this data go?” that fits in one sentence.
What we actually run
The API, the queue workers, the SMTP relay and the mail transfer agent are operated directly rather than resold on top of another sending provider. That matters more than it sounds: when a message is deferred, bounces, or is filtered, the reason is in a log we can read, not in a vendor’s support queue.
| Data residency | Processing, storage and delivery inside the European Union. |
| Authentication | A 2048-bit DKIM key generated per sending domain at registration, never shared. SPF and DMARC records handed back with it. |
| Reputation | Bounces and complaints ingested continuously, suppressed per organization, and used to hold sending before a bad list damages the shared IPs. |
| Interfaces | REST API, SMTP relay, three SDKs, an MCP server for AI agents, and a Claude Code plugin. |
Everything the service does to your mail is documented rather than implied. The documentation is public and machine-readable, the changelog records every customer-visible change, and the status page is independent of our own hosting.
Who runs it
eusend is operated by Bjørnerås Labs, a registered Norwegian sole proprietorship (enkeltpersonforetak), organisasjonsnummer 938 162 336, based in Oslo. The number resolves in Brønnøysundregistrene, the Norwegian public business register, which is the authoritative record of the entity behind this service. Norway sits inside the EEA and the GDPR applies in full.
The product is deliberately narrow: a small surface that behaves the same way every time, documented in public down to the error codes, rather than a broad platform with a long tail of options. Support goes to people who work on the service itself — there is no tier system to escalate through, and a deliverability question gets a real answer rather than a template. eusend is built for teams who want a dependable tool they can reason about.
Trust and abuse
Sending reputation is a shared resource, so the rules are enforced quickly. Purchased, rented and scraped lists are refused. Accounts whose bounce or complaint rates threaten the platform are suspended, with an explanation and a route back. New accounts that closely resemble ones already stopped are held before their first send rather than after it. Every one of those decisions is reviewable by a human — write in and it gets looked at the same day.
How to reach us
Support and sales: support@eusend.dev. Security reports: security@eusend.dev. Privacy and data requests are covered in the privacy policy, and the subprocessors we rely on are listed in full.