# Your newsletter, from your own domain.

URL: https://samva.dev/solutions/newsletters

Write each issue in Markdown, send it to your subscribers from your own domain, and publish a public archive of past issues on it.

[Start sending free](https://samva.dev/signup)

Start sending free

## Write in Markdown, publish an archive.

An issue is a Markdown file with a title and a slug. Save it, send it as a campaign, and the same issue becomes a page in your public archive, in your brand.

A newsletter issue is a Markdown file whose frontmatter names its newsletter topic, title, slug, and preheader.

## A newsletter shouldn't need a marketing suite.

- **A suite you did not ask for**: Drag-and-drop builders and automation menus, when you wanted to write an issue and send it.
- **Unsubscribes by hand**: Unsubscribe links, suppression, and bounce handling you would otherwise manage yourself.
- **Your archive on someone else's site**: Past issues live on a platform's page, not under your own name.

## Write, send, check.

1. **Write each issue in Markdown** Create a newsletter, write an issue as a Markdown file, and preview it as an email and as a web page before you send.
2. **Send it as a campaign** Send the saved issue to your subscribers from your own domain, now or on a schedule. Pause, resume, or cancel a run.
3. **See what happened for every reader** Every reader gets a status: sent, skipped, or failed, with the reason. Readers who opted out are skipped.

## Write in Markdown, keep an archive.

- **Markdown issues**: Write an issue as a Markdown file, preview it as an email and as a web page, and send it as a campaign.
- **A public archive on your own domain**: Past issues appear on a publication site in your brand, which you can serve from your own domain.

## Understand the split before you send.

- [Campaigns](https://samva.dev/features/campaigns): Send to your subscribers, now or on a schedule, with a status for every reader.
- [Templates](https://samva.dev/features/templates): Versioned, Git-backed templates for every issue.
- [Deliverability](https://samva.dev/features/deliverability): Domain authentication and suppression, the same on every send.
- [Transactional vs. marketing email](https://samva.dev/blog/transactional-vs-marketing-email): Why the classification decides your domains and consent.

## Questions from newsletter authors.

### Is Samva a newsletter platform?

Samva sends your issues from your own domain, with contacts, campaigns, and a status for every reader. You can write issues in Markdown and keep a public archive of past issues on your own domain.

### What does it cost?

You're billed per email sent: 500 a month free, then 50,000 for $19 on Growth. Each plan includes an active-contact allowance, listed on the pricing page.

You're billed per email sent: 500 a month free, then 50,000 for $19 on Growth. Each plan includes an active-contact allowance, listed on the pricing page.

### Can I bring my contacts?

Yes. Import a CSV into contacts, with tags.

### Should I send from a subdomain?

It helps. A subdomain like news.example.com keeps your newsletter's sending reputation apart from your other mail, such as receipts.

## Send your next issue from your own domain.

Verify your domain, import your contacts, and send the first issue.

[Start sending free](https://samva.dev/signup)

Start sending free