Start with onboarding
A defined edition
Start from the product whose defaults fit your operating model.
MSSP/MDR · Run the business
Match the license to your service.
Edition, modules and capacity.
Know what you are licensed to deliver before you sell it. Choose the edition for the service you run; the license records its enabled modules and capacity limits, and your proposal confirms the commercial package.
Named product editionsEnabled modules in the licenseCapacity limits recorded
SettingsYour MSSP
License
The PortalProduct edition
ModulesEnabled in the issued license
CapacityRecorded in the license
Additional accessVaries by agreement
Additional module access can vary by agreement. Confirm the commercial package in your proposal.
Product
The PortalProvider edition for your own stack
SelectedAutonomous SOCThe AI tier
SecOps PlatformAI plus operational modules
Core workspaceAlerts and Cases
Choose the edition for the service your team will operate.
Modules
Multi-TenantCustomer operations
EnabledCase PrioritizerCase risk signals
EnabledCase RouterAnalyst-aware routing
EnabledCore workspaceAlerts and Cases
Additional module access can vary by agreement.
License
- Product
- The Portal
- Enabled modules
- Multi-Tenant, Case Prioritizer, Case Router
- Capacity
- Tenants and users
- Capacity limits
- Set in the license
- Additional access
- Varies by agreement
- Commercial package
- Confirmed in your proposal
No limits are illustrated. Capacity belongs in the proposal review beside the workflows you plan to run.
License & Support
The PortalEdition for your existing stack
Multi-TenantDefault module
Case PrioritizerDefault module
Case RouterDefault module
Confirm the commercial package in your proposal, including enabled modules and capacity.
Enabled modules and capacity limits are recorded in the license. Confirm the commercial package in your proposal.
The Portal, Autonomous SOC and SecOps Platform are named product editions.
The license records the enabled modules. The Portal defaults shown here cover provider coordination.
Capacity limits are recorded in the license. This illustration shows labels without figures.
Confirm the edition, modules and capacity against your commercial proposal.
Illustrative customer workflow
01 - What it does
Make the package explicit before the rollout.
A named edition gives the service a starting point. The issued license records enabled modules and capacity, so the proposal can be reviewed against what you intend to run.
Agree the scope of the service.
Choose the edition around the work your team operates: Autonomous SOC for the AI investigation layer, SecOps Platform for the wider operational estate or The Portal for coordination on an existing stack. Compare those defaults with a customer workflow before agreeing the package.
The license records the modules and capacity your service can run.
License: your MSSPExample
- Edition
- The Portal
- Enabled modules
- Multi-Tenant, Case Prioritizer, Case Router
- Capacity
- Recorded in the license
- Additional access
- Varies by agreement
Illustrative package, without capacity figures or pricing. Confirm the commercial proposal.
An explicit module list
Review the issued grants against the capabilities your service needs.
02 - How it works in the product
Review the license against a real workflow.
Begin with what you will deliver for a customer. Agree the edition and the required module access, then check the issued license before configuring the service.
- 01The service
List the customer workflows and the tools your team will retain.
- 02The edition
Choose the named edition whose defaults fit those workflows.
- 03The proposal
Confirm enabled modules, capacity and any additional access by agreement.
- 04License & Support
Review the issued license before configuring customer operations.
Additional module access can vary by agreement. Confirm the commercial package in your proposal.
03 - How it connects
Choose the package with the team.
Compare the editions against your operating model. Bring the required capabilities and capacity to the commercial discussion so the proposal reflects the service you plan to deliver.
Works with
In the editions
The PortalEdition
Named edition for providers keeping their own stack.
Autonomous SOCEdition
Named edition for the AI investigation layer.
SecOps PlatformEdition
Named edition extending Autonomous SOC with operational modules.
04 - What it means for your service
Plan the service around a known scope.
Edition defaults and issued module grants give your team a concrete package to review. Capacity belongs in that review alongside the workflows you intend to configure.
A clear commercial discussion
Bring the edition and required capabilities into the proposal.
A package the team can review
Check enabled modules against the planned customer workflow.
Capacity in the same review
Confirm the limits recorded in the issued license before rollout.
Start with one customer
- 01Describe the service
Use one customer workflow to identify required capabilities.
- 02Check the defaults
Compare The Portal with the AI and full platform tiers.
- 03Confirm the proposal
Review the modules and capacity with the Imperum team.
Questions about Licensing that fits provider scale.
1How is Imperum licensed?
Imperum uses a product-and-module license model. Named product editions include Autonomous SOC, SecOps Platform and The Portal; enabled modules and capacity limits are recorded in the license. Additional module access can vary by agreement. Discuss your workflows, deployment and provider requirements to confirm the right scope, capacity and pricing.
2Is there a price per customer?
The product-and-module license records enabled modules and capacity limits. Confirm the commercial package for your service in a proposal with the Imperum team; this page does not publish pricing.
Have any other questions? Talk to our team
Define the service.
Agree the licensed scope.
Bring your operating model and required capabilities to a licensing discussion with Imperum.