---
title: Service provider reference architecture for dedicated instances
description: Service provider \(SP\) customers can access SP services by using a portal to a dedicated instance. SPs use these dedicated instances to manage their service delivery.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/bp-sp-reference-arch-dedicated.html
release: australia
topic_type: reference
last_updated: "2025-07-31"
reading_time_minutes: 1
breadcrumb: [Service provider reference architecture, Recommended practices for service providers, Domain separation for service providers, Access Management]
---

# Service provider reference architecture for dedicated instances

Service provider \(SP\) customers can access SP services by using a portal to a dedicated instance. SPs use these dedicated instances to manage their service delivery.

## Dedicated instances

Refer to the following image about dedicated instances.

\[Omitted image "bp-sp-reference-architecture-dedicated.png"\] Alt text: SP reference dedicated architecture

## Attributes

-   Dedicated instances require that you have separate administration and dedicated teams. You need multiple licenses for the administrators and developers who log in to multiple instances.
-   Each instance has a finite number of requesters and fulfillers. When you get a new customer, you must procure an instance that is based on the size and scale of your customer's company.

## Shared instance

\[Omitted image "bp-dedicated-vs-shared.png"\] Alt text: Dedicated vs shared



\[Omitted image "bp-dedicated-ds-hybrid-siam.png"\] Alt text: SP reference architecture comparison

**Parent Topic:**[Service provider reference architecture](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/bp-sp-reference-arch-ds.md)