Start here: workspace to first value
Create the workspace, select the client data region, add a customer, deploy the first agent, open the device record, create a ticket, configure backup, and verify the first report.
Documentation hub
Get from setup to a verified result without guesswork
Choose the path that matches the work: start a workspace, administer access, operate each module, troubleshoot a failure, or plan a safe migration.
Start, operate, troubleshoot, and recover
Why RadiantOS
What changes for your MSP.
Operate by module and role
Move through EndpointOps, ServiceOps, backup, Vault, NetOps, Microsoft cloud, InfraOps, reporting, automation, and governance with permissions and customer scope visible.
Troubleshoot through a safe next action
Start with the observed state, confirm impact and scope, collect evidence, then follow failure, retry, rollback, cleanup, and verification guidance.
From signal to proof
Documentation hub: a clear operating path.
- Prepare
Confirm prerequisites and authority
Check the required role, permission, entitlement, data region, integration, agent or collector, and approval policy before changing state.
- Operate
Follow the complete procedure
Use the documented happy path and the denied, failed, retry, rollback, and cleanup paths that apply to the workflow.
- Verify
Prove the result
Confirm visible state, backend or provider outcome, audit evidence, customer scope, and the next action before closing the work.
Documentation hub
What your team can do.
Identity, access, and administration
Set up tenants, customers, US or EU data placement, users, roles, MFA, SSO or SCIM, policies, integrations, entitlements, and billing state.
EndpointOps and ServiceOps
Deploy and manage agents, inventory and remediate endpoints, run remote work, handle alerts, tickets, SLAs, projects, time, contracts, and customer communication.
Data protection and recovery
Configure endpoint and SaaS backup, retention and legal hold, then select, approve, execute, verify, and evidence restores or bare-metal recovery.
Network, Microsoft cloud, and InfraOps
Operate collectors, topology, configuration and drift, Microsoft tenant services, cloud workspaces, infrastructure plans, applies, state, and recovery.
Automation, reporting, and governance
Build approval-aware workflows, apply customer-selected AI policy, review run history, reconcile failures, and produce customer or audit-ready reports.
Troubleshooting and support handoff
Use symptoms, request and route IDs, job state, audit evidence, safe diagnostics, retry limits, rollback, and escalation context without exposing secrets.
Built for MSP control
Control stays with your MSP.
RadiantOS keeps scope, access, approval, data placement, and audit evidence visible where the decision happens.
Review the security approachEvery procedure shows its boundary
Role, tenant and customer scope, region, entitlement, approval, side effects, failure handling, and verification stay attached to the procedure.
Examples are safe to reuse
Commands and payloads use explicit placeholders or seeded fixtures. Real keys, tokens, customer data, and internal host details never belong in an example.
Questions, answered
What MSP teams ask about Documentation hub.
Where should a new administrator start?
Use the customer onboarding guide, then follow the first-value path from workspace and data region through the first customer, agent, ticket, backup, and report.
How do I find a module procedure?
Start with the module name and the outcome you need, then choose setup, daily operation, administration, troubleshooting, or recovery guidance.
What belongs in a support handoff?
Include the affected tenant and customer scope, workflow, visible state, request or route ID, time window, impact, checks completed, and safe evidence. Never include credentials.