01
Connect
Bring existing cameras online
Map feeds and zones on hardware you already run.
Edge-native safety intelligence for warehouses and industrial sites
Deploy focused safety policy packs on the cameras you already run
Start with Core Safety, Worker Protection, or Forklift Safety. Use existing cameras, assign the right profile per camera, and review real incidents and evidence from the edge.
Existing cameras · profile-aware deployment · edge-native runtime · reviewable incidents and evidence
Forklift Safety is the primary launch wedge, but the same shared runtime, incident queue, proof flow, and handoff path already support Core Safety and Worker Protection packs.
Operating loop
From existing cameras to validated incidents
Start with one pack, keep site scope bounded, and turn policy hits into validated incidents. The same edge-native loop carries review, triage, closure, and proof artifacts for the next rollout decision.
02
Review
Evidence-backed review
Validated incidents in the queue—not alert floods.
03
Act
Follow-through to closure
Assign, evidence, close. Extend downstream only if you want to.
Deployment footprint
One edge box. Existing cameras. One pack at a time.
Bounded deployment starts with the cameras you already run, the right runtime profile per camera, and one focused pack in scope. The output is still the same: validated incidents in one evidence-backed incident queue, diagnostics when something drifts, then proof artifacts and handoff before you widen scope.
1
Existing cameras
Your cameras and zones, a bounded deployment boundary—no estate rebuild.
2
Edge Box + go-live
Bring-Up, Preflight, Deployments—checkpoints before the queue goes live.
3
Incident queue
Validated incidents with evidence—operators triage and assign in one queue.
4
Proof & handover
Acceptance, readiness, signoff artifacts, and a defensible record for audit and reuse.
Operational handoff
After closure, hand off into ticketing, security response, or direct notification—plus webhooks, cloud API (polling), or optional bus patterns when your stack needs programmatic intake.
Odoo · Genetec · Email · SMS
Security & Trust
Built for controlled go-live
Edgentik is designed so site one does not depend on guesswork. Edge runtime stays on-site, incidents keep their evidence and context, rollout and recovery stay visible, and downstream handoff is scoped up front so validated work does not dead-end in another silo.
On-site boundary
Edge runtime stays local; review and rollout state stay visible in the app.
Evidence chain
Incidents keep evidence, verification, and context on one record.
Controlled recovery
Rollout, diagnostics, and recovery stay bounded inside the product.
Defined handoff
Downstream handoff into your systems is scoped up front.
APIs & stack fit
Webhooks, cloud API polling, and optional message-bus patterns—connect incidents and artifacts to ERP, ticketing, and security tools on paths you define for site one.
Resilient edge path
Local evaluation and incident creation stay on site; outbound events buffer when uplinks are spotty or interrupted, then catch up within documented budgets—built for yards and warehouses where connectivity is not always perfect.
Proof in the product
Incident queue, closure, and handoff in one place
The product still lands where operators live: validated incidents, acceptance checks, and proof artifacts your team can walk through with the next owner. Packs change the commercial shape, not the discipline of review and handoff.
Evidence-backed review
Queue, triage, assign—not an alert flood.
Acceptance & handover
Readiness, signoff, proof packs—ready for audit and the next bounded rollout.
Policy Packs
Start with one focused safety pack
Edgentik launches through three practical packs that simplify first-site rollout. Choose the pack that matches the risk you want to monitor first, deploy the right camera profile, and review real incidents before expanding.
Core Safety Pack
Cover the fundamentals of site safety and compliance with configurable zones, movement rules, and occupancy awareness.
PPE Compliance
Zone Intrusion
Line Crossing
Dwell Violation
Loitering
Occupancy / Crowding
Best for: sites that want a fast, low-friction first deployment using existing cameras.
Worker Protection Pack
Detect serious worker-risk events such as falls and worker-down conditions for faster response and evidence-backed review.
Worker Down
Worker Fall
Best for: teams focused on direct worker protection, delayed response risk, and higher-severity events.
Forklift Safety Pack
Reduce pedestrian-vehicle exposure with forklift-aware zone, line-crossing, and dwell policies built for warehouse and industrial environments.
Pedestrian in Forklift Zone
Forklift in Pedestrian Zone
Forklift in Restricted Area
Forklift Line Crossing
Forklift Dwell in Prohibited Area
Best for: forklift-heavy indoor operations where pedestrians and vehicles share space.
Each pack is deployed through the right camera profile rather than a one-size-fits-all model stack. That keeps rollout practical while making room to expand later.
Searching for a specific buyer problem? See forklift pedestrian safety monitoring, PPE compliance monitoring, or warehouse safety cameras using existing infrastructure.
Platform progress
What’s now operational in the platform
The credibility shift is that the product is no longer just a conceptual platform story. The shared runtime, policy path, and profile model now cover real launch scope for both people and forklifts.
Shared runtime path now supports both people and forklifts
Tier A forklift policies are wired into zone, line-crossing, and dwell enforcement
Incident actor construction is now generalized across person and forklift entities
Camera profiles are assignable through backend and UI
Profile C maps forklift safety cameras to a forklift-ready runtime path
Final launch signoff is still pending replay and performance validation
Current launch boundary
- Forklift launch scope currently focuses on zone, line-crossing, and dwell-based policies
- Seatbelt, stop or yield, speeding, near miss, blind-spot, cabin-state, and load-state logic are not claimed as launch-ready
- Replay and performance validation still decide final launch signoff
Result: forklift is now a real launch wedge because the enforcement path, actor model, and profile model are already in place.
Camera profiles
Use the right camera profile for the job
Not every camera runs every model. Core Safety, Worker Protection, and Forklift Safety can each use a different runtime profile, so the deployment stays practical instead of pretending every view should do everything.
Profile A
Core Safety Camera
General detection and tracking with the runtime path used for PPE, zone intrusion, line crossing, dwell, loitering, and occupancy-aware policies.
Profile B
Worker Protection Camera
General detection and tracking plus pose-aware worker events for Worker Down and Worker Fall in the same review and proof flow.
Profile C
Forklift Safety Camera
Person plus forklift detection and tracking on the shared enforcement path for the current forklift launch scope. This is now wired through backend and UI.
Reserved
Premium / Advanced Camera
Held back for later high-complexity packs, rather than folded into launch claims before the runtime and validation path are ready.
Founding Pilot
Run a bounded first-site pilot
Start with one pack, up to two cameras, and a two-week review cycle. The goal is simple: capture real incidents, review the evidence, and decide what to roll out next.