Progress
What works today
Wardentry is in development and not open to sign-ups yet. This page says where it actually stands, so you can judge for yourself whether it is worth joining early.
There are no dates here on purpose. I am building it on my own, and a date given now would be a guess.
Working today
Passes carry an entry count and a validity window
A pass can allow ten entries, or be valid between two dates. The count is enforced at the gate, and a repeated scan is never double-counted.
QR codes scan on an ordinary phone
The scanner runs in a browser and returns admit or deny. Verified on a real handset against a pass shown on another screen.
Every scan is logged
Each entry attempt is recorded with its outcome, so the record behind later reporting already exists.
Organizations are separated from one another
Each organization's data is isolated at the storage layer, with tests that prove one organization cannot read another's.
Sign-in, and signup with no invite required
Accounts exist and are protected. Anyone can create an organization; usage is capped per organization rather than gated in advance.
Roles for staff
Separate permissions for administrators, the people running an event, and the people scanning at the door, enforced on every request.
Events, members, access points and passes
Creating and changing all of them, each scoped to one organization. Archiving an event stops its passes working.
Rules an organizer sets over a whole event
A cap on entries no pass may exceed, and when entry is possible — an absolute window, particular hours of the day, or both. The stricter of the event rule and the pass wins, and a rule that cannot be read denies rather than admits.
Passes delivered by email
A pass goes out by email with a page the attendee can return to if they lose it. Revoking the pass closes that page too.
Entry history and CSV export
Filter what happened at the door and export it, for your own records or for a venue or sponsor.
Counts on a dashboard
Total and per-event counts, including denials by reason, without reading a log.
Scanner links tied to one event
A link issued for one event and one door, which can be revoked and re-issued from the console.
Building now
The console
The web app for all of the above, run end to end against a real gate: a pass issued, emailed, opened, and scanned. What's left is the guided first run for someone who hasn't seen the data model, and staff invites confirmed with a second real person joining.
Planned before beta
Access limited to particular services or areas
A pass that opens the gym and the pool but not the sauna. Committed for the services track; the scanner already knows which door it is standing at.
Wardentry is built by Nikita Cherevko, a backend engineer with fourteen years across logistics, ecommerce, fintech and pricing — systems where a count has to be right, because a number that is wrong costs somebody money.
More about who is building thisIf this is the shape of what you need, the waitlist is where to say so. Early partners hear first when the beta opens.
Join the waitlistThis page last changed on 14 August 2026.