MSP HUB turns SSLNexus Enterprise into a service-delivery platform for managed certificate operations. Your own infrastructure remains a complete estate, while each customer is operated inside a separate client estate with controlled engineer access.
Use MSP HUB for the MSP's own servers, applications, network appliances and certificate workflows. Create customer estates beneath it when SSL Nexus becomes part of the service you deliver.
The MSP HUB remains fully usable for your own infrastructure instead of becoming an empty management shell.
Each client estate keeps its certificate, deployment, policy, vendor and audit activity separate from other customers.
Assigned staff move between customer estates from one signed-in dashboard instead of maintaining a separate SSL Nexus installation for every customer.
Create a separately governed customer workspace from the MSP HUB and label it with the references your service team already uses.
Assign staff per client so engineers see and operate only the estates they are responsible for.
Open a customer from the portfolio or estate selector and return to the MSP HUB without another login.
Manage certificates, targets, vendors, policies, reports and audit activity in the context of that client.
MSP HUB gives service teams a central view of customer certificate volume, upcoming expiry risk, failed automation and target health without combining the underlying customer records.
Use portfolio health to focus engineers on the customers with expiry exposure or failed jobs instead of checking estates one at a time.
Keep customer-specific policy and maintenance windows with the estate they belong to, reducing accidental work outside approved change periods.
Pause customer access during offboarding or contract changes while preserving the estate for later review or reactivation.
Organisation administrators can oversee the managed portfolio, while operational staff can be assigned only to the customer estates they support. Appliance-wide controls stay at the MSP HUB so customer operations cannot change shared platform administration.
Keep client access aligned with service ownership rather than giving every team member global customer visibility.
When an engineer enters a client estate, day-to-day certificate operations remain within that customer's environment.
Licensing, backups and shared platform administration remain separate from ordinary customer work.
Keep the normal Enterprise feature set and add multi-customer service delivery when you need it. Managed client-estate capacity can be sized to the portfolio you operate, and disabling the add-on does not erase customer estate data.