Beta · Invite only

Product events in, the right message out. In beta.

Contacts, companies and product events come in from your own systems. Segments and automations decide who should hear what. Every message passes a gate that checks consent and suppression right before it is sent, and every delivery can answer why this person got this mail. Built for SaaS teams whose customers are organizations. In beta and invite only.

Hosted by Cbox · Beta · Invite only

Hosted for you

Beta, invite only. Leave your details and I will reach out when there is room.

Events, not exports

Your app records what happened: a project created, a key revoked, a plan changed. Segments and automations are built on those events, not on nightly CSV uploads.

A gate before every send

Consent, suppression, frequency caps and a verified sending domain are checked at send time, not at campaign time. A dead address never gets a second mail.

Companies, not only people

An automation can run per contact, per membership or per company and pick the right administrator to talk to.

From an event to an explainable message

Product events API

One HTTP endpoint for events, deduplicated on an id you choose. Contacts and companies are keyed by your own ids, or by Cbox ID when you use it.

Segments and automations

Segments over properties and events; automations with waits, branches and messages that enter and exit on them.

Transactional and campaign mail in one pipeline

Password resets, invoices and release notes go through the same gate and get the same delivery log.

Website tracking

A small script records page views and custom events on your site and ties them to the visitor once they identify.

Delivery status and webhooks

Sent, delivered, bounced, complained, opened, clicked. Read it through the API or get it pushed to your app.

Connectors for Cbox ID and Cbox Billing

Sign-ups, memberships, subscriptions and invoices arrive as events without code on your side.