GateRev
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 posts tare and gross straight to your ERP, and every step lands in a record that settles an argument months later. The software runs on staging today; we are looking for the first sites to prove it in.
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 code or a card. 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
Tare and gross are captured automatically, net is calculated and compared to the delivery note, and the result is pushed to ERP or MES. 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.
Design partners
Two or three sites, and the criteria written down before we start.
A pilot that cannot fail is not evidence. These are agreed in the contract, measured by the system's own KPIs, and reviewed with you every two weeks.
Who it suits
High truck traffic — on the order of a hundred movements a day — gate queues that already cost someone their morning, an IT contact who can make decisions, and the willingness to sit with us twice a month while it is being proven.
Success criteria, agreed up front
Written into the contract before anything is installed. The kind of thing they look like: gate processing under five minutes for four visits in five across sixty days; zero lost events; nine drivers in ten completing registration without phoning anyone.
Measured by the product, not by us
Those numbers come from the same KPI reporting the product ships to its operators — turn-time, dwell, dock utilisation, no-show, detention. The pilot generates its own evidence, which is the only kind worth having in the room afterwards.
Sixty to ninety days, and it is not free
A free pilot signals a product with nothing to lose, so this one is paid and fully credited toward the contract if it converts. First partners get founding-customer terms and real influence on the roadmap instead of a discount on a thing nobody has proven yet.
Measured, not claimed
The target was written down before the measurement.
Which is the only order in which a benchmark means anything. These come from the S08 load test and the S14 delivery gate, on the same build that runs on staging today.
Gate processing, p95 317 ms
Two hundred registrations through the gate flow, 95th percentile at 317 milliseconds. The goal — under 500 ms — was fixed in the sprint definition before anything was run, so the number could fail. Reference points in this category talk about a healthy gate transaction in minutes.
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.
Five languages, because the driver is not local
EN, SL, DE, SR and HR in v1 — 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.
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 — into the ERP or MES you already run. It is an integration, not a migration.
Is this an eFTI platform?
No. eFTI is a regime for exchanging freight information with authorities, with its own certification, and we do not claim to be a certified platform under it. What GateRev provides is the integration opening — the structured record of a visit that such an exchange needs as its source.
How ready is it, honestly?
The software is built and runs on staging today — pre-arrival registration, approvals, slots, the gate flow, the weighbridge capture and the dashboard, with the full gate check suite passing. What has not happened yet is a real installation: the hardware phase, where ANPR cameras, a barrier and a weighbridge are wired to one specific site, starts with the first signed pilot. So every integration on this page is proven against our own rig and not yet against your equipment, and we will say which is which at scoping rather than after.
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.