routing
Multi-provider routing
Connect Brevo, Resend, and SMTP once, then choose how each app sends: pin to one provider, rotate traffic, or keep a standby route ready when a provider is constrained.
BrevoResendSMTProuting
One MCP URL · Brevo and Resend · your keys
Email orchestration runtime for AI agents.
Agents should spend context on the message, not on provider SDKs and rate-limit math. Plinth gives them one MCP URL with plinth.discover and plinth.execute, then runs provider routing, failover, rate-limit and cap enforcement, suppression, retries, and tagged delivery evidence across your connected email providers.
Managed SaaS · bring your own provider keys · designed for multi-app, multi-provider email operations.
Your MCP client
Claude
Codex
Cursor
…or any MCP client. REST works too.
Plinth runtime
plinth
email runtimehttps://plinth.dev/mcp
What the agent sees
plinth.discovercapability searchplinth.executerun any toolBehind the two calls
Provider routing and failover, TOS rate limits, per-domain caps, suppression, backlog queue, brand tokens, tagged delivery evidence — applied to every send.
67 tools indexed · 25 for email
Your email providers
Brevoyour API key
Resendyour API key
Keys are sealed in the vault. Plinth never owns your sending reputation.
One control plane for email delivery
Replace provider sprawl with a reliable email operations layer.
Plinth gives product and engineering teams one place to manage providers, routing, brand controls, safety limits, and delivery insight across every app that sends email.
limits
Provider-limit protection
Plinth applies known provider limits, such as daily caps and requests per second, so your product slows down gracefully instead of running into surprise blocks.
daily capsper-second limitssafe pauses
brand
Per-app brand identity
Run marketing, transactional, and customer-specific email from one workspace while keeping each app's logo, sender, footer, and visual style separate.
logossendersfooters
templates
AI-assisted templates
Draft and refine email templates from goals, audiences, and brand rules. Teams get faster iteration without losing control over the final customer-facing message.
draftpreviewapprove
insights
Delivery observability
See which app sent, which provider handled it, whether it was delivered, and where failures are concentrated. Filter by app, provider, template, or recipient domain.
insightseventshealth
keys
Bring your own keys
Use your own Brevo, Resend, or SMTP credentials. Provider billing stays direct, credentials are protected, and Plinth orchestrates delivery without marking up your volume.
sealed keysno markupyour providers
failover
Automatic failover
With two providers in an app's pool, turn on rate-limit failover: if the active route hits a Plinth quota or provider rate ceiling, Plinth tries the next provider before failing the send. (Explicit per-send `preferredProvider` pins skip failover.)
auto-retrycross-provideraudited
events
Unified event stream
Bounces, complaints, opens, clicks — every delivery event from every provider lands in one normalized webhook schema, one analytics table, one API. Build your suppression list once and it works across Brevo and Resend.
webhooks/insights/emailsuppression
agent
Agent-native workflow
Streamable HTTP MCP transport means your agent can compose a template, preview it, ask for approval, and send in one turn. No REST endpoints to wire, no JSON schemas to hand-roll — just tools your agent discovers.
streamable-httpemails.sendemails.compose_template
Designed for modern product teams
A clean dashboard for humans, automation-friendly APIs for engineering, and controlled workflows for AI-assisted email creation.
Workspace-safe by default
Business-domain verification, workspace ownership, and role-based access keep provider credentials and sending decisions under the right team's control.
Evidence for every send
Every delivery decision is recorded with app, provider, template, and outcome details so teams can investigate incidents and answer customer questions quickly.
Bring your own keys
Use your existing provider accounts and keep the commercial relationship direct. Plinth protects credentials and coordinates delivery across them.
AI-ready, approval-friendly
Agents can assist with template creation and sending workflows while operators keep visibility over routing, brand, and safety settings.
Hosted and managed
No separate email orchestration service to run. Plinth hosts the control plane while your team manages providers and apps from the dashboard.
Built for production email
Everything you need before email becomes an incident.
Single-provider setups work until volume, compliance, or reliability requirements rise. Plinth gives you the routing, safety, and visibility layer before those risks turn into support tickets.
Deliverability workflows
- Warm-up planning for new sender domains
- A/B subject and send-time experiments
- Suppression-list visibility across providers
- Provider health checks before high-volume sends
- Deliverability review for critical campaigns
Operational controls
- Per-app routing policies
- Provider-limit presets
- Credential rotation
- Team access controls
- Audit-ready delivery records
From signup to first send
A multi-provider email pool, set up properly the first time.
Plinth turns provider setup, routing, sender identity, limits, and delivery tracking into a guided workflow your team can manage from one dashboard.
- 01Domain verified
Create your workspace
Start with a work email so Plinth can verify your company domain and set up the right workspace for your team.
- 02Credentials protected
Connect your first email provider
Add Brevo, Resend, or SMTP credentials. Plinth stores them securely and checks that the provider connection works before marking it live.
- 03Limits preconfigured
Apply provider safety limits
Known daily and per-second limits are applied automatically so your team does not accidentally trip provider blocks during growth or a campaign spike.
- 04Provider pool ready
Add a backup or rotation provider
Use different providers for different apps, or rotate traffic across healthy providers so email keeps moving when one route is constrained.
- 05Routing saved
Pick a routing strategy per app
Choose whether each app should use one provider, round-robin rotation, or random distribution across the pool. The choice is saved and visible in the dashboard.
- 06First send tracked
Send with confidence
Your app sends through Plinth, which picks the right provider, applies the app's brand, respects safety limits, and records the outcome for later review.
Why Plinth, and not …
One provider, hand-rolled, or Plinth.
Single-provider services are great until that one provider degrades or hard-stops your daily quota. DIY multi-provider works until a policy update or a late-night rate-limit incident. Plinth carries the routing, provider-limit protection, and delivery evidence so neither failure mode becomes your problem.
| Plinth | Single-provider SaaS | DIY (you + N SDKs) | |
|---|---|---|---|
| Multi-provider pool from one integration | ● yes | ○ no | ◐ partial |
| Per-app routing strategy | ● yes | ○ no | ○ no |
| Provider-limit protection | ● yes | ◐ partial | ○ no |
| Failover when a provider's quota is exhausted | ● yes | ○ no | ◐ partial |
| Bring your own provider accounts | ● yes | ○ no | ● yes |
| Protected provider credentials | ● yes | ◐ partial | ○ no |
| Per-app brand identity at send time | ● yes | ○ no | ○ no |
| Audit-ready records across providers | ● yes | ○ no | ○ no |
| AI-assisted template workflows | ● yes | ○ no | ○ no |
Single-provider SaaS column is generalised across Resend, Postmark, Mailgun, SendGrid; individual products may handle a row better than the average. We're not trying to dunk on them — they're excellent at what they do, which is one rail.
Built on live usage
Plinth uses the same email operations layer we sell.
Sign-in emails, team invites, product updates, and customer notifications are handled through Plinth's provider routing, safety limits, brand controls, and delivery records. That keeps the product grounded in the same reliability requirements our customers have.
- Production email runs across multiple provider routes
- Provider health, limits, and routing are visible in the dashboard
- Delivery outcomes are recorded for support and compliance review
- The same controls are available to every customer workspace
Live platform signals
- Verified records
- #3
- Workspace
- self
- Providers connected
- 8
- Integrity anchors
- 0
- Update subscribers
- 2
- Posture
- healthy
These signals are refreshed from the live service so visitors can see whether Plinth's own email operations are healthy.
Updates
Stay in the loop on new providers and deliverability features.
Plinth is open and self-serve — claim a workspace whenever you're ready. If you just want to follow along, drop your email below and we'll send a short note when we ship a new provider integration, deliverability workflow, or product improvement. No drip campaigns and no noisy sales follow-ups.
Personal email addresses are welcome for updates. Use a work email when you're ready to create a company workspace.
Stop being a part-time deliverability engineer.
Plinth handles provider routing, safety limits, brand controls, template workflows, and delivery evidence so your team can ship email faster without gambling on a single provider.