Email should be one call you can trust.
One typed send call, idempotent, with every event signed. Deliverability, templates, inbound, and webhooks sit behind it.
Email reaches your app as four systems you maintain: a sending API, a template store, a bounce handler, and a way to match replies to users.
Samva puts them behind one API. You send, and delivery events and customer replies come back as signed webhooks, threaded to the email they answer.
Samva fits developers on small SaaS teams who reach for an SDK or a curl command first, and the coding agents working beside them.
Replies come back
01A customer's reply reaches your app, threaded to the email it answers, with no matching script.
Your own domain
02Samva generates your DKIM and SPF records and checks your DMARC policy. You send with your own reputation.
Everything signed
03Every webhook is signed and retried, and every send has events you can check.
Your agent can run it
04Hosted MCP and the CLI give your agent the same API you use.
Who builds Samva.
Samva is built by Saatvik Arya at Arya Labs. He reads the contact form and support@samva.dev himself, and usually replies within a day.
“I kept building the same email plumbing in every product: bounce handling, a noreply box, and a script to match replies to users. Samva is the API I wanted instead.”
Send your first email.
Create an account, verify a domain, and send from code.