What stays on-site, and what leaves the site?
Edge runtime: local processing and buffering. Cloud app: review, diagnostics, rollout state—what the floor team and leads actually work from.
Before go-live
What to nail down before Edgentik runs on your live floor
Four decisions: edge-first by default—what stays on-site vs what the cloud app carries; whether incidents and evidence hold up in review; whether rollout and recovery stay visible and bounded; and how handoff to your other systems is scoped.
Decision questions
Four practical questions buyers should resolve before go-live
Use this to decide whether you can cut over without losing the thread on data, evidence, rollout, or handoff to downstream systems.
How do we know incidents and evidence are trustworthy?
Incidents ship with evidence, verification, and context on one operating record—not a clip chased outside the system.
How do we keep rollout and recovery controlled?
Rollout state and diagnostics stay in the product; recovery paths are bounded instead of one-off field hacks.
How does this fit into our existing systems and controls?
Workflow continuation to customer systems is in place today; wider handoff, acknowledgements, and sign-off are scoped per deployment.
What buyers usually need clarified
Operational boundaries buyers often ask about
What stays on-site
Edge runtime: local processing, buffering, site-side policy evaluation.
What leaves the site
What the cloud needs for review, status, evidence, and follow-through—not a silent data pipe.
Access scope
Org, site, role, and action—so operators and admins stay in their lane.
Evidence handling
Incidents stay tied to reviewable evidence and the platform context around them.
Rollout and recovery
Bring-up, diagnostics, and recovery run through visible state and defined workflows in the product.
Workflow continuation
Handoff to your systems stays on defined integration paths—no open-ended workflow sprawl.
Product proof
Proof that the live-site controls are visible in the product
Supporting controls
Supporting controls buyers can inspect in live use
Scoped access / RBAC
Org- and site-scoped roles; actions match the job; invites and account changes leave a trail you can audit.
Gated health / metrics exposure
Health and metrics sit behind the same access rules by default. Broader read access is an explicit turn of the dial—not an accident.
MFA option
MFA with TOTP on cloud sign-in, stronger password handling, lockouts, and hardened sessions—without a bespoke IT project per login.
Audit-backed evidence
Who viewed or exported evidence is logged and searchable. Exports roll up by org/site; downloads follow the rules you set for who may pull what.
Trust Pack handover
One-click Trust Pack for customer review: SBOM, scans, runbooks, and current SLO evidence when you ship it.
Controlled pilot posture
Scoped access, evidence that holds up in review, encryption at rest called out, rollout kept on a short leash—meant for a real pilot, not a slide deck.
Deeper detail
Go deeper only where more operational detail is needed
Extra detail for operators and evaluators. Skip if the sections above already answer it—nothing here is required to use what’s on this page.
Change control
Staged rollout, visible changes, and what keeps live-site updates from turning into ad hoc edits.
Incident operations
Queue-first review, evidence on the record, and follow-through your floor can run.
Proof artifacts
Readiness checks, evidence bundles, and final review outputs leadership can actually read.
Multi-user control plane
Who sees which sites and devices, how roles are split, and where admin ends and operator begins.
Go deeper
Explore rollout, platform operation, and first-site scope
See the First-Site Rollout
From readiness checks through final review—one path, end to end.
See the Platform
Edge runtime, cloud control plane, and handoff to your stack—how the pieces line up.
See Use Cases
Strong first workflows: visible on the floor, reviewable in the app, sized for a first site.