# One workspace for your email, your team and your agents.

Bring your contacts with their consent, build journeys in the console or through your agent, approve what goes out, and see what happened.

[Start for $1](https://app.plainsend.app/auth/login?signup=1) · [Read the quickstart](https://plainsend.app/docs.md)

## Explore Plainsend

Everything in the console is also an API call, a CLI command and an MCP tool, so a person and an agent work on the same things. Here is what is built today, and what is coming.

## Build: Build it your way, or let your agent.

The console, the command line, YAML files or an agent over MCP: they all make the same templates and journeys.

- **Your agent does the typing**. Claude, or your own agent, drafts templates and journeys over MCP or the command line. Its key can't send to customers.
- **Start from a working journey**. Install a pack, then change anything.
- **On brand without trying**. Logo, colours, fonts and footer, applied to every email.
- **Every version kept**. See who changed what, a person or an agent, and restore any version.
- **Bring the people you already have**. A spreadsheet or your website form on every plan; Salesforce from Growth, with opt-outs written back; HubSpot is coming soon.
- **One-off sends, too**. Newsletters and announcements go through the same checks and approvals as journeys.

## Run safely: Nothing goes out by accident.

Consent, approvals and sending reputation are built in, so a draft can't become a mistake.

- **A record of every yes**. Who agreed, how and when, per person. Opt-outs go back to your CRM.
- **A person puts it live**. Agents build; an owner approves the audience, message, send settings and checks.
- **New domains start gently**. A daily cap from 50 that rises as your mail is accepted, most engaged contacts first.
- **Your own domain, verified**. SPF and DKIM on your domain, your postal address in every footer, and sending pauses itself if bounces climb.
- **Every key has a kind** (coming). People, roles, agent keys, brands and domains. The rules exist today; a map of them in the console is coming.
- **Stored in Sydney**. Contacts and consent stay in Australia. Read the details on the security page.

## Measure: See what actually happened.

Results count people, not machines, and trace what they did back to the email that earned it.

- **Human clicks, not scanner noise**. Mail proxies, link scanners and prefetch are left out of opens and clicks.
- **Back to the email that earned it**. Bookings and revenue credited to the last human click within a window, with the rule written in words.
- **By mailbox provider**. Delivery, bounces and complaints for Gmail, Microsoft, Yahoo and the rest, side by side, against Google and Yahoo's lines.
- **Your data, out any time**. Export your workspace and read contacts through the API.

## Questions

**Who is Plainsend for?** Small teams who want journeys without an enterprise contract, and teams leaving Marketing Cloud or HubSpot who want the same engine with less to run. Solo starts at $1 a month, billed yearly.

**Do I need an AI agent to use it?** No. The console does everything an agent can. If you use Claude or your own agent, connect it over MCP or the CLI and let it draft while you approve.

**Can an agent send email to my customers?** No. Agent keys can draft, check and send tests to your team. Going live is an approval a person gives.

**Where does my data live?** In Sydney, Australia. The security page lists every service that handles it.

**What isn't built yet?** A visual journey builder in the console, A/B tests with a winner, hosted forms with double opt-in, and HubSpot as a source. Each is marked as coming wherever the site mentions it.

## Start with one journey

Open a $1 workspace, connect a spreadsheet or your website form, and install a journey from the gallery.

[Start for $1](https://app.plainsend.app/auth/login?signup=1) · [See pricing](https://plainsend.app/pricing.md)