Public Overview Docs

Current Capabilities & Boundaries

Use this page to understand what exists today, where the current product is strongest, and what a bounded first site should prove before expansion.

Back to Public Docs Request a Pilot Scoping Call

This page is the public “what exists today” anchor for Edgentik.

If you are evaluating a first deployment, use it to avoid assumption drift and keep the scope grounded in what the current product is meant to do well.

What Edgentik is strongest at today

bringing a first site live with controlled rollout
running incident review with evidence and follow-through
supporting diagnostics and bounded recovery when something drifts
producing final review materials for the next-step decision

What a successful first site looks like

org/site scope is correct and obvious in the UI
at least one reachable device is in scope
at least one camera feed is verified
at least one zone is saved
at least one policy is deployed and converged
reviewed incidents are clear, or the quiet state is confidently understood
diagnostics context can be copied for escalation

Recommended boundary for a first site

For the First Site Pilot, keep scope intentionally bounded:

start with a small number of cameras
start with a small number of policy types
prove the full operating loop end-to-end before expanding

The goal of a first site is not breadth. The goal is credibility: a repeatable operating loop teams can inspect and trust.

What this page does not claim

This page is intentionally conservative. It does not claim that Edgentik is already optimized for:

broad multi-site rollouts before the first-site loop is stable
deep custom workflow tailoring as the default launch experience
configure-everything-at-once commissioning across many cameras and policies on day one
environments with highly constrained camera or network access without Site IT coordination

What may still require guided support