- Number of managed sites.
- Typical topology, router constraints, and route or DNS authority at each site.
- Support expectations, response model, and customer approval path.
MSP pilot
Repeat privacy gateway deployments without improvising every site.
The pilot is for consultants and small IT providers who need templates, runbooks, support boundaries, repeatable handoff, and a clear ownership model for route policy, DNS, fallback behavior, privacy posture, and recovery.
- Deployment templates, customer handoff, runbooks, support snapshot format, and review cadence.
- Commercial model for repeated sites and managed appliances.
- Named ownership for route policy, DNS policy, fallback behavior, and rollback approval.
- Customer-owned credentials, domains, and traffic paths stay explicit.
- Redacted diagnostics, retention rules, export process, and offboarding expectations.
- Support access should be scoped, revocable, and tied to a named change window.
- Name whether the MSP, end customer, or upstream provider owns route changes, DNS changes, fallback policy, and final approval per site.
- Document the policy source of truth when existing controllers, routers, or MDM systems already manage the network edge.
- Record how privacy posture claims are verified and who accepts residual risk.
- Confirm console, SSH, or local recovery access before any shared runbook allows live route or DNS changes.
- Require a rollback path, customer handoff notes, and support exit criteria for each deployment pattern.
- Keep fallback and degraded-mode behavior visible so customer sites do not drift into an unreviewed path.
- Define whether diagnostics are customer-generated, MSP-generated, or shared through a redacted bundle workflow.
- Set retention, export, and revocation rules before remote access or recurring operations begin.
- Keep customer support boundaries explicit when moving from advisory work to a live change window.
Pilot evidence
Repeat deployments need repeatable screenshots for handoff and review.
Supports MSP handoff with a redacted summary of route, DNS, device, tunnel, and backup state.
Helps separate MSP, customer, and upstream DNS ownership across repeated sites.
Supports reusable deployment templates without leaking customer topology.