TechRevati · Video Analytics Platform

A forklift nearly hit someone? You know about it the same shift. Clip, place and time — your team acts, and the video stays on your site.

Existing cameras → verifiable safety events on an on-site NVIDIA GPU edge box. Only metadata and short evidence clips leave the building — every alarm is reviewed by a human. When the link drops, the offline queue keeps every event until reconnect.

Start for €2,900: three weeks on your own cameras, then three months running live on your floor — included. After that, you decide. Excl. VAT · one site · up to 6 cameras · a limited number of PoC slots each quarter.

3 weeks and you know whether it works on your floor
174.9 / s measured ceiling, one GPU
12 cameras per recommended box
0 inbound ports; video stays on site
A zone drawn on a fixed camera. The edge box turns frames into events; only the event and a short clip leave the building. Illustration — synthetic scene, not footage from an installation.

Problem & ROI

Near-misses cost more than cameras

Warehouse EHS teams already film the floor. What they lack is a reliable signal when a forklift enters a pedestrian path — without streaming continuous video to a US cloud or inventing worker scores. Downtime, sick leave and insurance premiums from a forklift collision dwarf the cost of the cameras. A near-miss is the cheap lesson, and VAP puts it on video so your team can act on it.

  • Forklift vs pedestrian

    Zone and line rules turn camera frames into reviewable near-miss events — evidence at decision time.

    Forklift safety landing →

  • Insurers & audits

    Operators confirm or dismiss every alarm. Audit trail: camera, zone, time, clip, model version, decision.

  • Works when the internet doesn’t

    Durable offline queue on the edge — events buffer locally and retry until the link returns. Every PoC ends with reconnect tests, and their result goes into the handover record; the buffer has a documented ceiling, and if it is ever reached the box reports the gap instead of hiding it.

Compliance paperwork, drafted from your system

Vendors document their own compliance; some add blank templates. The paperwork the law puts on you — AI Act Art. 26(7) works-council notice before go-live, Art. 26(9) DPIA, ROPA, retention proof — is still yours to fill in. VAP pre-fills 17 documents from the live state of your system — the cameras, zones, retention and model versions you actually run — instead of blank templates. Your DPO reviews and signs instead of writing from scratch. Compliance deep-dive →

Data sovereignty

Video processed on your site; EU-hosted center optional; on-prem available.

GDPR by design

Events without identity; per-zone retention; Art. 28 DPA roles clear.

Hard boundaries

No face ID, no emotion inference, no worker scoring — technically enforced.

DPIA & Compliance Starter Pack

DPIA, LIA, DPA, ROPA, signage, employee notice, AI Act technical documentation, retention proof — filled in from your own system, not blank templates. They are drafts for your counsel to sign off: we assemble the file, your lawyer reviews instead of writing from scratch.

How it works

Inference on your floor. Events to the EU center.

Privacy by design: continuous video never crosses the perimeter — only structured events with short clips. Technical details (NVIDIA / ONNX).

YOUR SITE Edge box detect · track · queue zones · lines · schedule events only EU center Inbox · confirm / dismiss Alerts · Compliance Pack
Video stays on-prem; the center receives metadata, evidence clips and operator decisions.
  1. Connect cameras

    Existing RTSP cameras with a second stream — no rip-and-replace. Zones and schedules for your floor plan.

  2. Edge → events

    Local detection turns frames into verifiable events with model and rule version stamps.

  3. Human review

    Alarms reach e-mail or webhooks; operators confirm or dismiss — every decision is audit-logged.

Product: VAP

Edge video analytics for warehouses, logistics hubs and perimeter security — without streaming continuous video to the cloud.

What it does

  1. Watches — your existing cameras, analysed on site
  2. Warns — a person in the forklift lane, in a no-go zone, or too close to a vehicle
  3. Proves — your team confirms each alarm and the record is ready for the inspector

Who it is for

  • The safety lead who has to show the inspector which controls exist — not just promise them
  • The operations manager who cannot afford to lose a shift — or a person — to one collision
  • The integrator who wants to sell analytics on cameras he already installed — integrator kit
