OpenFence
For moving & logistics operators

Geofencing for moving & logistics fleets — every arrival is evidence

OpenFence turns each crew or truck crossing a job site into a signed, timestamped event — arrival, on-site load time, departure — and pushes it straight into your dispatch and billing. The same platform we're building to run our own moving company, WDA Movers.

We run WDA Movers — and we're building OpenFence to run it on.

Moving runs on timing you shouldn't have to call for

When a crew arrives, how long they're on site, and when they leave is billable, tariff-governed, and the backbone of the day's schedule. Most fleets still find it out by interrupting the crew.

Dispatch by guesswork

Without live arrival and departure, slotting the next job — or a same-day move — is a phone call and a hope.

Your crew's word, unbacked

Tariff-relevant time-on-site lives in a driver's memory. A signed, timestamped record backs what your crew already told you — automatically.

Customers in the dark

On moving day, silence breeds worry; "where's my crew?" becomes a support call instead of a notification.

How a move becomes evidence

The same real path every job runs — geofences, devices, events, signed webhooks, evidence.

  1. 1

    Geofence each stop

    Origin, destination, and terminal — a geofence around each address.

  2. 2

    Devices on the crew / truck

    Registered devices report location as the move runs.

  3. 3

    enter / exit / dwell

    Arrival at the stop, load duration on site, departure — at origin and destination alike.

  4. 4

    Signed webhooks

    Each event pushes into your dispatch & billing — HMAC-verified, retried, dead-lettered on failure.

  5. 5

    Explainable trace

    Every event is backed by a defensible trace — evidence, not a guess.

See the evidence a move leaves behind

Every arrival, on-site dwell, and departure lands as a timestamped, signed event — and each one pushes a delivered webhook into dispatch. Here's what that evidence trail looks like in the dashboard, for an example moving company:

openfence.ai/dashboard/events
OpenFence dashboard event feed: a moving company's trucks arriving at and departing job sites through the day, each row a timestamped geofence enter or exit with a delivered webhook.
openfence.ai/dashboard/events
OpenFence event detail: a geofence.enter arrival opened to show its signed payload and a webhook delivered with HTTP 200 in 118 ms.

Illustrative — example tenant (Acme Moving Co) with sample data. The dashboard UI is the real product.

The same platform you'd build on

Nothing here is moving-only plumbing. OpenFence is domain-agnostic by design — the same PostGIS geofences, enter/exit/dwell events, signed-webhook contract, rules engine, and explainable traces serve any fleet. This page just speaks moving's language; the engine speaks any vertical's.

Put your next move on the record

Start free — $0 today, 14-day trial. Drop a geofence on a job site and watch the evidence appear.