Rift adds a cryptographic verification layer to every notification your team receives. Here is how it works.
When your monitoring system or alerting tool fires, Rift intercepts the payload and generates a cryptographic signature using HMAC-SHA256. This signature is bound to the content, timestamp, and source identity — any tampering invalidates it.
Before a notification reaches your phone, inbox, or Slack channel, Rift checks the signature against its registry of trusted sources. Verification happens in milliseconds — typically under 50ms end-to-end.
Verified alerts are relayed with a visible trust indicator. Unverified or tampered alerts are quarantined, flagged, and optionally dropped — your team only sees what you can trust.
Every verification event is written to an immutable audit trail. Export SOC 2 and GDPR-ready reports with one click. Your auditors will thank you.
Drop-in SDKs and webhook adapters for the tools you already use.
pip install rift-verify. Five lines to wrap your existing alerting logic.
npm install rift-verify. Async-first, TypeScript-friendly, works with Express or Next.js.
go get rift.dev/verify. Zero-allocation hot path for high-throughput services.
gem install rift-verify. Drop it into your Rails app or Sidekiq worker.
Most teams are verifying their first alert within 30 minutes.
Talk to Us