Operator review with the proof attached. Every event carries the frame, the zone it broke, the rule row version and the thresholds that were in force at trigger time — so a decision can be defended months later. Demo data; the frame is labelled as a synthetic scene inside the product.
Sites on a map, with a text alternative. Camera pins are coloured by how much open work each one has. The same list is repeated as text below the map, so the screen works without seeing it. Map data © OpenStreetMap contributors (ODbL), rendering by Leaflet.

Platform features

  • Human-in-the-loop

    No alarm becomes a decision without an operator — no automated sanctions.

  • Offline queue

    Works when the internet doesn’t — durable edge queue; every PoC ends with reconnect tests whose result goes into the handover record (buffered as long as there is local disk); the box keeps detecting for up to 30 days without reaching us.

  • How many alarms does your operator actually get?

    If there are too many, he stops looking — and that is the settings, not the man. The standard for alarm systems (EEMUA 191) puts numbers on it: ≤ 6/h per operator is fine, ≤ 12/h is the ceiling, and past 30/h the system is no longer doing its job. We measure it on your site and tell you which three rules are making the noise.

  • Audit trail

    Camera, zone, time, clip, model version and operator decision — inspection-ready.

  • Milestone XProtect®

    Alarms land in your XProtect Smart Client as Analytics Events — camera, object box and zone included — posted by the on-site box to the Event Server over your LAN. Protocol-based, nothing to install in XProtect. Tested end to end on XProtect Express+ 2026 R1: the alarm arrives with the camera, the zone and the object box drawn in the alarm preview.

  • License-clean

    MIT/Apache/BSD path, CI license gate, SBOM with every release.

Use cases

Focused perimeter rules — reliable, verifiable, no individual surveillance.

  • Restricted zone

    Person dwells in a marked zone beyond threshold — per camera, zone and schedule.

  • Line crossing

    Virtual line crossed in forbidden direction — docks, ramps, corridors.

  • Forklift vs pedestrian

    Vehicle in pedestrian zone — the clearest near-miss case. Read the use-case →

    Tuned to your floor. Every site gets its own calibration on your recordings during the pilot — your aisles, your lighting, your forklifts. The number you get is yours, not an average from someone else's warehouse.

  • After-hours presence

    Presence outside defined working hours — theft and unauthorised access.

Why it's affordable

You don't pay us to stream video. You pay for verified events.

Your cameras already see every near-miss — you just can't prove it. VAP turns them into reviewable safety events on a GPU box that stays on your floor; only metadata and short evidence clips reach the EU center. That economy is why the subscription stays small.

  • Heavy lifting stays on your edge

    Inference runs on your GPU box; the center is a small EU server for events. No per-camera cloud video fees, no per-minute metering.

  • What the subscription covers

    Operator console and review, alerting (e-mail / webhook), retention and audit trail, Compliance Pack refreshes, fixes and upgrades.

  • Predictable cost

    Scales with sites and cameras under analytics — not with hours of footage. The offline queue means an outage never becomes an expensive gap.

  • Your data, your exit

    Your data always leaves with you: full export is built in. And if you’d rather run it yourself, there’s VAP Onsite. No lock-in games at renewal.

Numbers you can check

Every capacity figure comes with the box, the date and the command

“Up to N cameras” means nothing without the hardware, the date and the method. We publish all three — and the command, so your own engineer can reproduce the figure on your box. Rows that are scaled rather than measured are labelled estimate; that discipline is built into the product, not added for the brochure.

  • Measured on our lab card

    Measured ceiling 174.9 inferences/s on a Quadro RTX 6000 — 24 cameras at 5 fps with 30 % headroom already subtracted. The box we recommend for your site is sized from this figure with a wide margin: 12 cameras per box in the subscription. Sampling at 5 fps is a per-camera setting, not a compromise: zone and forklift–pedestrian rules measure duration, and 5 fps is five samples a second.

  • Your camera settings don't matter

    A frame costs 10.9–12.5 ms whether we read 1080p or a 640x360 substream, and the ceiling on 1080p input (174.9/s) matches the substream (174.7/s). Your cameras stay exactly as they are — capacity follows the card, not the camera menu.

  • The one requirement, stated plainly

    VAP needs an NVIDIA GPU on site — and we can show you why with a number: four cameras on CPU alone collapse to 5.8 inferences/s in total with a p95 of 1.07 s per frame, far outside the five-second frame-to-alert budget. A mid-range card removes the problem entirely; we check your vendor's quote before you buy.

  • Your card, measured in 10 minutes

    Bring any NVIDIA card and we run bench_capacity.sh on it during the PoC. A number from your own box always beats our table — and if it comes out lower than we sized, that goes in the written GO / NO-GO, not in a footnote.

