PING8 Product Documentation
PING8 is a self-hosted, multi-tenant email infrastructure and marketing platform, powered by WorkOnward.
Use it to run transactional email, marketing campaigns, contact lists, templates, tracking, mailboxes, and sending infrastructure from one control plane. PING8 is built for teams that want more ownership over domains, DNS, DKIM keys, IP reputation, delivery logs, and customer data.
What PING8 includes
| Area | What you can do |
|---|---|
| Send API | Queue transactional email through API keys, templates, tracking, and optional IP allowlists. |
| Email Marketing | Create campaigns, target contact groups and tags, schedule sends, run tests, and inspect delivery results. |
| Contacts | Manage groups, subscribers, tags, suppression, double opt-in, and subscription forms. |
| Templates | Build HTML, drag-and-drop, and AI-assisted templates with preview and reuse flows. |
| Domains | Verify A, MX, SPF, DKIM, DMARC, and PTR records before sending. |
| Mailboxes | Create mailboxes, import/export users, and give users webmail access. |
| SMTP | Connect external providers such as Gmail, Mailgun, SES, SendGrid, or a custom SMTP service. |
| KumoMTA | Route high-volume delivery through a dedicated MTA path with telemetry and policy preview. |
| Operations | Review health, queues, operation logs, failed sends, provider trends, and system services. |
Recommended reading order
- Start with Why PING8 to understand the product model.
- Use Quickstart to set up your first domain and test send.
- Read Concepts if you need the product model before changing settings.
- Pick a Common Workflow for your first real outcome.
- Configure Domains and DNS before real sends.
- Choose a delivery path in Sending Infrastructure.
- Build a campaign with Email Marketing or an API flow with Send API.
- Use Troubleshooting when verification or delivery behavior is unclear.
Choose your path
| You are | Start with | Then use |
|---|---|---|
| Building product email | First Transactional Send | Send API and SDK docs |
| Sending newsletters or launches | First Marketing Campaign | Contacts and Email Marketing |
| Running client brands | Onboard a Client or Brand | Domains and Settings |
| Migrating a list | Migrate Contacts | Suppression and Tags |
| Self-hosting delivery | Self-host with KumoMTA | KumoMTA and KumoProxy |
Public guides and comparisons
These pages explain PING8 in answer-ready language for teams evaluating the product:
- Self-hosted email infrastructure
- Transactional Email API
- Email Marketing Platform
- KumoMTA and KumoProxy delivery
- PING8 as a Resend alternative
- PING8 as a SendGrid alternative
Safe operating pattern
PING8 gives you enough control to send real volume, so use a staged rollout:
- Verify the domain identity chain.
- Confirm the selected delivery engine can accept mail.
- Send to one owned recipient.
- Confirm lifecycle telemetry appears in PING8.
- Send to a tiny segment.
- Increase volume only after bounce, complaint, and deferral behavior look normal.
Documentation style
The docs are organized around workflows: what the screen is for, what to prepare, what to click, what success looks like, and what to check when something fails.
All infrastructure examples use placeholders such as yourdomain.com, mail.yourdomain.com, mta.yourdomain.com, and 203.0.113.10.