Unique AI Service Models
2 min read
Unique AI supports three operating models. Each model defines where the platform runs, who manages the infrastructure, and what your team is responsible for.
At a Glance
SaaS / Multi-Tenant | SaaS / Single Tenant | Self-Hosted | |
|---|---|---|---|
Infrastructure | Unique-managed, shared | Unique-managed, dedicated | Client-managed |
Data isolation | Logical separation | Dedicated instance | Full control |
Hosting | Unique cloud | Unique cloud | Your cloud (Azure, AWS, or OpenShift On Premise) |
Updates | Automatic | Managed by Unique | Managed by your team |
Configuration | Standard | Configurable | Fully customizable |
Ideal for | Teams that want to get started fast | Organizations that need dedicated resources with managed operations | Organizations that require full control over infrastructure, data, and compliance |
How to Use These Pages
This documentation is organized into three content types:
Journey pages follow the implementation lifecycle in order, from initial evaluation through ongoing operations. Each page covers a specific stage: what actions to take, who is responsible, and what criteria must be met before proceeding to the next stage.
Technical briefs provide in-depth coverage of a single domain — security, cost, or integration — across the full lifecycle. They are referenced from journey pages at relevant points and can be consulted independently at any stage.
Playbooks address specific scenarios such as variant deployments, environment promotion, hardening, and incident response. Journey pages link to the applicable playbook when a scenario arises.
SaaS
The SaaS documentation covers security architecture, integration options, and onboarding for both Multi-Tenant and Single Tenant models.
Start with the model comparison to confirm which SaaS model fits your requirements. From there, follow the onboarding and provisioning process to go live, and refer to the integration and configuration guides to connect the platform to your systems.
Topic | Description |
|---|---|
Security architecture | Data isolation, encryption, identity and access controls, compliance certifications |
Multi-Tenant vs. Single Tenant | Detailed comparison, when to choose which, what triggers a move from MT to ST |
Integration and configuration | Configurable options per model, available APIs, identity federation, boundaries |
Onboarding and provisioning | Path from contract to live environment. Single Tenant vending form. Multi-Tenant provisioning process |
Limits and scaling | Usage limits, storage, rate limits, scaling behaviour per model |
Service transition | Moving from Multi-Tenant to Single Tenant, or from SaaS to Self-Hosted |
→ [SaaS Documentation]
Self-Hosted
The self-hosted documentation guides you from initial platform discovery through ongoing operations.
Start with Evaluate to understand the platform architecture, infrastructure requirements, and operational demands. Foundation then covers the decisions and planning required before any infrastructure work begins.
Once your team is aligned and architecture decisions are made, choose your platform track and follow Prepare, Setup, and Operate in sequence. Each stage defines entry and exit criteria, and a RACI for Unique and client responsibilities.
Stage | Reader goal |
|---|---|
Evaluate | Review the platform architecture, assess infrastructure requirements, and understand operational demands |
Foundation | Understand setup and operational prerequisites, confirm your organizations readiness, and plan your self-hosted implementation. |
Prepare | Set up infrastructure dependencies and configure your cloud environment to a platform-ready state |
Setup | Install, configure, and verify the Unique platform |
Operate | Manage the platform lifecycle, maintain operational health, and evolve your deployment |