Free push notifications for everything you run — with nothing to host, no per-device fee, and no password database anywhere. Then, when you're ready, the same channel can sign people in.
Works tonight with anything that can make an HTTP request. Nobody's permission required.
# In the app: Apps → ＋ → New token curl -X POST https://api.lauther.id/v1/push \ -d '{"token":"lpt_…", "title":"Backup finished", "message":"214 GB · disk 91% full"}' → your phone buzzes. # Need a human to decide something? curl -X POST https://api.lauther.id/v1/approve \ -d '{"token":"lpt_…", "title":"Deploy to production?", "wait":25}' → {"ok":true,"response":"approve"}
You've probably used something like this before. These are the parts that made you stop.
The whole onboarding. No SDK, no OAuth dance, no dashboard to configure first.
Sign in with a link sent to your email — no password exists. The address is used for sign-in and recovery only; no service ever sees it.
Apps → ＋ → New token. Copy the lpt_… string. Each one is revocable on its own.
A cron job, your NAS, a CI step, a webhook field in software you already run. One URL.
Lauther speaks the Pushover API for tools that let you change its server URL — and anything with a webhook field works as-is, which covers the rest.
Notifications are how most people arrive. They're not the point. Because every Lauther message travels over a relationship rather than an address, it can carry a question back.
Point a notification at a page on your own site. The person taps it and lands there signed in, ready to answer with a real keyboard. Decisions get buttons; conversations get a page. POST /v1/push {path}
One call pushes “Approve €2,140?” and waits up to 25 seconds for a thumb. Built for agents, deploys and anything spending money. POST /v1/approve
Two endpoints and a QR. Each user arrives as a per-service alias and a random ID — no email, no password, nothing to breach. POST /v1/pair/start
Big action? Fire a challenge; their phone asks for a fingerprint. Denying is one tap, approving never is. POST /v1/identity/verify
Fan out to subscribers you cannot enumerate. Perfect for a status page or an alert channel. POST /v1/topics/publish
Some sites only accept an address. Mint a throwaway one that arrives as a notification — and kill it whenever you like.
That last part is the quiet pitch for anyone running a web app: a browser tab can't reliably reach someone who closed it, can't ask for a fingerprint, and can't put a button in the notification shade. Shipping a native app to get those costs you two codebases, two store accounts and a permanent maintenance tax. Here your users install one app, once, for every site that speaks Lauther.
One buzzes your actual phone in about a minute, one is a public room with real people in it, and one works before you install anything. All three →
Paste a token, make your phone buzz, block a script on your own approval — and leave with recipes for curl, Uptime Kuma, Home Assistant and GitHub Actions.
A real public channel. Join it with a name that carries no email, no number and no password — and get a notification when someone mentions you.
Washing machine, freezer, the front door you left unlocked. No account with anyone, no identity at all — just a token and one HTTP request.
Every tool below is good at its job. Here is the real difference — in both directions.
Pushover and ntfy are good at what they do, and we deliberately speak Pushover's API so their ecosystem works here. The difference is what a message can carry: a pipe moves text, a relationship can ask a question, prove who's answering, and be revoked.
Not a rival — use passkeys. They fix passwords brilliantly, but they can't reach you, so after a passkey signup the site still asks for your email. We're the reach-and-consent layer beside them.
Alias relays work anywhere email is accepted — a real adoption advantage we don't have. But everything else about email survives: spam folders, tracking pixels, forever-databases. We drop the medium.
Hide My Email is our closest cousin and Apple's reach is enormous. But it's Apple-only, email-shaped underneath, and gives the service no direct channel back to the person.
It doesn't prove you're a unique human — one person can hold many identities by design, so it's the wrong tool for one-per-person voting or coupons. And it protects you from services correlating you, not from us: our servers know which identities are yours, because that's what makes one-tap revocation and recovery possible. Read the security model, limits included →
Everything on the personal side is free and always will be — including recovery, biometrics and revoking anyone who annoys you. See pricing →
Installing the APK: open the download, allow “install unknown apps” for your browser if prompted, install, done.