01
The code is never the same twice
Each board issues a random single-use token that expires on a timer you choose, 15 seconds to 15 minutes. Issuing a new code revokes the old one.
Proof the walk-in was checked.
A named person, at the fridge, at the time the check was due. Not a sheet filled in after service.
Most records of physical work aren't evidence.
Every common way of recording that a task happened can be produced by someone who never went. That's fine until a client, an auditor, or an insurer asks you to prove it.
01
A printed sticker is a photo
Static QR codes get photographed once and forwarded. Every scan after that looks identical to a real one, because it is one.
02
Paper is written from memory
Clipboards and sign-off sheets get filled in at the end of a shift, or by a colleague. There's no timestamp anyone can defend in a dispute.
03
GPS is spoofable and unpopular
Mock-location apps are free, accuracy indoors is poor, and asking staff to be tracked all day is a fight most operations teams would rather not have.
Three moments. Zero guesswork.
The board
A short-lived code
One token at a time. Then it's gone.
The person
Sign in and scan
Opens in the browser. Needs a named account.
The record
A verified event
Person, place, time. Then the job starts.
Code lifetime
15s-15m
per device, default 60s
Uses per code
One
then revoked
Device offline after
3 min
without a heartbeat
Signature window
±5 min
clock skew tolerance
As easy as any QR code. Much harder to fake.
Scanning feels completely ordinary. Underneath, four separate things have to line up before Anchor records anything: a live code, a registered board, an open site, and a person with an account.
01
A live code
Single-use, on a timer. Only the hash is stored.
02
A registered board
Signed hardware, bound to one named location.
03
An open site
Closed sites cannot redeem, even with a live code.
04
A named account
A signed-in member of your organisation.
02
Any phone camera works
Scanning opens a normal web page. Nothing to install, nothing to pair, nothing to hand out to a subcontractor on their first day.
03
Tied to a named account
A scan only counts once a signed-in user in your organisation redeems it. That's what turns 'someone scanned' into 'Jordan scanned'.
04
No location tracking
Anchor never asks for or stores GPS coordinates. The work is proven by the board in the room, so there's nothing invasive to opt into.
05
Boards that know the schedule
In scheduled mode a board shows nothing until its work is due, then goes quiet again once the job is done. Early scans aren't possible.
06
The right form, automatically
A verified scan can open a patrol checklist, raise an incident, or create a task, chosen by rules you set, not by the person scanning.
Printed codes, GPS apps, and Anchor.
The three ways teams usually answer “did the work actually happen?”, and what each one can really tell you.
Photographed and shared
- Printed QR
- The photo is still a working copy
- GPS app
- Doesn't use a code
- Anchor
- Single-use, then it expires
A specific indoor room
- Printed QR
- Works, but any copy counts
- GPS app
- Weak and spoofable indoors
- Anchor
- Bound to one board in that room
Nothing to install
- Printed QR
- Any camera will scan it
- GPS app
- Needs an app on the phone
- Anchor
- Opens in the phone's browser
No location data
- Printed QR
- Nothing to collect
- GPS app
- That's the whole mechanism
- Anchor
- Never requested or stored
Which person did the work
- Printed QR
- A name on a sheet, at best
- GPS app
- Proves a device, not a person
- Anchor
- A signed-in account in your org
The right task on arrival
- Printed QR
- The person picks the form
- GPS app
- Check-in is the whole event
- Anchor
- Rules open the portal or task
The workflow changes. The evidence standard doesn't.
A kitchen check, a patrol, a contractor visit, a care round. Different jobs, one record. These are applications of the same platform, not separate products.
Everything behind the scan.
The scan is the evidence. What you build on top of it is the operation: schedules, forms, incidents, and the rest of your stack.
Devices that prove themselves
Each board holds an ECDSA P-256 key generated on the hardware. The private key never leaves it, and every request it makes is signed and time-bounded.
Portals you assemble
Build the on-phone screen from headings, checklists, timers, photo capture and forms. Text, number, temperature, yes/no, select, checkbox and photo fields.
Workflows with conditions
Trigger on any event, filter on fields like the user's role or a submitted reading, then open a portal, create a task, or raise an incident.
Signed webhooks
Subscribe an endpoint to the event types you care about. Every delivery carries an HMAC-SHA256 signature, and secrets are encrypted at rest.
Metrics and scoreboards
Define counts, ratios, distinct locations or time-between-events, group them into tables, and compare people across 24 hours, 7 days, 30 days or all time.
Roles, audit and multi-site
Per-resource permissions across eighteen areas, an audit log of administrative changes, and organisations split into sites with their own timezone and status.
A board for the wall
A browser tab on a screen you already own is a live board. We hang a wall board later if the kitchen needs one.
Start with one kitchen.
We set up the walk-in check with you. A browser tab on a screen you already own is enough for the first log.
Questions that come up first.
The short version: no app, no GPS, one use per code, and a named person behind every record.
What stops someone photographing the code?
Each code is single-use and dies on a timer you set: 15 seconds to 15 minutes. A photo is a dead credential the moment a new one is issued, and often before.
Do people need to install an app?
No. Scanning opens a normal page in the phone's browser. They do need an Anchor account in your organisation, so a scan is always tied to a named person.
Do you collect GPS or track phones?
No. Anchor never asks for or stores coordinates. The work is proven by the signed board in the room, not by the phone's location services.
What hardware do we need?
A browser tab on a screen you already own is a live board. We add a wall board later if the kitchen needs one.
Can anyone with the link check in?
No. Redemption requires a signed-in user in your organisation, at an active registered device, at a site that's open. Fail any of those and nothing is recorded.
What's the difference between Presence and Scheduled?
Presence boards always show a code. A scan means someone was here. Scheduled boards stay idle until work is due, then light up. A scan means this job happened here, now, by this person.
Do you sell a different product per industry?
No. Security, facilities, hospitality, contractors, property, logistics, care and compliance are use cases on one platform. Plans are priced by sites and boards, with unlimited users on every tier.
How much does it cost?
We set the first kitchen up with you. Email hello@averanta.studio. There is no self-serve checkout yet.
Start with one kitchen.
We set up the walk-in check with you. A browser tab on a screen you already own is enough for the first log.