Welcome to Litehook
Litehook checks each incoming event, shapes it and sends it where it needs to go.
If it can make an HTTP request, it can send to Litehook. Each sender is a source with its own source address and secret.
A source's flow decides what happens to each event: a short notification on your devices, kept in your inbox; a forward to one or more destinations, retried; or both. Use it to hear when a backup fails or a deploy finishes, or to pass a provider's webhooks on to your own services.
Reading preferences
Choose a colour and appearance for the docs.
Where to go next
Start with Getting set up. It covers creating a workspace, sending a first event and enabling notifications.
Getting set upCreate a workspace, send a first event and enable notifications.
Sending eventsSource addresses, fields, grouping and what each response means.
Receiving notificationsWhich devices hear about what, summaries, quiet hours and your inbox.
Building with LitehookA prompt for AI coding assistants and examples for common tools.
SecurityHow your events and secrets are protected.
Limits and fair useLimits per source, workspace and session.
How it works.
- Secure. HTTPS only. Each source has its own 256-bit secret: a signing secret encrypted at rest, or a URL token stored only as a SHA-256 hash. Notifications are encrypted for each device, so push services can't read them.
- Tidy. Repeats collapse into one, busy sources can arrive as a summary, and each device chooses what it hears about and when.
- Clean. A notification is a title, a message and a level, always shown as plain text. The app loads no third-party scripts, and visits are counted first-party, without IP addresses or browser details.