WayfindYour customers see where the van is. Nobody's server sees where your customers live.
Live delivery and school-transport tracking with no tracking company in the middle. Your customers' addresses stay on the device you typed them into. The person waiting taps a short link — no account, no app to install, no cookie banner.
On the way
Not before
08:59
2 stops before yours — about 4 minutes away if the van came straight here.
Live positionWhat a customer actually sees. The arrival time is worked out on their own phone, from what the van is sending out — which is why it can say "not before" honestly instead of inventing a promise it might break.
Who it's for
It starts as one address and a link. It grows into whatever you actually run.
The same thing underneath, and the words change to yours. A pharmacy does not have "jobs", it has patients; a school does not have "customers", it has parents who sign up once in September.
Restaurants & takeaway
One order at a time
Orders arrive singly and go out as riders come free. Send the link with the order confirmation, before the food is even bagged.
Pharmacies
What happened at the door
Delivered, refused, nobody home — each one signed by the driver's phone so it cannot be quietly changed afterwards, with an optional doorstep photo. When a regulator asks, the answer is already on file.
Courier fleets
Planned in the morning, reflowed all day
Rounds ordered by real driving time, handover between drivers mid-shift, and a skip that surfaces the second it happens rather than at close of business.
School transport
A route is fixed for a term; the driver is not
Parents sign up once and their link keeps working, even when today's driver is a substitute. No live map of other people's children — a parent is told about their own stop and nothing else.
What's different
Every other tracker asks you to upload your customer book.
That is the part worth reading twice. A normal tracker needs your stops on its computers before it can work out anything at all. So if a company you have never heard of gets hacked, your customers get hacked with it. Wayfind is built so there is nothing there to steal.
| Where does it live? | A normal tracker | Wayfind |
|---|---|---|
| Your customers' addresses | On their computers, in one big database shared with every other company that signed up | On the device you typed them into. They are never sent anywhere — the van gives off a scrambled fingerprint of its round, never the round itself |
| Where your drivers are | Recorded centrally, and kept indefinitely | Sent straight from the driver's phone to the people holding a link, and to nobody else |
| The tracking link | Needs an account, or quietly reports back the moment it is opened | A short link whose secret half your browser never sends to anyone. There is no server that could receive it |
| The arrival time | Worked out on their computers, so they find out which doorstep each person is waiting at | Worked out on the waiting person's own phone. Nobody is ever told which stop you care about |
| The map and the directions | A maps service billed per lookup, forever | An ordinary map file your device reads the few pieces it needs from. Nothing to look up, nobody to bill you |
The catch, stated plainly: because the van talks to your customers directly, they see it moving while the driver's phone has signal. When it does not, the page tells them so — "nothing has come through for ninety seconds, so the last position has been taken down" — instead of leaving an old dot sitting on a map looking live.
The part nobody advertises
An estimate says "about". A floor says "not before". A settled delivery says "delivered 14:32". And when there is no map for the area, it says that — instead of a number somebody might drive to.
Promising too much is how every tracking product fails: a confident arrival time that was really a guess, a green dot for a phone that died forty minutes ago. Wayfind is built so the screen cannot promise more than it knows. Each thing it says is backed by something the van actually reported, and there is no setting, anywhere, that turns a guess into a promise.
How it works
Four steps, and none of them is "create an account for your customer".
Type the address
Your device looks it up in a public map file it reads directly, the way you'd open a page in a book. The address you typed never leaves your browser, because there is nowhere to send it.
Send the round to a driver's phone
The whole round travels as one locked file — a QR code on screen, or a file you send — that only the phone you set up can open. Someone photographing that code over your shoulder gets nothing but noise.
Give each customer their own link
Same round, one link each, carrying only that person's own stop. They can watch the van until the link runs out, and never learn a thing about anybody else on the round.
The record is the receipt
Delivered, skipped, failed — each one signed by the driver's phone at the door, with an optional photo locked to that record. Not a line in a spreadsheet somebody could tidy up later.
Get started
Open the console and send one delivery.
There is nothing to install and no account to create to try it. The console runs in an ordinary browser tab and works with no company servers behind it at all — which is also exactly how a fleet running its own setup uses it for real.
Run it on your own machine
A depot can run the single box that connects its drivers and its customers, sitting on its own network. Your fleet's traffic never touches anybody else's equipment.
Or run nothing at all
Letting us host it works the same way, because the parts we hold are only ever scrambled files, billing records and "something changed" nudges. If our servers were broken into, what was taken would be useless.