Full capacity table per card Can you run a PoC? Check in 30 seconds

How VAP compares

Six things that decide the total cost — and who carries the risk.

Criterion VAP Typical cloud video analytics
Continuous video leaves your site No — events + short clips only Yes — streamed to the cloud
Works when the internet drops Yes — durable offline queue, retries until delivered Varies by product — ask the vendor for the spec
Face ID / worker scoring Never — technically enforced Often optional → legal risk
Data residency EU center or self-hosted Provider-dependent (often US)
Cost grows with Sites and cameras under analytics Minutes of video, retention, cameras
What the auditor gets Pack generated from the live system A marketing PDF

Start with a PoC

Every site starts with a three-week PoC on your cameras. See the PoC offer: one onboarding fee covers the install and your first three months, then you decide. Billing unit: camera under analytics. Prices exclude VAT.

Team

€249/mo

One site · 6 cameras included · +€35/cam

  • Forklift–pedestrian and person-in-zone, alerts to e-mail / webhook
  • Quarterly remote tuning + Compliance Pack refreshes
  • E-mail support, 1 business-day first response
Start with a PoC

Business

€799/mo

Up to 3 sites · 24 cameras included · +€18/cam

  • SBOM + NIS2 documentation
  • Named contact, 4 business-hour first response
Start with a PoC

Growing? Add cameras to any plan — and the moment you reach the size of the next plan, the next plan is the cheaper one, with faster support on top. One recommended box runs up to 12 cameras: Team fits one box, Site one or two, Business two or more. The number of boxes is always in your quote. First-response times are targets and run on business days, 9–17 CET. Annual prepayment: −10%.

Rather own it? VAP also comes with a one-time, permanent licence and runs on your own hardware — on site or in your data centre. Same software, no monthly fee, and support and updates come with a yearly Care plan. We check what your server can handle in 10 minutes and send you a quote — just ask.

Services

What you get beyond the software

  • A PoC in 3 weeks

    Time-bounded, on your site, with a written GO / NO-GO against measured KPIs — not a demo video. PoC offer →

  • Zone & rule tuning

    During the PoC we tune your zones and measure false alarms on your own cameras — the number is written into the handover record. We tune toward a target below 5%; it is a target, not a contractual guarantee.

  • Integrator enablement

    Install spine (center + edge + first camera → first event), zone recipes, printable checklist. Integrator kit →

  • Compliance Pack as a deliverable

    ROPA / DPIA / signage / DPA templates generated from live system facts — your DPO gets a pack, not a promise. Compliance →

  • A model tuned to your floor

    Site adaptation turns the corrections your operators already make into a candidate model. We run the training and score the candidate against the pinned one on a validation set frozen for your site — if it does not beat the incumbent, it does not ship. Your footage never leaves the building. How it works →

FAQ

Objections we hear first

Will VAP hit the brakes or warn the driver?

No. VAP never touches the brakes, and we built it that way on purpose. On-truck warning systems need a device on every vehicle, a retrofit and drivers who accept it, and when the shift is over you have nothing in your hands. VAP uses the cameras you already have and sees the crossings a sensor on the truck never will. Your team gets the near-miss on video, with the zone, the time, the model version and the operator who confirmed it, so the cause gets fixed instead of guessed at. Already have warnings on your trucks? Keep them. They beep in the moment, and VAP shows you where and when it keeps happening.

How many false alarms will my operators see?

