Customer access
Create expiring device-level access, assign the right location, deliver configurations, and revoke one device without disturbing the whole customer.
Operating model
Give each task a controlled place
Manager roles
Enterprise RBAC creates scoped admin accounts for customer, server, or support work and records who performed sensitive actions.
Branded service
Use your own product identity, domains, outbound email identity, legal links, portal, and standard customer apps.
Several locations
Manage compatible remote nodes from the main panel, track health and capacity, and move customers through a controlled migration path.
Corporate networks
Enterprise site-to-site VPN supports branch and office connectivity alongside the customer-facing service model.
Recovery
Use scheduled backups, remote storage, signed updates, rollback, health checks, and an auditable operational history.
Questions to settle first
A managed service needs an ownership map
| Responsibility | Decide before onboarding |
|---|---|
| Infrastructure | Who owns each VPS, domain, DNS zone, firewall, and backup destination |
| Customer support | Who answers the end user, which hours apply, and which problems escalate |
| Payments | Whose legal entity and provider account receives customer funds |
| Privacy | Which logs and DNS services exist, how long records remain, and what customer terms disclose |
| Admin access | Which manager can change customers, servers, billing, support, or global settings |
| Exit and recovery | How credentials, data, keys, and an off-host backup are returned or restored |