Getting started
Deployment
Deployment in vedSecure is intentionally staged. Different groups can move at different speeds, and protection levels can be raised gradually without forcing a full fleet into the same posture on day one.
Choose the deployment model
The most common deployment models are self-serve rollout, pilot-first rollout, and department-based rollout. Each one uses the same building blocks but applies them at different scales.
- Self-serve for one person or a very small team
- Pilot groups for testing aggressive protection safely
- Department rollouts for finance, engineering, and executive devices
- Fleet-wide activation after policy and compatibility validation
Stage policy and release behavior
Staging is where vedSecure becomes operationally safe. Instead of only validating whether the agent runs, teams validate whether the protection model behaves correctly for real workloads, internal tools, and roaming endpoints.
Deployment checklist
Before promoting a rollout from pilot to broader release, operators should verify health stability, exclusion quality, update timing, and alert routing behavior.
Deployment checklist
- Pilot devices healthy for 7 days
- Internal tooling verified against behavior engine
- Alert routing tested with a synthetic incident
- Quarantine restore flow validated
- Release channel pinned for the target cohort