See it live

Three demos.
All of them real.

Start with the Workbench if you came for notifications — token in, phone buzzing, recipes out, about a minute. The room is where the identity side lives: six things a login usually can't do, all of them working. And Hearth runs before you install anything at all.

01

Register

An identity that exists only between you and one site.

02

Log in

Come back tomorrow, or on a computer that has never seen you.

03

Be reached

The site tells you something while the tab is closed.

04

Re-authorize

Something irreversible asks your phone first.

05

Come straight back

Tap the notification, land on the right page, already signed in.

06

Burn it

End the relationship. Every route back dies at once.

Real · your token, your phone
For everyone who came from Pushover

The Workbench

Paste a token. Press a button. Feel your pocket. Then flip the priority to +2 and see what "gets past quiet hours" means, and make a script block on your own approval — fingerprint and all.

Leaves with you: working, copy-paste recipes for curl, Uptime Kuma, Home Assistant and GitHub Actions, with your token already filled in.

Open the workbench →

What you can do there

  • Send yourself a push — title, message, priority −2…+2
  • Trigger an Approve / Deny and watch a poll loop wait for your thumb
  • Demand requireBiometric and see confirmedBy come back
  • Copy ready-made integrations for the tools you already run
  • Read the exact HTTP of everything the page just did
Real · not simulated
All six, in one room

The Lauther room

One public channel. Reading is open to anyone; speaking needs a name the room can hold you to — and that name is the only thing it ever gets. Nothing to hand over, nothing to reset.

This one is live. Real messages, real people, and a real notification when someone mentions you while the tab is closed. If you are early, the room may be quiet; that is what early looks like.

Open the room →

What you can do there

  • Join and pick the name the room knows you by
  • Sign out and come back — by name, or straight from the app
  • Get mentioned and have your phone tell you
  • Delete everything you wrote — irreversible, so your phone is asked first and the server checks the answer
  • Tap the notification and land back in the room signed in
  • Burn the identity in the app and watch the room stop recognising you
Works with or without the app
The half that needs nobody's permission

Hearth — your own things

A home hub with no identity in it anywhere. The washing machine finishes, the freezer starts warming up, and the front door has been unlocked for twenty minutes — so it asks whether to lock it, and wants a fingerprint before it will.

Underneath, on the same page: the Home Assistant automation, the curl, the token, and every call the page just made.

Open Hearth →

Why this one matters

  • Your own devices, reaching you directly — with no account at a vendor, no bot in a chat workspace, no mail relay in between
  • Works tonight, with anything that can make an HTTP request
  • Shows what priority 2 is for — the one level that gets past your quiet hours
  • An approval with a physical consequence, which is the only kind that really tests whether you trust it

Runs against a simulated phone by default, so you can try it before installing anything. One button switches it to your real device.
How messages behave

Three kinds of notification

Which one you get is decided by what the service sends, never by a flag it can set — so the buttons, the urgent channel and the quiet-hours bypass stay reserved for the moments that deserve them.

Approval

Approve or deny, in the shade

The only kind that ever gets buttons, because a decision is the thing that deserves a fingerprint. A service can ask for a real owner check — and a phone with no lock can still deny; approving is what takes the proof.

Message with a destination

Tap it, land there signed in

Tapping opens that page on the service's own site, already signed in as your pairwise identity, at the exact thing that needs an answer.

Plain message

Nothing to answer

Your washing is done. Your report was received. It opens in the Lauther app and that is the whole story.

Being straight with you about these

  • The workbench is entirely real. Everything it sends goes to the phone behind the token you paste — which is why it asks for one instead of pretending.
  • The room is real and it is public. Anyone can read it, anyone with the app can post, and messages persist. Treat it like a noticeboard, because that is what it is.
  • Hearth is a fictional hub, but every call it makes is the real public API. In simulated mode everything stays in your browser, and the request log says simulated beside each call it kept local.
  • Lauther relays no personal data. If a service needs your name or address, it asks on its own site, with its own form and its own privacy policy — where it belongs.
  • Pairwise identity keeps two sites from matching you to each other. We could still correlate them; that limitation is written down in the security notes, in the open.