| Excerpt | ||
|---|---|---|
| ||
If clients opt for self-hosted options, either Customer Managed Tenant or On Premise Tenant, they (potentially with Uniques Advisory at a rate) must equally provide all necessary pieces in order to satisfy the setup and run requirements. You can learn about them in the respective models details linked above. Note that this page gives a high-level overview. For Customer Managed Tenant clients can use the https://unique-ch.atlassian.net/wiki/x/JAEkJQ to further cross-check their tenant for the arrival of Unique. |
| Inc drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Providing a tenant (1)
It does not matter what deployment model is chosen, a client has to provide a landscape that can provide user accounts (IAM, IDP, potentially Just-In-Time or Privileged Access Management).
...
Hosting Unique / Dedicated resources (2)
Clients must provide means to provision a set of resources needed to run Unique successfully. Depending on the use cases, more or less of these services are needed.
...
Workload configurations and supporting services (3)
Brick | Use Case | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Postgres Server1 |
|
| ||||||||||||
MongoDB1 |
|
| ||||||||||||
Redis Cache(s)1 |
|
| ||||||||||||
LLMs1 (mainly Azure OpenAI) |
|
| ||||||||||||
|
| |||||||||||||
S3 compatible storage1 |
|
| ||||||||||||
|
|
1 These services are recommended to be provisioned outside of the orchestrator, see (2).
Unique workloads (4)
The Unique workloads themselves have no requirements except all the services mentioned above, CPU and memory. Some require some disk space to locally ephemerally cache file or similar content.
...