Email plumbing, rebuilt in every app, forever.
Every application needs to send email — receipts, notifications, password resets, newsletters. So every application grows its own SMTP settings, its own templates, its own unsubscribe handling. Configuring it separately in each app is repetitive; keeping it compliant is worse.
And the day you want to switch email providers, you get to do it once per app. LymeSend centralizes delivery behind one API — the apps ask it to send, and the provider is a setting you change in one place.
Delivery, subscribers, and campaigns in one place
Verified against the service as it runs in production today.
- One HTTP API for transactional email — contact forms, notifications, receipts
- Subscriber management with proper opt-in and opt-out
- Campaign and bulk sending to your lists
- Unsubscribe compliance (CAN-SPAM) handled by the platform, not by each app
- Pluggable transports — Azure Communication Services, SMTP, SendGrid — switch providers in one place
- Multi-tenant: scoped API keys, sender addresses, and lists per tenant
- Email template support shared across your apps
- Self-hosted on your own VM, cloud or on-prem — no hard dependency on any cloud platform
The honest status
This site is the honest map of the suite — every page says exactly where its product really is.
LymeSend is in production — it delivers email for LymeBooks and the rest of the suite today, and has been through a full CI/CD hardening pass.
Early access is about onboarding outside tenants deliberately: sender reputation and deliverability are earned, so we bring teams on one at a time.
Wire email once. Then stop thinking about it.
If you run more than one app — or plan to — centralizing email is the kind of plumbing you only want to build once. Ask for early access and tell us what you're sending.
Request early access to LymeSend
One request covers anything you check below. We'll reach out by email to get you set up.
Request received
Thanks - we'll reach out by email to get you set up. No lists, no spam.