Integrator kit
An approved commercial offer with a fixed install spine: centre → edge GPU → camera → zone → rule → first event. List prices are public, partner discounts were signed off on 2026-08-01, and the spine below is the sequence we run ourselves.
Install playbook (order matters)
- Centre: the installer verifies API health and prints the result
- Edge GPU: the box installer verifies that the GPU execution provider is active
- RTSP cameras with a second stream (passwords with operator) → lat/lon → zone → rule → enable
- Acceptance: ≥1 Inbox event with snapshot; Confirm/False in EN/SL/SR
What the partner earns
| Path | Margin | What you carry |
|---|---|---|
| Referral | 10 % of the first 12 months | the introduction and deal registration |
| Resale | 20 %, 25 % certified, 30 % at ≥5 active sites | install, first-line support, the customer relationship |
| Hardware | 100 % yours | sourcing and shipping the box |
We do not sell hardware. That is a decision, not modesty: we publish the reference configuration, the partner sells the box. The hardware margin is deliberately left to the channel — we are not competing with you for the same euro.
Deal registration holds for 90 days. Discounts were approved on 2026-08-01 and hold today; your customer sees the list price. The partner agreement is issued at onboarding.
Milestone XProtect® (Analytics Events)
The bridge lives on the box, not in the cloud: the box posts each VAP event to the XProtect Event Server on the customer's LAN as an Analytics Event — message VAP <event type>, the object box and the zone polygon as image fractions, and the camera reference XProtect uses. Protocol-based — nothing to install in XProtect.
- Management Client: enable Analytics Events, add the box's address to the Event Server allow-list, and create one alarm definition per VAP event type.
- Camera matching: by default the box uses the camera address it already streams from; if your XProtect leads the camera differently (host:port, channel or FQID), enter that reference per camera in the VAP console.
- Failure has a name: a rejected post (address not on the allow-list) raises a named alarm in VAP monitoring instead of silently dropping the event; stale events are not forwarded.
Status: Milestone Technology Partner enrolment is in progress; the integration was tested end to end on XProtect Express+ 2026 R1 (September 2026). Milestone and XProtect are trademarks of Milestone Systems A/S.
Partner FAQ
- Can I quote EUR list prices today? Yes — approved and public since 2026-07-31. Quote them as list price; discounts come from the partner offer, so you never have to improvise a number in front of a customer.
- Do I need to buy a Jetson or a dedicated box first? No. The lab and the PoC run on an existing NVIDIA host over RTSP, and hardware margin stays with you.
- What language is the operator console? EN, SL and SR — all three complete, not machine-translated.
- How do I size a customer's box? From the capacity table, or we measure their actual card during the PoC and put the result in writing.
Onboarding ships the full playbook, the printable acceptance checklist and the partner agreement.