Logistics and warehousing
Order, picking, unloading and incident alerts. The operator confirms from their device and the operation moves on.
Truck at dock 3
Unload scheduled 2:30 PM · 12 pallets
Operational alerts · Acknowledgement · Audit trailOperational alerts that get delivered,
Operational alerts that get delivered,
acknowledged and logged.
When something needs action, Pingway reaches the right person — on the right device. As simple as a pager, built for modern operations.
On Android? Get the APKv1.4
- Reaches the right person
- Read confirmation
- Everything is logged
device:android-01delivered · ACK
200 OK142 ms
Use cases
Where email falls short and chat gets lost
Pingway works the same in logistics, maintenance, food service, healthcare or security. Same pattern: someone receives it, confirms it, and it stays on the record.
From the perspective of whoever has to act
The alert lands in a pocket or on a wrist. One tap confirms it — no app to open, no phone to unlock. That confirmation reaches your system the same second.
- 1 Your system POSTs the event
- 2 It rings on the paired device, not in a group chat
- 3 The person taps "Confirm" and it is on the record
Maintenance and industry
Alerts to the technicians on shift. No radios, no internal group chats. It reaches the right device and records who saw it.
Line 2 stopped
Pressure sensor out of range · 4 min
Food service and retail
Orders, pickups, floor alerts. The kitchen display or the manager device confirms every event instantly.
Order — table 12
2× margherita pizza, 1× salad
Clinics and hospitality
Room requests, status changes, staff calls. Every notification reaches the person who must see it, not a shared inbox.
Room 214 calling
Assistance requested · 40 s ago
Security and monitoring
Camera, sensor and alarm events. Delivered to the device of whoever is on duty and confirmed within seconds.
Temperature out of range
Freezer unit · −12 °C
API integrations
Your pipelines, cron jobs or internal systems fire alerts over the API. No mobile SDKs, no push tokens to manage.
Backup failed
prod-db · retrying in 10 min
Capabilities
What you get by integrating Pingway
A small piece that saves you building and maintaining the usual plumbing: mobile SDKs, token management, deduplication, retries, acknowledgements.
Explicit acknowledgement
Flag critical alerts with requireAck. The event only closes when the recipient confirms it — and that confirmation is on the record.
iOS and Android receiver app
A native app that only receives what is addressed to its paired device. No noise, no mass push, no SDKs inside your apps.
Send by group or tag
Alert "maintenance", "night-shift" or "downtown-branch" with a single POST. Operational segmentation, not marketing.
Per-organization isolation
Each organization manages its own devices, API keys and webhooks. No leaks between accounts.
QR pairing
Generate a code in the console and pair by scanning it with the device. No SDKs, no rotating credentials.
Real time
Sub-second end-to-end latency. If the device is offline, Pingway redelivers as soon as it reconnects.
Event webhooks
Subscribe to delivered, ack and failed. Your system reacts once the recipient confirmed — not before.
Agent-ready (MCP)
Built-in MCP server: an AI agent can alert a person and wait for their confirmation before moving on. Connects with the same API key.
Full audit trail
History per message, device and organization. Filter by status, device or time window from the console.
Integrate in 3 lines
One API key, any language
Generate the API key in the console, point at the hub and start sending. The paired device receives in real time and confirms once the user marks it as seen.
- No mandatory client libraries
- Works with any backend or cron job
- Optional webhook for delivery events
send-notification.sh
# POST an operational notification with ACK curl -X POST "https://hub.pingway.io/api/notifications" \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "to": "device:android-01", "title": "Order — table 12", "body": "2× margherita pizza, 1× salad", "requireAck": true }'
✓ delivered·ACK 142 ms·device:android-01
Reliability
What happens when the phone does not cooperate
The question that matters is not whether the server is up, but whether the alert lands when the phone is locked, in battery saver or out of signal. Here is what Pingway does in each of those cases.
The phone is locked or the app is closed
The alert still shows, and it can be confirmed from the notification itself — no unlocking, no opening the app. On iPhone delivery travels over Apple push, which works with the app closed; the receipt is recorded right then.
Android goes into battery saver
Doze suspends background apps, so keeping a connection open is not enough. Pingway uses a high-priority Google message to wake the device and reconnect; the alert is delivered as soon as it is back.
The device lost connectivity
The notification is not lost: it stays pending on the server. Once the device reconnects, everything pending is delivered to it — the sender does not have to retry anything.
Nobody confirms the alert
With acknowledgement required, the send is not considered closed: delivery is retried and the status stays unconfirmed. Your system can listen for that event and escalate to someone else.
Your system retries the same send
Send an idempotency key and two attempts at the same alert create a single notification. The recipient sees no duplicates and your quota is not charged twice.
The person muted that profile
They stop receiving immediately, and whatever was sent meanwhile is discarded instead of piling up: turning it back on does not bury them in stale alerts. The sender sees it reflected in the status.
Everything is on the record
Every delivery attempt, every receipt and every confirmation is stored with its timestamp. When someone asks "was this reported?", the answer is not a guess.
Comparison
Why what you already use is not enough
Almost anything can deliver a notification. The hard part is knowing someone saw it, having it on the record, and having it insist when they do not.
| Capability | Pingway | Raw FCM / APNs | WhatsApp / Telegram | PagerDuty / Opsgenie | Pushover / ntfy |
|---|---|---|---|---|---|
| Per-event acknowledgementa | Yes | No | Partial | Yes | Partial |
| Record of who confirmed and when | Yes | No | No | Yes | No |
| Retries until confirmed | Yes | No | No | Yes | Partial |
| Ready-to-install receiver app | Yes | No | Yes | Yes | Yes |
| No mobile SDK or token management | Yes | No | Partial | Yes | Yes |
| Multi-org console with API keys | Yes | No | No | Yes | No |
| Send by operational group or tag | Yes | Partial | Yes | Yes | Partial |
| Separate from personal messages | Yes | Yes | No | Yes | Yes |
| Built for frontline staffb | Yes | n/a | Yes | No | Partial |
| AI agent integrationc | Yes | No | Partial | Yes | No |
| Cost | Per workspace | Your engineering | Free | Per user | Low |
- a. Every alert is acknowledged on its own and recorded with a timestamp, along with who attended to it.
- b. Built for people who work without a desk: confirmed with one tap from the notification, no unlocking, no opening the app.
- c. Ships with an MCP server: an AI agent can send an alert and wait for a person to confirm before moving on.
When we are not your tool. If you need on-call rotations, tiered escalation and infrastructure incident postmortems, go with PagerDuty. If you want to blast promotions to millions of users, go with FCM. Pingway is for the everyday operational alert that someone has to see and confirm.
Pricing
Simple plans. You pay for real delivery.
Start free and move up when you need to. Annual saves ~17–20%.
Free
To try Pingway, integrate and validate a simple flow
$0/mo
Free forever
Start free- 1 organization
- 1 paired device
- 1 API key
- 500 notifications / month
- 3-day history
- ACK included
No webhooks · No SLA · Community support
Starter
For businesses starting out with a single operational point
$10/mo
Billed annually · $120/yr
Get Starter- 1 organization
- 3 paired devices
- 2 API keys
- 3,000 notifications / month
- Explicit ACK
- 7-day history
- Email support
No webhooks · No SLA
Most popular
Pro
For teams that depend on delivery
$24/mo
Billed annually · $288/yr
Try Pro- 1 organization
- 25 paired devices
- 10 API keys
- 50,000 notifications / month
- Explicit ACK + webhooks
- Send by group or tag
- 90-day history
- Email support
Move up a plan when you need more volume
Business
For critical operations at scale and multi-site
$79/mo
Billed annually · $948/yr
Talk to sales- 1 organization with multi-site
- Up to 100 paired devices
- Up to 25 API keys (extendable on request)
- 500,000 notifications / month
- Signed webhooks + retries
- Send by group, tag and site
- 1-year history + CSV export
- 99.9% SLA · Optional SSO
Priority support · Assisted onboarding
Need more? For higher volumes, multiple organizations, agencies and integrators, dedicated environments or on-premise — let us talk about Enterprise.
Prices in USD · No card for the Free plan · Cancel anytime.
iOS and Android
Get the receiver app
The paired device only receives notifications addressed to its deviceId. Confirm with a tap from the notification, your wearable or the app itself.
iPhone· iOS 17+On the App Store
Download on the App StoreAndroid· Android 8.0+v1.4build 532 MB
Enable “unknown sources” when installing the APK outside the Play Store. Signature verification stays inside the app.
- Pair by QR or code
- Multiple profiles per team
- No third-party telemetry
- ACK from wearables
9:41PINGWAY
Notificaciones
device:android-01
Comanda mesa 12
✓ ACK2× pizza margarita, 1× ensalada
142 ms · ACK
Backup completado
prod-db · 2.4 GB · 31 s
hace 2 min
Aprobación requerida
! pend.Orden #4429 — $2.480
requiere ACK
Sensor temperatura
cámara-3 · 2,8°C estable
hace 6 min
Start delivering what matters
Create your organization, generate an API key and send your first alert in under 5 minutes. Free plan, no card required.