For Integrators & Deployment Partners
Use this page to understand the commercial-operational shape of the first Edgentik offer for resellers, integrators, and deployment partners.
Edgentik is meant to help a team deploy a first site without turning the engagement into a broad custom integration project.
Who this is for
- resellers evaluating whether Edgentik fits a partner-led delivery motion
- integrators planning a first customer site with bounded scope
- implementation leads deciding what stays standard versus what should be separately scoped
- field-delivery partners trying to avoid a first engagement that expands into custom services too early
First-site baseline
- one site with clear success criteria
- a small number of cameras, with at least one working device and one verified feed as the minimum credible baseline
- one bounded rule set or a small number of policy types
- a controlled path from readiness to go-live to review
- optional downstream workflow only when it is actually needed
The goal is to prove one real operating loop end to end before broader expansion.
What is included by default
- site readiness
- workflow setup
- deployment and go-live
- incident review
- diagnostics and final review materials
In practice, the first deployment is built around existing cameras, site configuration, the core review and diagnostics flow, and the review surfaces needed to inspect the outcome.
What is excluded or separately scoped
- broad multi-site rollout before the first-site loop is stable
- deep custom workflow or integration tailoring as the default experience
- configure-everything-at-once commissioning across many cameras and policy types on day one
- environments where camera or network access is highly constrained without site IT coordination
- a custom workflow for every stakeholder in the first engagement
Ownership model
Edgentik typically provides the bounded first-site structure, the workflow from readiness to deployment review, and the standard review outputs used for the next-step decision.
The partner typically leads site execution: bring-up, rollout sequencing, readiness validation, deployment review, and packaging the outcome for customer review.
The customer typically provides the target site, named owners, camera access, success criteria, and the initial rules to evaluate.
Support and handoff
The public-docs support model is straightforward: check readiness and rollout state first, use diagnostics when something looks wrong, and escalate with enough context for the next reviewer to understand the issue quickly.
A successful first-site handoff means the customer can inspect materials such as the preflight result, deployment or rollout status, CRA or SRA when needed, the site readiness report, the signoff summary, and the installer acceptance pack.
What typically expands after success
- more cameras at the same site
- more rule types at the same site
- more sites using the same operating model
Expansion comes after the loop is credible, not before.