01
Package products consistently
Use stable products, packages and quantities rather than reinventing scope for every customer.
Guardian for MSPs and MSSPs
Add recurring security products without building every platform and operating process yourself.
Guardian gives service providers authorised customer workspaces, product entitlements, integration mapping, operational visibility, recurring reporting and consolidated wholesale billing while the MSP retains its customer relationship and retail pricing.
Provider-scoped customer workspacesGuardian wholesale product catalogueConsolidated MSP billingClear support and escalation boundaries
What changes for the service provider
Sell and operate a broader security service without turning every customer into a separate manual process.
The MSP keeps the customer relationship, sets its own customer retail price and provides the agreed first-line service. Guardian gives the provider a repeatable product catalogue, customer scope, entitlement model, evidence and reporting process.
Damocles provides the Guardian platform, selected products and the contracted escalation or managed-service layer. The amount Guardian invoices the MSP is based on Guardian wholesale pricing and is not changed by the MSP’s customer retail price.
02
Operate customers safely
Use server-derived provider authority and explicit customer relationships to keep data and actions correctly scoped.
03
Protect your margin
Guardian wholesale billing remains separate from the retail price the MSP sets for its customer.
Provider capability
The operational foundation for a repeatable managed security offering.
CW
Customer workspaces
Move between authorised customer contexts with clear provider and customer relationships.
PC
Product catalogue
Select Guardian Core, packages and add-ons using stable product and entitlement definitions.
EN
Entitlements and limits
Control which products are active and which users, endpoints, sites, targets or sources are included.
IM
Integration mapping
Map exact provider and customer sources rather than relying on fuzzy attribution.
OH
Operational health
See collector, agent, source and module state across the supported product estate.
RA
Risk and actions
Convert findings into customer-owned remediation work with due dates and evidence.
RP
Customer reporting
Produce consistent customer-safe reports and review material from approved records.
BI
Consolidated wholesale billing
Receive one Guardian invoice for the MSP relationship, with customer and product allocation available for reconciliation.
SU
Support and escalation
Define MSP first-line responsibilities and the Damocles platform, product or managed-service escalation path.
Partner lifecycle
From partner onboarding to recurring customer service.
01
Onboard the partner
Confirm commercial relationship, roles, support model and authorised provider users.
02
Create the customer
Establish the customer relationship, workspace and server-derived provider authority.
03
Select products
Assign the agreed package, add-ons, quantities, allowances and service tier.
04
Connect sources
Map the approved customer integrations, agents, sites, targets and operational contacts.
05
Operate and report
Review posture, actions, source health, investigations and customer reports.
06
Reconcile and renew
Use stable product quantities and effective dates to support wholesale billing and renewal review.
Commercial model
Guardian invoices the MSP. The MSP controls its customer price.
For an external MSP relationship, Guardian invoices the MSP using the approved Guardian wholesale price book and the contracted product quantities. Guardian does not invoice the MSP’s end customers.
The MSP may record or calculate its customer retail price for margin visibility, but that retail amount must never alter the wholesale amount Guardian invoices to the MSP.
Guardian-managed customers and direct standalone customers use the applicable direct price book and are invoiced directly by Guardian or Damocles according to the contract.
Delivery responsibilities
Make the support split explicit before the first customer is onboarded.
The partner agreement and service schedule define who sells, invoices, provides first-line support, approves changes, communicates with the end customer and escalates product or security incidents.
Product scope, service levels, customer data access, reporting, branding, renewals and exit handling are confirmed before activation. No exclusivity or regional-rights claim is implied by the website.
Build a repeatable security practice
Review the products, margins and support model you want to take to market.
We will map the Guardian products, wholesale relationship, customer onboarding, support responsibilities and billing model required for your MSP or MSSP.