Wicket tells your app which email address is signing in.
That's all it does.
Free for apps only you sign in to. $5 a month for up to 100 people, $20 for up to 1,000.
It proves the address with a link mailed to it:
-
They type their email address.
-
They open the link Wicket mails them and press Continue.
-
They're back in your app, signed in.
Try it signs you in to a small demo app with a real link, in about 30 seconds, and shows the ID token an app gets. It makes no account and keeps no session, but like any sign-in it leaves the records under What Wicket keeps: the address you type is in the audit record for 30 days.
Set it up with your coding agent
Paste this into your coding agent:
Add Wicket sign-in to this app. Install the wicket CLI from
https://wicketauth.com/cli/ and run wicket setup with this app's name and
an http://127.0.0.1 callback URL. Show me the link it prints: I'll open it
and approve (the first time, I sign in with my email). Then follow
https://wicketauth.com/llms.txt to add sign-in, using the WICKET_ISSUER and
WICKET_CLIENT_ID it prints.
- Open the link, click Approve. Your agent prints a link. Open it; the first time, sign in with your email. Check the page shows the code your agent printed, and click Approve. That is the only step that needs you.
- Sign-in works on
http://127.0.0.1: the agent registers your app, puts itsclient_idin your config and wires up the sign-in. - Then production. Add your real callback URL and the same app signs people in in production.
What it will never do
Each of these follows from that one sentence. Each is a choice, not a missing feature, and none of them is coming later. If you need one, Wicket is the wrong choice for you, and it is better to know that now.
- The address is the account. Your app knows a person by their email address and nothing else. Someone who changes address gets a new account, and nothing moves to it.
- No passwords. The link mailed to the address is the proof, so there is no password to store, leak or reset.
- No client secrets. Every app is a public client using PKCE, so there is no secret to keep, rotate or leak.
- The proof lasts 10 minutes. An ID token lasts 10 minutes, and there are no refresh tokens. Then your app keeps its own session, and when that ends, the person signs in again.
- Every app sees the same address. A person's subject
(
sub) is their email address in every app that uses Wicket, so apps can match their users with each other's. There are no per-app identifiers. - No migration to another provider. Not now, not behind a setting, not through a tool. If you outgrow Wicket, you move your app to another sign-in provider yourself.
- People only. Wicket signs in people, nothing else: no machine or service identities. The CLI's credential is your own key for managing your apps, not an identity anything signs in as.
Pricing
Free for apps only you sign in to; pay when other people do. Each app has its own plan. Starter and Pro are counted by monthly active users: the different addresses that open a sign-in link to that app in a calendar month (UTC), whether or not your app goes on to finish the sign-in. The count starts again on the 1st.
| Plan | Price | Who can sign in |
|---|---|---|
| Personal | $0 | only you: your own address, and its
plus-addresses (you+anything@example.com) |
| Starter | $5 a month | up to 100 monthly active users |
| Pro | $20 a month | up to 1,000 monthly active users |
Every new app starts on Personal. Anyone else who tries to sign in to it
is refused before any email is sent, and told the app only lets its
developer sign in (HTTP 402, developer_only:
the guide has the details).
Over a plan's limit, Wicket refuses people who haven't opened a sign-in
link to the app that month: they are sent the link, and continuing from it
shows a page saying the app is full this month (HTTP 402, over_limit:
the guide has the error and its fields).
People who already have keep signing in. There is no grace period and no
overage charge. Past 1,000, new people are refused too: there is no bigger
plan.
You can have up to 10 apps at once, on any mix of plans, and register up to 20 a day (UTC); deleting an app doesn't give a registration back. Paying doesn't raise either.
Upgrade an app to Starter or Pro from its page in the dashboard. Stripe bills it monthly, in advance, from the day you buy it: the first charge is the full price, not a part of a month, and pays for a month from that day. Monthly active users are still counted by calendar month, whatever day you buy. Starter and Pro are available to customers in the United States for now. Sign-in and Personal work everywhere.
Switch or cancel any time from the same page, under Manage billing. Switching between Starter and Pro takes effect at once, and Stripe charges or credits the difference for the rest of the month you paid for. After you cancel, the app keeps its plan until the end of the month you paid for (a month from the day of your last charge), then moves to Personal; from then on you can delete it. There are no refunds for part of a month, but your first charge is refunded in full if you ask within 14 days. The terms have the details.
Wicket is run by Stackwell Labs LLC, a company registered in Wyoming, USA. To reach a person about billing or anything else, write to support@stackwell.tech.
What Wicket keeps
The main records are below. The privacy page lists every one, with how long it is kept and why, and says how to ask about or delete what names you.
- For each app: its name, its redirect URIs and its developer's email address.
- For each sign-in: the link and the code, stored only as hashes. A link expires after 15 minutes and a code after 5, and each works once.
- Counters for the sending limits: 5 links per address per 15 minutes, 300 per network address per hour.
- An audit record of every sign-in step and every app change, naming the address and the app (and, for a CLI approval, the network address that asked), kept for 30 days for investigating incidents.
- For each app and month, a one-way hash of each address that opened a sign-in link to it, to count its monthly active users. Each month's hashes are deleted a month after it ends.
- For an app on Starter or Pro: its Stripe customer and subscription ids, and the plan's state. Card details go to Stripe, never to Wicket.
- For each developer: their email address and when they first signed in to the dashboard or approved the CLI, and, if one of our ads brought them from outside the EEA, the UK and Switzerland, its campaign and Google's id for the click, which go to Google Ads to count the sign-up. Visitors in the EEA, the UK and Switzerland get no advertising cookie, and no page carries a tracking pixel.
Wicket's servers also keep operational logs for 14 days, and its stored records are kept in backups for up to 35 days. There is no table of your apps' users: beyond the records the privacy page lists, Wicket keeps no list of who has signed in to an app.
Five companies handle part of it. Amazon Web Services runs Wicket's servers and stores its records, in the US. Resend sends the sign-in mail. Cloudflare's Turnstile, on the sign-in page, sees the browser's network address and tells people from bots, so that nobody can make Wicket mail strangers; it is the only script from anyone else on any page. Stripe takes payments. Google Ads is sent the click id of a sign-up one of our ads brought, as above.