Drop a “Sign in with Chirp” button into your app in five minutes. It’s standard OpenID Connect, with two differences from Auth0 / Clerk: you never receive the user’s email, and the user ID you get is unique to your app — so there’s no cross-app profile of your users for anyone to leak, sell, or subpoena.
Drop in any OIDC client — nothing else to learn. Test against real, signed tokens before you have a single user. Hosted today. Self-hosting is coming, and the source will be published before general availability.
Free for private apps with up to 25 people · no credit card · AGPL-3.0 source published before general availability
Register an app, drop in the button, handle the callback. Any standards-compliant OIDC client works.
/dashboard → New app name myapp.com redirect_uri https://myapp.com/auth/cb → client_id cs_dev_7f3a09c2… (public PKCE client — no secret)
Download the example's files: /docs#integrate-web # Set CHIRP_CLIENT_ID in .env, then: cargo run --locked
POST /token grant_type=authorization_code&code=<one-time>&code_verifier=<pkce>
→ { "id_token": "<jwt>", "token_type": "Bearer", "expires_in": 43200 }That's it — verify the RS256 JWT against our JWKS and you know who signed in. Full quickstart, plus iOS & Android →
Mint a genuine, RS256-signed ID token for a made-up user of your own app, from the app’s page in your dashboard. Hand it to your app in a test environment and prove your token handling works — before you onboard a single real user, with no email round-trip.
Test tokens name a test: user and are signed by your account’s own test key under a test issuer, never by Chirp’s production key. So your production verifier rejects them, and they can never impersonate a real user anywhere. Your test environment accepts them by trusting that test issuer, which the dashboard shows you. How to verify one →
/dashboard → your app → Mint a test token sub test:alice → eyJhbGciOiJSUzI1NiIs… # a real signed JWT iss https://signin.chirpauth.com/test/tnt_… # in your test environment, trust that issuer: OIDC_ISSUER=https://signin.chirpauth.com/test/tnt_…
The two differences are the whole reason to choose Chirp. You get a stable per-user ID scoped to your app — a pairwise sub derived with HMAC-SHA256, under a secret key only Chirp holds, from the user’s account id and your app id — and you never hold their email. So you can’t leak it, sell it, or be subpoenaed for it; and two apps comparing notes can’t tell they share a user. A cross-app profile of your users simply never exists.
Everything else is the same OIDC you already know. No social-login aggregation, no analytics pixels, no marketing email: Chirp sends your users sign-in and account mail; the messages they’ve allowed your app to send reach them in Pigeon. Your users sign in with a short-lived email link or a passkey — you never see or choose which.
It's an identity provider — you shouldn't take its security on faith. The source isn't public yet; we'll publish all of it under AGPL-3.0 before general availability, so you can read it before you trust it.
The hosted service runs the same code we'll publish. No proprietary fork, no “enterprise” black box.
Self-hosting the same code in your own AWS account is coming, but isn't ready yet. Chirp is standard OIDC, so you can move to another provider now, or to your own copy later — either way, your users’ IDs change when you do. How to carry them across.
Build on Free — private apps for you and up to 25 people you invite, unlimited apps, no card. To let anyone sign up, switch to Starter or Pro. One subscription per account, not per app; paid tiers are counted in monthly active identities.
Self-hosting the same code for $0 is coming; it isn't available yet.
signin.chirpauth.com issuerPricing is per tenant — one subscription per Chirp account, no matter how many apps you register. On Free, every app is private: you can always sign in, and up to 25 people you invite can too, counted across all your apps combined. Starter and Pro are counted in monthly active identities — distinct end users who sign in to any of your apps in a calendar month (UTC).
Chirp is standard OIDC, so you can move your apps to another provider; your users’ IDs will change when you do. We're building self-hosting so you can run the same AGPL-3.0 code in your own AWS account instead — it isn't ready yet, and your users’ IDs change that way too. How to carry them across.
Any standards-compliant OIDC client works — openid-client, AppAuth, ASWebAuthenticationSession, whatever you already use. App registration and test tokens live in the dashboard and a plain HTTP control plane.
Yes — unlimited private apps, no card. You can always sign in to your own apps, and you can invite up to 25 people across them with single-use links. Anyone else who tries sees that the app is private. When you want open sign-up, Starter is $5/mo.
A short-lived email link or a passkey (Face ID / Touch ID / hardware key). No passwords to leak, nothing to phish. The sign-in page and sender domain are the same for every Chirp app — one flow your users already know.
As little as possible: an email and what's needed to sign in. Identities are pairwise per app. To bill paid tiers we record which of your users signed in each calendar month — no timestamps, no count of sign-ins. When a user deletes their Chirp account, their entry becomes an anonymous placeholder that still counts for that month. No analytics, no selling. Read the policy.
No — on purpose. Sign-in always happens on signin.chirpauth.com and sign-in emails always come from the same sender, for every app. Users learn one legitimate domain, which makes look-alike phishing stand out. White-labeling auth would train them out of that.