These pages are in English to make them accessible to Service Providers.
On this page, you will find more information about managing your single-tenant services on the SURFconext platform. This is depicted in the IdP-section as well as the SP-section of our documentation because these services are usually managed and configured by identity providers (institutions) and occasionally by service providers. Information on these underlying pages is used in the SURFconext Dashboard. This is work in progress. These pages describe the following single-tenant services:
What is a Single Tenant Service?
Single-tenancy SaaS architecture (confusingly also called multi-instance) is where a separate instance of a software application and supporting infrastructure is used by each customer, or tenant. Single-tenant architecture is mainly used by companies who need a customized approach, either because of their geography (or that of their client-base) or their need of a higher level of security. With single-tenant, each company has a distinct database and system that is either placed on an individual server or segregated using extensive security controls to create a virtual server network.
This could be either by using a separate subdomain per customer on the host of the service provider. Examples are:
Or by hosting the service on the IdP hosting location under the domain of the institution. Examples are: