Every message your customers get, from one place.
Order confirmations, campaigns and WhatsApp conversations run through one workspace, with one contact list, consent recorded at every opt-in, and plans that grow with you.
1
contact list
Email and WhatsApp share consent and history
2
channels, one workspace
Campaigns, transactional email and WhatsApp
Free
to start
Every account opens in a sandbox
4
plans
From a first campaign to agency workspaces
One order, four moments.
Here is what Aegis does for a single customer, from the moment your app calls the API to the reply your team sends back.
- 01
Your app sends the receipt
One API call. Retries with the same idempotency key never send twice.
- 02
It lands in the inbox
From your own verified domain, with delivery, opens and clicks tracked.
- 03
WhatsApp keeps them posted
An approved template, sent only because Sam opted in.
- 04
Your team replies
The reply arrives in a shared inbox next to Sam's orders and consent history.
Everything you'd otherwise need three tools for.
- Campaigns
- Drag-and-drop email with personalization, scheduling, A/B subject lines and a resend to people who didn't open. WhatsApp broadcasts from approved templates.
- Email · WhatsApp
- Journeys
- Welcome series, reminders and win-backs that trigger on events from your app, wait, branch and send on either channel.
- Automation
- Signup forms
- Popups, flyouts, bars, embedded and hosted forms with display rules and double opt-in, added with one script.
- Growth
- Consent records
- Every opt-in keeps its source, page, time and the exact wording shown. Suppression lists, retention rules and erasure requests are built in.
- Compliance
- Agency workspaces
- Run client workspaces under your own brand and domain, with separate wallets and your margin on top.
- Agencies
Built for the people who write the code, too.
Create a key, verify your sending domain and send. Delivery events reach your webhook as they happen, errors carry stable codes, rate limits are in the response headers, and the TypeScript and Python SDKs are generated from the same OpenAPI spec as the API.
curl 'https://api.aegironlabs.com/v1/emails' \
-H "Authorization: Bearer $AEGIS_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: first-email-001' \
-d '{
"from": "Your business <hello@your-verified-domain.in>",
"to": [
"you@example.test"
],
"stream": "transactional",
"subject": "Your first Aegis email",
"html": "<p>Hello from your application.</p>"
}'Send your first message today.
Build against the real API in a free sandbox. Go live after a short business check.