About Services Tools Blog Contact us

Passwordless Email Sign-in

Signs people in with an emailed one-time code or link, creates the account on first use and can restrict the full archive to a paid tier.

  • Web Tools
  • Cross-sector
  • Tool
  • Product
  • Cloud
  • 2026

The problem

A short-lived product loses signups when it asks people to invent a password. A research archive also needed a clean way to charge for its full history. Every forgotten password then became a reset request for support.

What it does

The visitor types an email address. The server saves a scrambled copy of a short-lived code or link and emails it with Postmark or Mailgun, without revealing whether the address was already known. Entering the code signs the visitor in and creates a user on the free tier if there was none. A Stripe checkout can upgrade them to a paid tier, and expired codes are cleared on a schedule.

Outcomes

  • Nobody has to invent, store or reset a password.
  • The account is created on the first successful code.
  • A paid tier opens the rest of the archive.
  • Expired codes are deleted on schedule, so they do not pile up.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Passwordless sign-in

Hash only
Codes sent today
46
Passwords stored
0
New accounts this week
12
1. Email

The reply is the same whether or not this address already has an account. A correct code creates the user on the free tier.

2. Send
Ready to send

Archive Free

Latest five notes
Notes 5 of 12
DateNoteTier
9 Oct 2026How a Saturday count is readFree
2 Oct 2026Queue time at the Harbour Street shopFree
25 Sep 2026Winter opening hoursFree
18 Sep 2026What a fitting slot includesFree
11 Sep 2026A note on gift wrapFree
7 earlier notes stay on the paid tier
Free

£0

The latest five notes. Created on the first code that works. No card.

Full history

£6 / month

Lifts this session only. The sample card is not a live charge.

Code cupboard

Stored hashes The code itself is not kept
CodeAddressStateExpires
482916[email protected]UsedToday, 10 min
110294[email protected]Active9 min left
773001[email protected]ExpiredYesterday
550812[email protected]Expired3 days ago
904433[email protected]UsedYesterday

An hourly job deletes expired hashes so the table does not grow. Used codes stay until the audit window ends.

How it works

  1. Accept an email address and store a scrambled copy of a short-lived code or link.
  2. Send the code without revealing whether the account exists.
  3. Check the code and its expiry, sign the visitor in and create the user if needed.
  4. Show free visitors a short feed and paid visitors the full history.
  5. Take payment through Stripe, and confirm it safely twice without charging twice.
  6. Clear expired codes on a schedule.

Pipeline

flowchart LR
  A[Email] --> B[Send code]
  B --> C{Code valid?}
  C -->|Yes| D[Session]
  D --> E[Free tier]
  E --> F[Stripe]
  F --> G[Paid tier]