shared-signals.dev

About

About this site

shared-signals.dev is a developer’s guide to the OpenID Shared Signals Framework, CAEP and RISC: how the standards fit together, every event type, who implements them, and a live Transmitter and Receiver to test against.

Who runs it

The site is maintained by Mike Kiser, a co-chair of the OpenID Foundation’s Shared Signals Working Group.

Independent, not official

This is not an OpenID Foundation website, and nothing here is normative. The explanations, examples and sample code are written to make the specifications easier to approach; where they and the specifications disagree, the specifications win. The authoritative texts are on openid.net, and their sources are on GitHub.

Spec facts on these pages were last checked against openid/sharedsignals at commit a34d6ff (2026-09-01).

What’s here

  • Learn — the concepts: streams, SETs, subjects, delivery and discovery.
  • Specs — the three Final specifications, the CAEP Interoperability Profile and the RFCs underneath.
  • Events — every CAEP, RISC and SSF event type, with example SETs.
  • Implementations — products that implement the standards, and the interop events they took part in.
  • Playground — a live sample Transmitter and Receiver and a SET inspector.
  • Working group — who writes the specifications, and how to join in.

Contributing

The site is open source at github.com/derrumbe/shared-signals.dev. Corrections, new implementations and improvements are welcome:

Privacy

Most of the site stores nothing about you. The playground keeps your sandbox credentials in your browser, and sandbox links carry them in the part of the URL that is never sent to a server. What the site does store:

  • Playground data — the streams, received SETs and logs you create. They’re deleted after 7 days without use.
  • Optional passkey accounts — your passkeys’ public keys, a label for each (like “Mac, added 10/14/2026”), your sandbox’s credentials (secret encrypted), and active sign-in sessions. No email, name or password. Signing in sets an HttpOnly session cookie, plus a five-minute cookie while a passkey prompt is open; there are no other cookies and no analytics. Accounts are deleted after 90 days without use, or immediately from the account panel.
  • Request logs — requests to the playground’s API (the sample Transmitter and Receiver, the inspector and accounts, not the reading pages) are logged by Cloudflare for troubleshooting: time, address, status and the request’s details, which can include your IP address. The logs are kept for a few days and seen only by the site’s maintainer.
  • Session signals — while signed in, signing in and out sends CAEP events about your account to your sandbox’s streams. They identify you only by a random account id, and you can turn them off.

Pages load their fonts from Google Fonts, so your browser contacts Google when you visit. Don’t put real personal data in events you send; this is a public test service.

How it’s built

Static pages built with Astro, served by a Cloudflare Worker. The playground’s Transmitter and Receiver run in the same Worker, with state in Durable Objects; the code is in worker/ and is meant to be read.

Credits

The standards are the work of the Shared Signals Working Group, its editors and contributors — listed with each specification. Interop results come from the OpenID Foundation’s reports and participants’ own write-ups, linked on the Implementations page.