Record 4302:14:07
Checkpoint scan, North Stairwell B2
- Device time
- 02:14:07
- Server time
- 02:41:30
- Signed on the enrolled phonePending
- Follows record 42Pending
- Countersigned by GuardHelmPending
Checked by your browser as the page loads.
Patrol records your clients can check
Scheduling, patrols, reports and timecards for security companies. Every scan is signed on the guard’s phone, with or without signal, and your client can check the receipt without an account.
$2 per active guard a monthNo contractNo setup fee
Pre-release, taking its first pilot companies. See what is built
One night, on the record
An overnight post at a sample site, from clock-in to the client’s question. Every step is built.
Clock in
On the guard’s own phone, after the post orders. Weak GPS never blocks it; the office gets a flag.
Checkpoint scans
QR tags printed from the console. A hand-entered checkpoint is labelled manual in the signed record.
No signal
The phone signs the scan and keeps it. The guard sees what is still waiting to send.
Back in range
GuardHelm countersigns on arrival. Device time and server time both stay on the receipt.
Timecards
Built from signed punches. A correction sits beside the original, never over it. Payroll CSV.
The client asks
Send a signed link. It opens without an account, and the guard’s identity is not shown.
Try to backdate a scan
A sample record in GuardHelm’s production format, checked by your browser. Move the scan time back, the way a missed round gets covered up.
Signed receipt
Sample record, demonstration keys
Record 43
Checkpoint scan at North Stairwell, level B2, signed by the guard’s enrolled phone
- Site
- Riverside Tower
- Post
- North Gate
- Activity
- QR checkpoint scan
- Device time
- 02:14:07 EDT
- Server time
- 02:41:30 EDT
- Server sequence
- 412
Record 42
Loading Dock B
······
Record 43
North Stairwell, B2
······
Record 44
Roof Access Door
······
Change the device time on record 43
Now 02:14:07 EDT
-
Device signature
Signed on the guard’s enrolled phone. Only that phone holds the signing key.
-
Chain link
The next scan, record 44, points back to this one, so a removed or swapped record shows up.
-
Countersignature covers this record
GuardHelm countersigned this exact record when it arrived at 02:41:30.
A valid receipt shows
- The enrolled phone signed it
- It follows the record before it
- GuardHelm received it at the server time
It does not show
- Who was holding the phone
- That the phone’s clock was correct
- The hours that will be billed
When a client disputes a shift
QuestionScreenshots and PDF exportsGuardHelm
What the client getsA copy you madeA link to the signed record
Who vouches for itYour company, the party in the disputeGuardHelm’s signature, checked against published keys
If it was edited laterYour client can’t tellThe check fails
Technical details
A receipt is the ASCII string guardhelm.receipt.v1, a line feed, then RFC 8785 canonical JSON,
signed with ECDSA P-256 and SHA-256 (ES256). The signature is 64 raw bytes. Records signed on the phone use the
same scheme with the tag guardhelm.event.v1, so any ES256 library can repeat these checks.
- Receipt, signed bytes
- Receipt signature, base64
- Record 43, signed bytes
- Demonstration public keys, JWK
These sample records were produced by GuardHelm’s own signing code using throwaway keys. They do not describe a real company, guard or site. Customer receipts are verified against the keys GuardHelm publishes.
A guard app built for the night shift
Every record stays on the phone until the office confirms it, and the guard can see what has arrived.
“This app crashes in between scans, hence making me look as if I don’t do my work.”
- Dark when the phone is dark
- With a night dim for unlit areas.
- Controls at least 56 points
- Clock-in is bigger still.
- Clock-in never waits
- Not on GPS, signal or the office.
- Location you can see
- The app always shows when it is on.
- Their own phone
- iPhone or Android. No company devices.
- Plain words
- “This phone cannot reach the office”, never a code.
What is built
GuardHelm is pre-release. Everything below marked Built works in the console or the guard app and passes its automated tests; none of it has run a customer’s shift yet. We support each pilot company’s first shifts. Reviewed .
AreaWhat it doesStatus
Signed recordsSigned on the phone, chained and countersigned. Corrections are added; originals are never rewrittenBuilt
Guard appiPhone and Android. Clock in and out, rounds, reports, schedule, inbox and own records, all offline. Not yet in the app storesBuilt
Patrol toursQR checkpoint tours, manual fallback, printable tag sheetsBuilt
OperationsOne queue for coverage gaps, missed check-ins and reports awaiting reviewBuilt
Sites and mapPost fences drawn on the site map, last known positions with their ageBuilt
SchedulingWeekly roster by site and post, with shift changes guards acknowledgeBuilt
Time and payrollTimecards from signed punches, exception review, approval, payroll CSVBuilt
ReportsDaily activity and incident reports, incident photos, supervisor review, release to clientsBuilt
MessagesOffice and site threads between the console and the guard appBuilt
ClientsSigned receipt links that open without a client loginBuilt
Client billingInvoices to your clients, payments received and agingBuilt
LicencesGuard licence records and expiry trackingBuilt
VoiceCalls with guards, in the app and by phoneNext
Data exportPayroll CSV today; a full export of all records is being builtNext
Field useFirst real shifts with pilot security companiesNext
Pay for the guards who clock in
Office staff and clients who never clock in are free, and so are the first 30 days.
Regular
$2per active guard
per month
$40 monthly minimum, which covers up to 20 guards
- Month to month, cancel any time
- No setup fee, no device minimum
- No automatic increase at renewal
Founding First 20 companies
$1per active guard
per month
$29 monthly minimum, price fixed for 12 months
- Everything in Regular
- In exchange for ongoing product feedback
Voice is coming. $3 per active guard ($2 founding), only for the guards you turn it on for.
Published pricing in this market
Each vendor’s own website, applied to 100 guards. Reviewed .
| Vendor | Published price | At 100 guards |
|---|---|---|
| GuardHelm | $2 per active guard, $40 minimum, month to month, no setup fee | $200 |
| GuardsPro | $5 to $10 per user, 3-user minimum, add-on modules extra | $500–$1,000 |
| QR-Patrol | Priced by guard band, $59 to $376 a month on the Base plan | $376 |
| Guard Owl | From $300 a month; terms add 5% at each renewal | $300 or more |
| Belfry | Quote only | Not published |
| Trackforce (TrackTik, Silvertrac) | Quote only | Not published |
Prices change, so confirm with each vendor. Trademarks belong to their owners. Ours stays low because there is no field sales team, no setup project and no server fleet: GuardHelm runs on Cloudflare’s network.
Questions
Something else? Email hello@guardhelm.com and the people who build GuardHelm will reply.
Do we have to leave our current system to try GuardHelm?
No. A pilot can start with one site while your other sites stay where they are. We set up that site’s posts and guards with you and print its checkpoint tags.
What counts as an active guard?
A person who clocks in at least once in the calendar month, whatever their role, so a supervisor who works a shift counts. Guards who don’t work that month aren’t billed, and every billed person is listed on the invoice. Office staff and clients who never clock in are free.
Do guards need company phones?
No. The guard app runs on the guard’s own iPhone or Android phone. Each phone is enrolled to one guard, and a lost or replaced phone can be removed from service in the console without losing that guard’s records.
What happens when a phone has no signal, or the battery dies?
Every record is signed and saved on the phone first, and stays there until GuardHelm confirms it was received. The guard can see what is still waiting. If the phone dies, anything it already signed is sent the next time it is switched on and has signal.
Is location tracked when guards are off duty?
By default the guard app reports location on and off duty, under your company’s policy. You can turn tracking off for the whole company or for an individual guard. There is no covert mode: the guard app always shows when location is on, and tracking never delays a clock-in or clock-out.
What can our clients see?
Only what you share. A client link opens a single record. Reports released to a client are written without the guard’s identity, pay or hours.
What does verification actually check?
Each record is signed with a key held on the guard’s phone, and GuardHelm checks that signature when the record arrives, then countersigns it. Anyone holding a receipt can check GuardHelm’s countersignature against its published keys, without an account and without our cooperation. If a single byte has changed, the check fails.
Can we cancel, and what happens to our records?
Billing is month to month, so you can stop at any time. Payroll exports are CSV today, and a full export of your records is being built. Receipts you have shared stay checkable after you leave, or if GuardHelm shuts down, because checking one needs only the receipt and a copy of GuardHelm’s published keys.
Who do we contact if something goes wrong?
During the pilot, email hello@guardhelm.com and we support your first shifts directly. Guards never wait on us: clock-in and scans work offline and are sent when the phone has signal.
How does a pilot work?
Email us and we’ll set up a 30-day pilot with you: your sites, posts and guards, printed checkpoint tags, and support through your first shifts. No card or contract is required.
Try GuardHelm free for 30 days
We set up your posts and guards with you, print your checkpoint tags and support your first shifts. No card, no contract.
hello@guardhelm.com