GateRev
Gate-first yard management
The digital gate for factories and logistics centres.
GateRev is built to digitise the whole life of a truck or visitor at your site: the carrier registers the visit before it happens, logistics approves it into a time slot, the barrier reads the plate and opens on a match, the weighbridge checks the net against the delivery note and pushes the result to the ERP you already run, and every step lands in a record that settles an argument months later.
GateRev
Features
The visit is registered before it arrives
The carrier or driver books through a public portal — identity, plate, cargo, delivery-note reference, preferred time. The queue at the gate is shortened by work that happened yesterday.
Time slots instead of a morning rush
Logistics approves each visit into a slot bound to the warehouse plan, with holiday calendars and automatic moves. Docks stop being either idle or three trucks deep.
ANPR and QR at the barrier
The camera reads the plate and matches it against the approved visit; the driver confirms with a QR pass or a PIN. On a match the barrier lifts without anyone leaving the gatehouse.
Safety training checked at the barrier
The visit is checked against your EHS records. An expired or missing safety induction raises an alarm and keeps the barrier down — the check happens where it can still prevent something.
Weighbridge to ERP without retyping
Weights are recorded at the scale, net is calculated and compared to the delivery note, and the result is pushed to your ERP or MES over a signed webhook. Tare deviating from a plate's own history raises an alarm.
An audit trail that holds up
Every visit, plate image, condition photo and weighing time lands in an append-only record — enforced by a database trigger, not by the absence of an edit screen. When a damage claim arrives three months later, the timestamps are the answer rather than the argument.
Who it's for
For sites where the gate is the bottleneck.
High truck traffic, a safety obligation towards everyone who drives in, and an ERP that needs the numbers to be right.
Factories with heavy truck traffic
FMCG, food and electronics plants where inbound and outbound flow is constant and a blocked gate stops a line.
Logistics centres & warehouses
Sites running docks against slots, where turn-time, dwell and detention are numbers someone is measured on.
Industrial zones with many contractors
Where a large share of the people driving in do not work for you, and their safety induction is still your obligation.
- Languages on the driver side; the staff console has five
- 7Languages on the driver side; the staff console has five
- ANPR vendors supported — Hikvision and Axis, confirmed on your own camera before go-live
- 2ANPR vendors supported — Hikvision and Axis, confirmed on your own camera before go-live
- Automated unit tests, plus an end-to-end suite, counted by machine in October 2026
- 3,000+Automated unit tests, plus an end-to-end suite, counted by machine in October 2026
- Full database restore in the last drill, 5,636 visits recovered
- 1.61 sFull database restore in the last drill, 5,636 visits recovered
What changes
What changes on Monday morning.
Every row below is a job someone on your site does by hand today.
| Your morning today | With GateRev |
|---|---|
| Carriers email arrival requests, and someone copies the details into a list. | The driver self-registers from a phone in seven languages, and back-office approves in one click. |
| Paper slips, a logbook, and photos in a chat group. | One append-only trail — every plate, gate, dock and weighing event, kept together. |
| The guard cross-checks plates by eye. | The plate is confirmed over several consecutive reads. An ambiguous read goes to the guard rather than through silently. |
| Nobody can say who is on site right now. | A live evacuation list and a one-click drill, with a roll-call report to keep. |
| Weight fraud surfaces months later, if at all. | A tare more than 20% off that plate's own history is flagged at the weighbridge, and the net is checked against the dispatch order. |
| “Who is late? Who never came at all?” | Turn-time, on-time share, no-show rate and dock utilisation, with a per-carrier scorecard you can export. |
Your morning today
Carriers email arrival requests, and someone copies the details into a list.
With GateRev
The driver self-registers from a phone in seven languages, and back-office approves in one click.
Your morning today
Paper slips, a logbook, and photos in a chat group.
With GateRev
One append-only trail — every plate, gate, dock and weighing event, kept together.
Your morning today
The guard cross-checks plates by eye.
With GateRev
The plate is confirmed over several consecutive reads. An ambiguous read goes to the guard rather than through silently.
Your morning today
Nobody can say who is on site right now.
With GateRev
A live evacuation list and a one-click drill, with a roll-call report to keep.
Your morning today
Weight fraud surfaces months later, if at all.
With GateRev
A tare more than 20% off that plate's own history is flagged at the weighbridge, and the net is checked against the dispatch order.
Your morning today
“Who is late? Who never came at all?”
With GateRev
Turn-time, on-time share, no-show rate and dock utilisation, with a per-carrier scorecard you can export.
One visit, end to end
The same arrival, from the driver's phone to the audit trail.
Six steps, each one replacing something a person does by hand today.
- 01
Before arrival
The driver pre-registers
From a phone, in one of seven languages. No email to anyone, and nothing retyped into a list afterwards.
- 02
Approval
Back-office approves in one click
Where a site needs several approvers the chain runs in order, and the first signature does not open the gate.
- 03
At the gate
The plate is read, then confirmed
Blacklist, tenant and safety checks all run before the barrier moves. A read below the confidence floor never opens anything by itself.
- 04
On site
A dock, and the route to it
The yard board shows who is waiting, who is at a dock, and for how long they have been there.
- 05
At the scale
The weighing is checked twice
Against that plate's own history and against the dispatch order, so an anomaly is caught at the weighbridge rather than at the year-end audit.
- 06
Afterwards
It lands in the trail
Every plate, gate, dock and weighing event in one append-only record — edits and deletions are refused by the database itself.
Carriers
Before the truck reaches the gate
The cheapest minute at the gate is the one removed the day before. Carriers book, accept your rules and report delays themselves — the gate only checks what was agreed. The carrier portal is free for carriers.
Invited, verified, approved by you
You send a sign-up link. The dispatcher confirms a work email; your admin decides who gets in. The company ID is checked for format and check digit (RS, HR, SI, ME, MK, PL, RO) — not yet against a public register, so the decision stays with your admin.
Your rules, accepted before the first booking
The carrier sees your booking rules and accepts that version before booking — in the portal and for a TMS API key alike. A booking without accepted rules is refused.
Arrival time and delays from the source
A TMS sends and updates the expected arrival time through the API; the driver can report a delay, or that the truck will not come, with a reason. No location tracking.
No-shows: a warning first, then fewer privileges
The no-show rate per carrier is measured over 7 days from your own data. First a warning; if it continues, auto-approval is switched off and the booking cap halved. No fines, no public list, no rating shared with other customers.
A dispute before the consequence
The carrier sees every counted no-show and can dispute it within 3 working days; while a timely dispute is open, the stricter step does not apply.
Made for a phone in a parked truck
No countdowns, buttons of at least 48 px, and the pass tells the driver not to use it while driving. GateRev never needs the driver's continuous location.
Carrier ratings are deliberately never shared between customers: what a carrier does at your gate stays with you.
In daily use
The details that decide a gate's day
What a site manager notices in the first week. Every one of them is already running.
The wrong truck never leaves with the right goods
For orders with a pickup code, loading needs the code and a four-way match — order, carrier, plate and driver. At the scale, net weight is checked against the dispatch order within a 2% tolerance, and tare against the plate's own history.
Trailers are tracked, not remembered
Every trailer is an object in the system. A drop-off is proven at exit and matched to its pick-up, so nobody walks the yard with a clipboard looking for one.
A lunch break is not a new visit
A truck that leaves for a break comes back into the same visit with one click — no second registration, no duplicate in the count.
The guard never retypes a plate
When a read is unclear, the guard's console pairs a camera barcode scanner with an on-screen keyboard. A terminal without a physical keyboard is enough.
Ready for the auditor and the DPO
The trail is kept for 24 months, and every month removed leaves a sealed record of what went and when. A checked document is stored as a keyed fingerprint, never the number itself, and every person can get an export or an erasure.
An outage never locks anyone in
When the system loses the cloud, exit is unconditional — even for a vehicle on the deny list — so no truck is trapped, for operations or for an evacuation. A live evacuation list and a one-click drill keep the roll-call report for ISO 45001.
See a real visit log before you talk to anyone
This is the visit log a site downloads from GateRev as a spreadsheet: one row per truck visit — slot, arrival and departure, plate, carrier, the reason for any manual release, and container and seal numbers as declared and as seen at the gate. Sample data only: the companies and drivers are made up.
Download the sample visit log (CSV)Spreadsheet · 5 sample visits · opens in Excel
GateRev on one page (PDF)PDF · one page · no prices
One run, no paper
A minute from a driver's morning.
Pre-registration on the phone, the pass, the gate, the dock and check-out.
One visit, recorded
The product itself, on screen.
From the driver's form to the audit trail — a screen recording, not an illustration.
Early access
A limited number of sites, and the gate is set up with you.
GateRev is in early access. We take on a few sites at a time so each gets the attention a gate deserves, and what those sites need is what gets built next.
What runs today
The full gate flow — registration, approval, slots, plate matching, weighbridge capture and the dashboard — behind more than 3,000 automated unit tests and an end-to-end suite. Every release has to pass them before it ships.
What you need
A gate worth digitising and someone who owns what happens at it. ANPR cameras, a barrier controller and a weighbridge if you have them — GateRev works through your own controller's interface, and what your site has is checked against our compatibility list before anything is promised. Your ERP receives the result over a signed webhook with retries, so your integration team gets a contract rather than a project.
How to start
Send us a site plan and a description of a normal morning: how many trucks, how many docks, what happens when a driver arrives without a booking. You will get back which parts of GateRev earn their place at your site and which do not, before anyone commits to anything.
Measured, not claimed
Measured on the build that ships.
Each figure comes from a load test or a delivery gate on that build, and carries the conditions it was measured under.
Gate processing, p95 170 ms — and 344 ms under 117% load
Two hundred registrations with fifty live dashboard connections: p95 170 ms at baseline, and 344 ms when the same load was re-run on a shared host at 117% saturation. The figure and the load are published together, because a latency figure without its host conditions is a number, not a measurement.
Daylight saving, tested on both weekends
A slot at 02:30 on the night the clocks move either happens twice or not at all, and a yard planned around it is wrong for a day. The transitions are tested for Ljubljana and Belgrade specifically, because a corridor operation runs across both.
Server time is the authority
A driver's phone or a gate terminal two hours out of sync cannot move a timestamp: the skew is detected and raises an alarm instead of quietly rewriting when a truck arrived. Tested by simulating a clock two hours ahead.
A tare that disagrees with its own history
Weighings are compared against that registration plate's own record, and a tare more than 20% away from it raises an alarm. The fraud this catches is old, ordinary and expensive, and it is invisible to anyone reading one weighing at a time.
A retry cannot double-count a visit
Ingest is idempotent by event id, so a lost response and a client retry produce one visit rather than two. The dull correctness that decides whether the yard count on the dashboard is the yard count in the yard.
Seven languages, because the driver is not local
EN, SL, DE, SR, HR, PL and RO for drivers, five for the staff console — Slovenia sits on the corridor between the EU and the Balkans, and the driver at the barrier frequently shares no language with the dispatcher who approved the visit. A gate that only speaks the site's language is a gate with a queue.
Pricing
Per location, on an annual contract.
Billed monthly. No charge per driver, per booking or per truck — the price does not rise when your traffic does.
Included for every location
- All modules — gate, docks, weighbridge, EHS, evacuation and the evidence chain
- Unlimited drivers, carriers and bookings
- Seven languages for drivers
- Data stays in the EU
Implementation is agreed separately: setting up your site, connecting the equipment at your gate, acceptance with real trucks and on-site training for every shift.
We send a quote after a short call about your gate — the number of gates and docks, the weighbridge, cameras and traffic. Several sites are quoted together.
Ask for a quoteRequest early access to GateRev.
Tell us about your site and what you need to be able to prove. We reply within one business day, and you will be talking to the engineers rather than a sales desk.
GateRev
Tech stack
- Next.js
- TypeScript
- Prisma
- PostgreSQL
- Zod
- Playwright
FAQ
Frequently asked questions
Is plate recognition biometric processing?
No — but plate data is still personal data, and we treat it as such. A registration plate is not a physiological or behavioural characteristic, so reading one does not trigger Article 9; it does not put the processing outside the GDPR, and the retention, access and audit controls apply to it like anything else. That distinction is exactly why plate reading is in the product and face-based identification of staff is not: identifying a person by face would be Article 9 processing and a high-risk system under the AI Act.
Does this replace our ERP or WMS?
No, and it is not trying to. GateRev owns the gate, the yard and the weighbridge, and pushes the result — net weight against the delivery note, arrival and departure times — to the ERP or MES you already run, over a signed webhook with retries and a dead-letter queue. Named connectors for a specific ERP are built with a named customer rather than invented in advance, and one rule holds either way: an ERP that is unreachable must never stop the gate, so inbound checks are advisory and never a block.
Is this an eFTI platform?
No — eFTI is a regime for exchanging freight information with authorities, with its own certification. What GateRev provides is the integration opening: the structured record of a visit that such an exchange needs as its source.
Does the gate keep working if the internet drops?
Not on its own, and we will not claim otherwise. What is built today is a centrally hosted system: during a WAN outage the barrier does not lift automatically, and the documented behaviour is that the gate falls back to the guard rather than failing open or failing silent. Autonomous operation at the edge is designed and on the plan, and until it ships this answer stays as it is.
Who is responsible for barrier safety?
Your installer, and that is deliberate. The interface in our code can only send open — there is no close command in it at all. Closing, the safety loops and the photocells stay with the barrier controller already fitted at your gate, which is also where responsibility under EN 12453 sits. A software vendor taking that on would be taking on a liability it cannot discharge from a database.
How long does it take to get running?
It depends on the site, and we scope it with you. What drives it is the number of gates and docks, whether the weighbridge and ANPR cameras are already in place, and how quickly your ERP team can take a webhook. Send a site plan and the list of what is installed, and you will get a schedule with names against it.
How do we start?
With a conversation about your gate, not a demo of ours. Tell us the traffic, the docks and what happens today when a driver arrives without a booking, and we will tell you which parts of GateRev earn their place at your site and which do not. Early access is a limited number of sites at a time, so each gets the attention it needs.
Have a project in mind?
Tell us what you want to build. We respond within one business day.
Built by an EU-incorporated senior team — 20+ years in enterprise delivery.