Send the announcement from your own domain.
Product updates, launch notes, and newsletters go to your contacts from your own domain, now or on a schedule. Send from the dashboard or the API, with the same templates, events, and bill as the rest of your email.
Announcements usually mean a second tool: another domain to set up, another template system, another contact list that drifts from the one you answer customers from, another bill priced per contact.
- AUDIENCE214 contacts, picked by tag
- DISPATCH212 of 214 dispatched
- SUPPRESSED2 skipped as suppressed
Create, send, and watch.
Create the campaign.
A published template or an inline email, sent to an audience picked by tags or contact ids.
Run it now or schedule it.
Pause, resume, or cancel a run while it sends.
Watch each recipient.
See who was sent, failed, or skipped, and why. Unsubscribed, suppressed, or blocked contacts are skipped for you.
Sending a newsletter? See the newsletter API page.
What comes with a campaign.
Unsubscribe handled
One-click unsubscribe on every campaign, plus your brand footer and unsubscribe link.
Engagement on your webhook
Opens, clicks, and unsubscribes arrive as signed webhook events tagged with the campaign and run.
Paced on new domains
A domain with a warm-up plan paces campaign runs until it is ready.
From anywhere
The dashboard, SDK, REST, the CLI with a dry run, or MCP.
Billed as sends
Each recipient is one email on your plan.
Beyond a single send: journeys and newsletters.
Journeys
Automated email sequences that start on a contact event, a new contact, a tag, or a group, then wait, branch, and exit.
Newsletters
Write issues in Markdown, send them as campaigns, and publish a public archive on your own domain.
Common questions.
Is this an email marketing platform?
No. A campaign sends one email to a list of contacts from your own domain. Automated sequences are journeys.
What are journeys?
Automated email sequences that start on a contact event, a new contact, a tag, or a group, then wait, branch, and exit.
Can I publish a newsletter?
Yes. You write Markdown issues, send them as campaigns, and publish a public archive on your own domain.
Can I use my existing templates?
Yes. Send a published template or write the email inline. Either way it goes out from your domain.
Who gets skipped?
Contacts who unsubscribed, are suppressed, or are blocked. Each skipped recipient shows the reason.
How is it billed?
Campaigns are on the paid plans. Each recipient is one email on your plan, and plans also include an active-contact allowance, listed on the pricing page.
The rest of the API.
Send email in one typed call
Transactional email from the SDK, REST, CLI, or your agent through MCP. Retries are safe.
Replies land in your app
Receive on your domain, parsed and threaded to the email it answers, delivered as a signed webhook.
Change the email without a deploy
Versioned templates in Git. Review the diff, publish that version.
Know why an email did or didn't land
SPF and DKIM on your domain, suppression you can see, events for every send.
Send the announcement too
Campaigns go to a list of contacts from the same templates and domain.
An inbox for your AI agent
A mailbox your agent reads and replies from, with a key that reaches only it.
Send your next announcement from Samva.
Related Resources
- FeatureTransactional emailTransactional email from the SDK, REST, CLI, or your agent through MCP. Retries are safe.
- FeatureTemplatesVersioned templates in Git. Review the diff, publish that version.
- FeatureNewslettersSend each issue to your subscribers from your own domain.
- FeaturePricingStart free with 500 emails a month. Then pay for the volume you send.
