HOW IT WORKS
One place for every app
Manage separate projects with distinct credentials and sending settings. Keep test and production environments apart, and avoid mixing traffic between client applications.
A send flow built for real products
Target a known user or a group of subscriptions. Attach a URL or application deep link, define expiration rules and provide an idempotency key so retries do not create multiple messages.
Understand what happened
Track the journey from scheduled to queued, accepted by a provider and—in cases where the client reports it—opened. Provider acceptance is not proof a user saw a notification.
Privacy by default
Store only the data needed to address a subscription, rotate keys and isolate every project. Retention and deletion policies are part of the core design, not an afterthought.