Notifications.
Push, SMS and in-app notifications through one API — multichannel delivery, targeting and engagement analytics.
Reach users across push, SMS and in-app through one API, with segmentation, quiet hours, retries and engagement analytics — and the model to decide what to send and when.
- Category
- Communications
- Deployment
- Managed → air-gapped
- Governance
- IAM · encryption · audit
Three steps to running.
Connect push, SMS and in-app endpoints.
Target by segment and event, respecting quiet hours.
Delivery receipts, retries and engagement per channel.
Notifications, in full.
Push, SMS and in-app from one send, with fallback.
Segments, events and quiet-hours respected.
Receipts, retries and dead-letter handling.
Open, tap and conversion per channel.
Provision it in a few lines.
Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.
# Provision notifications on Aether Cloud
aether communications create \
--service notifications \
--name app \
--region us-1 \
--deploy managed # or vpc | on-prem | air-gappedAt a glance.
- Channels
- Push · SMS · in-app
- Targeting
- Segments · events
- Delivery
- Receipts · retries
- Quiet hours
- Respected
- Analytics
- Per channel
Built for real work.
Transactional alerts
Multichannel campaigns
OTP & verification
On one model, not stitched together.
The usual stack runs notifications in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.
No stitching a vector DB to one place, a warehouse to another and a model to a third — notifications sits next to the rest of the catalog, one identity, one bill.
The provider that runs Aether runs your notifications — so the data and the model never leave the same governed boundary to talk to each other.
Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.
Good to know.
Multichannel push, SMS and in-app from one API — with targeting and the model deciding what to send and when.
Yes — one send across channels with fallback and retries.
Yes — verification and one-time-passcode flows are supported.
Your boundary, your choice.
Pairs well with.
Run Notifications on Aether Cloud.
Push, SMS and in-app notifications through one API — multichannel delivery, targeting and engagement analytics. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.