Notifications and alerting
ORCA
Your own push service.Inside your own perimeter.
ORCA delivers notifications to your apps and devices over a connection it maintains itself, parses your logs and turns alert storms into single incidents. In-app push never passes through a Google or Apple service.
Self-hosted on servers you run. In-app delivery needs no third-party service, and ORCA has been tested with no route to the internet.
Every number above is invented. The layout is modelled on ORCA’s own dashboard.
Your own push service.
In-app push never passes through Google or Apple. The connection, the identity and the record all live on servers you run.
Every app holds its own line.
Three live lines run from ORCA to a field tablet, an operations console and an orders service, each carrying a pulse toward its endpoint.
A device is woken when you need it.
A single pulse travels from your backend through ORCA to Field tablet 07, which is tagged wake.
Back online, caught up.
The tablet's line goes dashed while ORCA holds three messages marked kept; when the line returns the messages move to the tablet, fetched on reconnect.
And every delivery is on the record.
A dispatch log lists four deliveries — in-app push, web push, email and webhook — each marked sent, the webhook after one retry.
An alert storm becomes one incident.
Repeats of the same alert fold into a single incident, so the on-call phone rings once. If it gets worse, it rings again. Acknowledge, resolve or silence it from the console.
From a raw line to a structured event.
Point a firewall, a server or a cloud account at ORCA and pick from 47 built-in parsers — or paste a sample line and let the advisor choose. Lines nothing matches wait in a dead-letter queue until you replay them.
Four ways to reach the right person.
- In-app push
- Over the connection your app holds to ORCA.
- Browser push
- Standards-based web push to subscribed browsers, delivered through each browser’s own push service.
- Over TLS, with a templated subject and body.
- Webhooks
- Signed with HMAC-SHA256 and retried with backoff.
Client SDKs for both ends of the line.
The Android and iOS libraries hold the connection, reconnect with backoff and catch up on missed messages, so your app only handles the message. The Python library is the other end: it provisions devices and sends their wake signals.
Built as the backbone of the platform.
ORCA is the messaging layer the Appdirs platform is built around. Device management wakes its devices through it, AuthX authenticates the services that send, and Kestryn and Prospica send their audit and server logs to it.
See the platform- MDM
- wakes managed devices through ORCA
- AuthX
- authenticates the services that send
- Prospica
- sends its audit and server logs
- Kestryn
- sends its audit and server logs
Built to run where you run it.
- Organisations
- Applications, policies and incidents are isolated per organisation — multi-tenant, managed from the console or the API.
- Roles and audit
- Custom roles with fine-grained permissions, scoped per application, and an audit log of every permission-gated change.
- Outbound, guarded
- Every outbound destination passes an SSRF guard, and webhooks are signed so the receiver can verify them.
- Observable
- Prometheus metrics, with separate liveness and readiness probes.
- Self-hosted
- Ships with a hardened systemd unit and a Dockerfile. Optional integrations — single sign-on, an external event store, certificate issuance — connect out only when you turn them on.