One account for
every app you ship.

Start free with one project and 3,000 emails. When the next idea goes live, Pro pools 25,000 emails across unlimited projects for $10/mo.

Start freeRead the quickstart
  • Transactional + marketing
  • REST · Node · SMTP
  • Card on file for production
Your workspaceEvery thing you shipPRO
ProjectKeyEmails
WAWeekend Appweekend.example
Sending key4,820
MSMicro SaaSmicro.example
Project key3,460
CLClient Launchlaunch.example
Custom key2,147
One pooled allowanceUnlimited projects on Pro10,427 / 25,000
3,000Free emails / month$10/moPro workspaceUnlimitedProjects on Pro25,000Pooled Pro emails

Start at $0

Free ships the first app. Pro pools the rest.

Start with one real product. Upgrade when another project, domain, automation, or inbound workflow needs the same account.

FreeFirst project$0

Ship one outbound product with a guarded path from sandbox to verified-domain sending.

  • 3,000 emails / month
  • 1 sending domain
  • No marketing contacts or broadcasts on Free
  • 100 recipients / day after activation
Read Free limits
ProEvery project$10/mo

Run transactional and marketing email for every app on one bundled workspace plan.

  • 25,000 pooled emails / month
  • 10 included domains
  • 10,000 contacts and marketing recipients included
  • Inbound receiving and REST attachments
Read Pro limits
Free is hard-capped with no overagesPro usage expands after the included amounts

The indie shipping loop

Build, separate, send, and see.

The workflow stays the same when the project changes. Give the new app a boundary, prove the send, and keep moving.

  1. 01BuildProve the first send

    Use the sandbox sender and simulator outcomes before a real recipient or verified domain enters the loop.

  2. 02SeparateGive the app a project

    Keep its sender domain, key, templates, contacts, suppressions, and results inside one clear boundary.

  3. 03ShipUse the stack you have

    Send through REST, the Node SDK, or the SMTP relay without rebuilding the application around email.

  4. 04SeeRead every outcome

    Inspect the recipient timeline or consume the same accepted, delivered, bounced, and complaint events.

One workspace, clear boundaries

Shared billing does not mean shared state.

Pool the allowance at the account level while each project keeps the identity, content, recipient state, and evidence for its own product.

ResourceProject boundaryOperating proof
Sender domains

Each verified domain belongs to exactly one project.

Unambiguous ownership
API keys

Bind a key to one project or select the precise workspace resources it may use.

Scopes cannot widen
Content and contacts

Templates, audiences, broadcasts, and automations stay project-local.

No cross-app mixing
Results and recipient state

Logs, events, and suppressions retain their project attribution.

Traceable end to end

One integration, every project

Swap the key. Keep the code.

REST, the Node SDK, and the SMTP relay all use the same account. A project-bound key can make the app’s access obvious without changing the send contract.

Open the quickstart
Production request200 OK
AuthorizationBearer ntc_project_key
EndpointPOST /api/v1/email/send
Outcomerecipient timeline + webhook
RESTNode SDKSMTP relay

The email chores

The pieces you would rather not maintain.

Test the unhappy paths, verify each sender, authorize the agent, and send the launch update from one product surface.

Test outcomesDelivered, bounced, complained, and suppressed — without contacting a real inbox.Separate sendersGive every product a verified identity and visible domain status.Hand it to an agentUse MCP, OpenAPI, scoped keys, and stable errors to let an authorized agent wire the app.Send the launch updateCreate the audience, send the broadcast, and follow each recipient result.

The next project

Create the key. Send the first email.

Start with the sandbox and one project, then keep the same integration ready for every product that follows.

Start freeCompare plans