Why PING8

PING8 combines the parts that teams usually buy from separate vendors:

A transactional Send API.
Marketing campaigns and contact segmentation.
DNS and deliverability verification.
Mailboxes and webmail.
SMTP provider connections.
KumoMTA-based high-volume delivery.
Multi-tenant operations, audit logs, and role-based administration.

The core idea

Email infrastructure works best when the sender controls the identity chain:

The domain that appears in the From address.
The DNS records that prove authorization.
The DKIM key that signs messages.
The MTA and outbound IP path that build reputation.
The logs that explain delivery outcomes.

PING8 brings those pieces into one dashboard.

Common use cases

Use case	Typical workflow
Transactional email	Add a domain, create a Send API template, issue an API key, send through `/api/batch_mail/api/send`, and watch delivery telemetry.
Marketing campaigns	Import contacts, create tags, build a template, create an email marketing task, test, launch, and inspect analytics.
Agency operations	Create domains and mailboxes for client brands, isolate send settings by tenant, and review operation logs.
Self-hosted infrastructure	Configure DNS, use Local Postfix for low volume, and connect KumoMTA/KumoProxy for controlled high-volume sending.
Compliance-sensitive sending	Keep domain configuration, contacts, mail content, and operational logs inside infrastructure you control.

Production defaults

Use verified domains before sending.
Keep unsubscribe links enabled for marketing campaigns.
Enable open and click tracking only when your privacy policy covers it.
Use Tenant default delivery once your tenant delivery profile is configured.
Send one test email before launching any campaign.
Confirm delivery telemetry, not only task progress.

What PING8 is not

PING8 does not magically fix poor list quality or cold IP reputation. It gives you the tools to configure identity, route mail intentionally, observe lifecycle events, and operate cleanly.

Introduction Personas