Installing and Upgrading Unique
Overview
This section details the deployment options for Unique, offers guidance on infrastructure prerequisites, provides installation instructions tailored to the selected deployment model, and explains the upgrade process for new releases. Additionally, it includes release notes to keep clients informed about the latest platform developments.
High Level Deployment Overview
The following visualisation shows on a high level all Deployment models of Unique and their . While many abominations exist, the four most commonly used patterns are linked below
Deploying Unique can be achieved through the four key models described earlier. However, all of them essentially involve coordinating across four primary layers:
Landscape: This layer encompasses the foundational elements such as infrastructure, identity management, governance, audit logging, and conditional access. It’s crucial to determine who is responsible for providing and managing these foundational components.
Infrastructure (or Resources): This layer includes the actual infrastructure, such as virtual machines, database servers, and other essential resources. Responsibility lies with the party providing and maintaining these elements.
Workload (Configurations): This layer involves the workloads or configurations required to ensure Unique operates effectively. It’s important to identify who is accountable for setting up and maintaining these configurations.
Unique (the Product): Unique itself is always provided by Unique. The only exception is when clients use the Software Development Kit (SDK) to extend Unique with their own custom logic.
For all these layers, it’s not just about determining who sets them up initially but also about identifying who will maintain them over the long term.
More clear responsibilities must be defined in the more elaborate models and you can find more information in the linked sections.
Layer / Tenant | SaaS/Multi Tenant | Single Tenant | Customer-Managed Tenant | On-Premises |
|---|---|---|---|---|
Product | RAC: Unique I: Clients | [a collection of container images, RAC: Unique I: Clients | ||
Workloads | [ Workload configurations RAC: Unique I: Clients | [ Workload configurations RACI: to be defined | [ Workload configurations RACI: to be defined | |
Infras-tructure | [ Unique provisions all necessary infrastructure to run the workloads ahead. Unique maintains and pays the infrastructure up front.
RAC: Unique I: Clients | [choice of customer, By agreement with the customer either Unique (charged by effort) or the customer provisions and maintains the infrastructure. The infrastructure is directly paid by the customer. RACI: to be defined | [unclear, choice by customer] The customer provisions and maintains the “infrastructure”. Unique can advise or provision the infrastructure (charged separately by effort) but cannot maintain it as it is by definition out of reach. | |
Landscape | Unique operates the Azure AD tenant, implements policies and processes on it, manages users and roles and guarantees its security. RAC: Unique I: Clients | The customer operates the tenant, implements policies and processes on it, manages users and roles and guarantees its security. | The customer provides a runtime or orchestrator. The on-premise landscape is fully operated, governed and controlled by the customer and Unique will only advise (charged by effort) | |
Details | ||||
R: Responsible, A: Accountable, C: Consulted (billed by effort), I: Informed
Author | @Dominik Meyer |
|---|
© 2025 Unique AG. All rights reserved. Privacy Policy – Terms of Service