Every product gets a project. Your usage stays pooled.

Give each client, website, or product its own operating boundary. Domains, keys, contacts, and logs stay local; usage stays pooled.

Create your first project See pooled pricing
Projects
AS

Acme Storeacme.store

6.8k
LW

Lakeside Weblakeside.dev

3.1k
CP

Client Portalportal.co

1.4k
Workspace usage11,427 / 25,000
46%

Separation where it matters

Clean project boundaries without account sprawl.

Projects are designed for builders who move between client work, experiments, and live products all day.

Domains belong to projectsA normalized domain has one project owner, making sender context unambiguous.
Keys follow the workChoose a project-bound key, selected projects, or full workspace access.
Recipient state stays localContacts, suppressions, broadcasts, automations, and deliverability state do not leak between clients.
One place to operateSwitch projects without switching accounts, billing portals, or support workflows.

Organize the account in minutes, not migrations.

  1. Name the project

    Use the product or client name. The immutable slug keeps API and portal routes stable.

  2. Add domains

    Attach one or several sending domains and optionally enable the receiving capability.

  3. Choose the key boundary

    Use a project key for the application or a broader key for a trusted agent.

  4. Watch pooled usage

    See project contribution and the single workspace allowance from the same dashboard.

Build the portfolio, not the billing spreadsheet.

Free starts with one project. Pro unlocks unlimited projects with 25,000 pooled emails and 10 included domains.

Get your API key See pricing