Start with onboarding
A choice of deployment model
Discuss shared or dedicated arrangements around the customer’s requirements.
MSSP/MDR · Technology
A dedicated deployment for the customer who needs one.
Or a tenant in your shared one.
Imperum supports shared and dedicated deployments, so a customer that needs its own boundary does not have to be turned away. Agree the arrangement per customer, then review permissions, tool connections and model endpoints against the work your service will deliver.
Shared and dedicated deployment models supportedCustomer boundaries reviewed in the deployment designLocal model options through AI Fabric
Deployment design
Shared deployment
NorthstarCustomer tenant
JuniperCustomer tenant
Tenant ProfilesCustomer-specific endpoints and credentials
Customer context within a shared environment.
Customer requirements
- Customer
- Northstar
- Data boundary
- Architecture review
- Permissions
- Assigned scope
- Deployment
- Shared or dedicated
Agree the arrangement before committing the service.
Shared deployment
JuniperCustomer tenant
OktaCustomer connection profile
Alerts and CasesSupported customer-scoped views
The shared environment remains a deployment option for other customers.
Dedicated deployment
NorthstarSeparate customer environment
Access ControlAuthorized operator permissions
Virtus SettingsModel endpoints for licensed AI
Illustrated as a separate arrangement, subject to the deployment design.
Dedicated deployment
NorthstarSeparate customer environment
Access ControlAuthorized operator permissions
Virtus SettingsModel endpoints for licensed AI
Illustrated as a separate arrangement, subject to the deployment design.
Tenant Profiles
- Customer
- Northstar
- Connector
Microsoft Sentinel- Endpoint
- Customer-specific
- Credentials
- Imperum Vault
Review connection-test results; reachability does not establish authentication.
Dedicated deployment
NorthstarSeparate customer environment
Access ControlAuthorized operator permissions
Virtus SettingsModel endpoints for licensed AI
Illustrated as a separate arrangement, subject to the deployment design.
Providers
Local model endpointInside the dedicated environment
Virtus RoutingReview the full provider chain
Licensed AI workflowsEnable the required modules
Local hosting alone does not describe every integration’s data flow.
Shared and dedicated deployments are supported. Agree each customer’s arrangement in the deployment design.
Northstar and Juniper are illustrated as tenants in a shared deployment.
The alternative places Northstar in a dedicated deployment while Juniper remains in the shared environment.
Review the connection profile and reachable tools inside Northstar’s proposed deployment.
Agree authorized access and model endpoints for the dedicated arrangement before putting the service into use.
Illustrative customer workflow
01 - What it does
Allow for a separate customer deployment.
A customer’s required boundary can shape the deployment arrangement. Shared and dedicated models give the architecture review a starting point, alongside the customer’s permissions and the workflows your team needs to deliver.
Start with the boundary the customer requires.
A shared deployment holds customer tenants in one environment. A dedicated deployment provides a separate arrangement for a customer that needs it. Review the required boundary with the customer, then agree permissions, supported connections and model endpoints for that design. Tenant context scopes supported views and connector credentials; it does not by itself settle the customer’s deployment requirements.
A strict boundary requirement becomes a design choice, not a lost deal.
Northstar: deployment briefExample
- Model
- Dedicated
- Permissions
- Assigned scope
- Model endpoint
- Local
- Tool access
- Customer profile
Illustrative customer and configuration. Not customer performance data.
An explicit boundary discussion
Review permissions and tool access as part of the deployment design.
02 - How it works in the product
Agree the arrangement, then configure access.
Deployment is an architecture decision before it is customer onboarding. Work through the boundary and reachable systems, then use the platform’s access and integration controls for the agreed environment.
- 01Deployment design
Agree shared or dedicated deployment against the customer’s required data boundary.
- 02Access Control
Review the roles and permissions for the people who will operate the service.
- 03Marketplace
Configure supported tools with the appropriate customer profile and review connection-test results.
- 04Virtus Settings
Select reachable model endpoints for the licensed AI workflows.
Deployment arrangements are agreed per customer. Confirm the enabled modules in your license.
03 - How it connects
Connect the tools that the site can reach.
Integrations supplies the customer’s tool access. AI Fabric lets the design use locally hosted models or supported cloud endpoints, with the full model route reviewed against the customer’s data policy.
Works with
In the editions
The Portal, Autonomous SOC and SecOps PlatformIncluded
Agreed in the deployment design; enabled modules follow the license.
04 - What it means for your service
Say yes to the customer with strict data rules.
A separate deployment requirement does not have to end the conversation. Review the arrangement and its connections early, so the proposal matches the environment the customer actually needs.
A model that fits the brief
Choose between shared and dedicated deployment arrangements.
Access reviewed before use
Agree the permissions and connections that make the customer workflow possible.
A concrete customer discussion
Use the deployment design to record the required boundary and reachable systems.
Start with one customer
- 01Write down the boundary
Record why the customer needs a shared or dedicated arrangement.
- 02Map its connections
Identify supported tools and model endpoints the environment can reach.
- 03Review one workflow
Validate its access and deployment requirements with the Imperum team.
Questions about Remote dedicated instances.
1Can a customer have a dedicated deployment?
Yes. Shared and dedicated deployments are supported. Confirm the required data boundary, permissions and deployment arrangement for the customer during architecture review.
2Can a dedicated deployment use local models?
Imperum can connect to locally hosted models. Configure the providers and endpoints for the AI workflows in the license, and review the full provider chain and integration data flows against the deployment design.
Have any other questions? Talk to our team
Shared or dedicated.
Agreed per customer.
Review shared and dedicated options against a customer’s real service requirements.