Private preview · iPhone & iPad

Delivered,
not retained.

Turn any webhook into a private notification on your Apple devices. Set up in seconds, encrypted by default, with no account required.

See how it works Read the privacy model

Accountless Encrypted pushes No payload retention

webhook.jsonPOST

curl https://hooks.relayseal.com/v1/builds
  -H "Authorization: Bearer rs_••••••"
  -d '{
    "title": "Build passed",
    "body": "Ready to ship 🚀"
  }'

202 accepted in 184ms

9:41•••

9:41

Tuesday, August 26

RelaySealnow

Build passed

Ready to ship 🚀

◆ Decrypted on this device

Made for the signals that matter

CI builds•AI agents•Cron jobs•Home automation•Payment events

From POST to pocket

One endpoint.
Three simple steps.

No SDK to install. No workflow builder to learn. If it can send an HTTP request, it can reach RelaySeal.

Create an endpoint

Open the app and get a private endpoint in about 30 seconds. No account, password, or dashboard required.

POST200

Send any webhook

POST JSON, form data, or plain text from a script, service, AI agent, cron job, or automation.

Read it on your device

RelaySeal maps the event, seals the notification for your device, and delivers it through APNs.

Privacy without hand-waving

Your webhook is a delivery,
not our data.

RelaySeal is designed to do one job and leave as little behind as possible. Plaintext is handled briefly for mapping, encrypted for your device, and never retained in Relay mode.

At the edge

Handled briefly, never warehoused

RelaySeal processes each event in memory inside a Cloudflare Worker only long enough to map and encrypt it. In Relay mode, payload content is not written to persistent storage.

In transit

Sealed before APNs

The title and body are encrypted for your device before Apple receives them. APNs carries the sealed envelope, not readable content.

On your device

Useful history stays local

Your encrypted notification history stays on your iPhone or iPad for 14 days and is deleted automatically.

Plain English promise

Apple can see routing metadata. RelaySeal briefly sees plaintext while processing. Neither receives a stored copy of your notification content in Relay mode.

Planned launch pricing

Start small.
Pay when you grow.

The essentials stay useful for free. Upgrade for more endpoints, more devices, and richer delivery controls.

FreeStart here

$0forever

A private endpoint for the small automations you rely on.

✓1 endpoint
✓1 device
✓100 events / month
✓14-day local history

Explore the free plan

ProBest for builders

$1.99month · $14.99 yearly

More room, richer routing, and delivery controls.

✓10 endpoints
✓5 devices
✓5,000 events / month
✓Templates and per-device routing

Explore the Pro plan

VaultOn the roadmap

$4.99month · planned for later

End-user encrypted history for when local is not enough.

✓50 endpoints
✓10 devices
✓10,000 events / month
✓90-day encrypted web inbox

View the Vault roadmap

Questions, answered

Before your first webhook.

Clear answers about setup, supported sources, privacy, and what to expect from the RelaySeal preview.

01What is RelaySeal?

RelaySeal turns an incoming webhook into a private push notification on your iPhone or iPad. It gives scripts, services, AI agents, scheduled jobs, and home automations a simple way to reach you without sending their events through a team chat or general-purpose notification inbox.

02How do I send a webhook notification?

Create an endpoint in the RelaySeal app, then send an HTTP POST request to its private URL. The request can come from a curl command, CI pipeline, server, cron job, shortcut, or any tool that supports webhooks. RelaySeal accepts JSON, form data, and plain text, so most integrations need no dedicated SDK.

03Does RelaySeal store my webhook payloads?

In Relay mode, payload content is not written to persistent server storage. RelaySeal handles the incoming event briefly in memory so it can map the title and body, encrypt the notification for your device, and pass the sealed result to Apple Push Notification service. Your useful notification history remains encrypted on your own device for 14 days.

04How are notifications kept private?

Each notification is sealed for an enrolled device before it is handed to APNs. Apple receives the encrypted notification content along with the routing information needed to deliver it. RelaySeal necessarily sees plaintext for a short time while processing the webhook, but Relay mode does not retain a readable copy after delivery. See Apple’s APNs documentation for more about remote notification delivery.

05What can I use RelaySeal with?

Anything that can make an HTTP request can use RelaySeal. Common examples include build and deployment pipelines, long-running AI agents, payment events, backup jobs, uptime checks, smart-home routines, and personal scripts. You choose the events worth interrupting you for, while the source system continues to own its full logs and history.

06Do I need an account or a dashboard?

No traditional RelaySeal account, password, or web dashboard is required for the core setup. Enrollment happens from the app, which creates the private endpoint and connects it to your device. Keep the endpoint credentials secret just as you would any webhook token, because they authorize a sender to deliver notifications to you.

07When and where will RelaySeal be available?

RelaySeal is currently in development for iPhone and iPad. The planned free tier is intended for a single endpoint and device, while paid plans add more endpoints, devices, monthly events, templates, and routing controls. Final availability, features, and launch pricing may change as the private preview progresses.

Sealed. Relayed. Delivered.

Give your webhooks
somewhere private to land.

RelaySeal is currently in development for iPhone and iPad.

Explore the 30-second setup

Delivered,not retained.

One endpoint.Three simple steps.