njokey
Products · Verify · Early access

Know where work happens.

An employee says they're working from London. Verify checks — many independent signals, one confidence score, nothing to take on trust. Pure software, live in days.

Desktop + phone pair Confidence score Consent-based
An employee holding a phone showing the Njokey app's verified location check
Verified · with consent
01 /// Pair

Two devices, bound once.

An employee accepts an invite, installs Njokey Desktop and Njokey Mobile, and the two are bound together with public-key cryptography — so only that phone can vouch for that computer.

Public-key pairing, once
Only that phone vouches for that computer
Linked to your existing IdP login
02 /// Verify

Checks run on your terms.

At login, on a schedule, before access to sensitive systems, when policy requires it, or on demand — with consent, and never in the background.

At login · scheduled · on-access · on demand
Consent prompt, employee-visible log
Nothing runs off the clock
03 /// Correlate

Signals that are hard to fake all at once.

The desktop reports network and device context; the phone reports physical context. The engine cross-checks them: do the locations agree? Does the Wi-Fi match? Is the travel speed since the last check physically possible? When the desktop says London and the phone says Nairobi, verification fails.

Desktop: IP, device posture, timezone, network
Phone: GPS, Wi-Fi, Bluetooth, motion, integrity
Cross-checked into one confidence score
04 /// Report

HR sees the answer, not the surveillance.

No raw GPS coordinates, no movement trail. Just a clear, signed result — Verified · London · 99% confidence · evidence on file — defensible for the company, private for the person.

Verdict + confidence, not coordinates
Signed evidence on file
Same audit trail as every Njokey product
See it work

Run a check. Watch the signals agree — or not.

An honest check-in verifies. A spoof attempt fails. Same five signals, in front of you.

Try itInteractive demo · sample data

Pick a scenario and run the check — the same five signals, correlated in front of you.

HR sees the verdict and confidence — never raw coordinates

Why teams choose Verify

From "we assume they're there" to "we can show they're there."

Pure software

Nothing to buy, ship, replace or track. Runs on the devices your team already owns.

Live in days

Accept an invite, install two apps, set approved regions. No procurement, no rollout project.

Privacy-respecting

Consent-based, work moments only, employee-visible log. A verdict — never a movement trail.

Grows with you

Day-count alerts and audit evidence from day one. Add Anchor V1 when your data demands hardware.

Where teams use it

One check, many jobs.

HR

Confirm remote and hybrid staff are where policy expects.

Finance

Catch cross-border days before they become tax or payroll exposure.

IT & Security

A phishing-resistant login factor, tied to a verified place.

Operations

Roll out in days across the whole team — no hardware to ship.

FAQ

Questions, answered.

Verify vs Anchor V1

Start with software. Anchor when it matters.

Both run on the same policy engine and audit trail — the difference is how strongly place is bound to the work.

Verify — for most teams
Software verification
  • Desktop + phone, cryptographically paired
  • Independent signals fused into a confidence score
  • Nothing to procure — live in days
  • Right for policy compliance, tax day-counts, payroll accuracy
Anchor V1 — for sensitive data · coming soon
Hardware-bound verification
  • A different trust model — not Verify with a USB stick
  • Tamper-resistant secure element; keys never leave the device
  • Continuous verification while the key is plugged in
  • Right for export controls, defence, regulated data
Explore Anchor V1
Early access

Know where work happens.

Book a demo, or start early access today.