As many as your zones are tuned for — and tuning them is what the PoC is for. Alarm volume has an industry yardstick: EEMUA 191 calls ≤ 6/h per operator acceptable and 30/h impaired, and we bring your zones under it during the three weeks, with the false-alarm rate per camera per day written into the handover record. A vendor quoting you 99% accuracy without naming the dataset and the threshold is quoting a brochure; we quote your floor.

Do workers / works council need to consent?

VAP does person/object detection — not facial recognition, emotions or worker scoring. Legal basis and works-council process sit with the customer as controller; we ship Compliance Pack templates (DPIA, signage, DPA roles) for counsel to complete. We do not invent signatures.

Which cameras work?

Existing RTSP cameras with a second stream — no rip-and-replace. Lab and PoC paths use your LAN streams; passwords stay with the operator.

We already run Milestone XProtect. Do our operators get a second console?

No. The box on your site sends each VAP event to the XProtect Event Server as an Analytics Event — with the camera reference your XProtect uses, the object box and the zone — so the alarm appears in Smart Client next to the live view. Stale events are not forwarded; a late alarm is noise. The VAP console remains the place for zones, rules, the operator decision and the compliance record. The integration is protocol-based; details are on the integrator page.

How long does install take?

With RTSP streams and the GPU host ready, installation covers centre, edge box, first camera, zone, rule and first event. The rest of the PoC is tuning around your shifts, not installing.

What happens when the internet drops?

The edge keeps a durable offline queue and retries until events reach the centre — we treat unexplained loss as a product bug. Continuous video still never leaves the site.

Who sees the video?

Nobody off-site sees continuous video. Only events (metadata + short evidence clips) go to the EU centre your tenant controls. Operators review in the dashboard; no face ID.

Which GPU do I need, and for how many cameras?

Any NVIDIA card from the Turing generation up with 8 GB and a video decoder; for a box that runs unattended we recommend 16 GB with ECC memory. Measured on a Quadro RTX 6000: 24 cameras at 5 fps, 12 at 10 fps, 8 at 15 fps, with 30 % headroom already subtracted. VRAM is 0.4 GB + 0.16 GB per camera, and decoding costs 0.217 CPU core per 1080p stream — so 4 cores minimum, 8 recommended. Other cards are scaled by FP32 throughput and published as estimates, with the method written out. Full table per card.

Do I have to reconfigure my cameras first?

No — resolution, bitrate and frame rate stay exactly as they are. A frame costs 10.9–12.5 ms at any input resolution and the measured ceiling on 1080p (174.9/s) matches a 640x360 substream (174.7/s). One thing each camera must already have, though: a second stream (substream). We size the box and the camera count on it, so a camera without one is not part of the offer — the most common reason an otherwise fine camera is left out. Most IP cameras have one, and a 640 px substream also saves ~13 % of frame time and LAN bandwidth. The full list is one page, and we check yours before the PoC.

Can it run without a GPU?

No — VAP is built for an NVIDIA GPU on site, and the numbers say why: on CPU alone one camera reaches 17.2 inferences/s (4.7x slower) and four cameras collapse to 5.8/s in total with a p95 of 1.07 s per frame, far outside the five-second frame-to-alert budget. A mid-range card is a small line in the budget, and we confirm the right one for your box before you buy.

I don't have a box and procurement takes months.

Then send us the vendor's quote before you buy — we check it against our spec within a day, so you never pay for a card the installer will refuse. You buy the box, it stays yours; your integrator can sell you one too. We neither sell nor lend hardware; that margin is deliberately left to the channel. What the box needs.

One recommended box carries 12 cameras: Team is half a box, Site exactly one, Business two. Extra cameras are possible up to that limit — beyond it you add a box.

Demo, PoC or partner conversation

Tell us about your site — we reply within one business day.

Controller: TechRevati d.o.o. We use what you enter here only to answer this enquiry (Art. 6(1)(b), steps at your request before a contract). Your IP address is used only for rate limiting and abuse detection (Art. 6(1)(f)) and is not forwarded with the enquiry. Not stored in the product database. Privacy Policy.