About Rasket

Rasket is an email API for developers: one REST API, a dashboard and typed SDKs for transactional email and broadcasts. You verify a domain, post a message to POST /emails, and every delivery, bounce, complaint, open and click comes back as a signed webhook. Sending, receiving, templates, contacts, broadcasts and automations are one product behind one API key.

Nothing in that split is a second product. A broadcast to a segment travels the same send pipeline as a password reset, records the same events, and honours the same suppression list.

• Email APISend email over one REST call: idempotent sends, batches, scheduling, attachments, templates and a delivery timeline for every message.
• WebhooksEvery delivery, bounce, complaint, open and click posted to your endpoint, signed with a timestamp, retried on failure and replayable from the dashboard.
• DomainsAdd a domain, publish the generated record set and send from it. A 2048-bit DKIM key per domain, a custom return path, and verification that runs on its own.
• ReceivingReceive email at your own domain. A signed webhook names every message; read its headers, text and HTML, and fetch attachments behind signed links.
• TemplatesWrite an email once, publish a version, and send it by ID or alias with typed variables. Every send records the exact version it used.
• BroadcastsAn audience you own: contacts with typed properties, segments, topics people subscribe to, and broadcasts sent through the same pipeline as your other mail.
• AutomationsWorkflows that run per contact: start on a custom event or a segment change, wait, branch, and send. Every run pins a version and is inspectable.
• For AI agentsAn MCP server, a setup skill, Markdown at every docs URL and typed SDKs, so an assistant can set Rasket up and send for you with no key in the prompt.

One Next.js application on Vercel serves the marketing site, the documentation, the dashboard and the public API. There is no second deployable unit and nothing is containerised.

The public API is described by an OpenAPI document served at /openapi.json, and the Node and Python clients are generated from it — so a field cannot exist in one and be missing from the other.

Every documentation page has a Markdown twin at the same URL, and /llms.txt lists them, because an assistant reading the docs should not have to parse a web page to do it.

Tenant isolation is enforced in the database rather than in application code, and every secret we hold is encrypted at rest.

The security page has the detail on all of it.

Everything published on this site is written by the Rasket team — the engineers who build the product. We publish under that name rather than a personal byline, because the team is what stands behind a claim, not whoever typed it.

How we check what we publish, how posts are dated, and how to ask for a correction are set out in the editorial policy.

Sales, support, security and everything else each have their own mailbox on the contact page.