mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 21:52:54 +00:00
Wim Van LaerandGitHub
9b064d8b74
# Which Problems Are Solved - Typos - Punctuation - Markdown table formatting - ... (A bunch of issues my editor gave) # How the Problems Are Solved # Additional Changes # Additional Context
33 lines
1.6 KiB
Plaintext
33 lines
1.6 KiB
Plaintext
---
|
|
title: Instances
|
|
sidebar_label: Instances
|
|
---
|
|
|
|
## Instance Structure
|
|
|
|
An instance is the top node in ZITADEL's data hierarchy.
|
|
Within an instance all the default [settings](/concepts/structure/policies),
|
|
such as branding, login policy, password policy, etc. for the system can be configured.
|
|
One instance normally runs on one domain and represents one issuer (e.g. login.customer.com).
|
|
|
|
One instance can contain multiple [organizations](/guides/manage/console/organizations-overview),
|
|
which in turn can represent your own company (e.g. departments), your business customers or a consumer organization.
|
|
|
|
Read more about how to configure your instance in our [instance guide](/guides/manage/console/default-settings).
|
|
|
|
|
|
|
|
This overview shows the general structure of ZITADEL.
|
|
You will find more detailed explanations around the different concepts in the following sections.
|
|
|
|
## Multiple Virtual Instances
|
|
|
|
ZITADEL has the concept of virtual instances.
|
|
When installing ZITADEL from scratch, one instance is always automatically created for you.
|
|
Nevertheless, you can add more virtual instances via the [system API](/reference/api/system).
|
|
This is useful if you have business customers, which in turn have their business customers with self-service and Custom Domain demands.
|
|
By providing a virtual ZITADEL instances, your customers have all the customization options available in ZITADEL.
|
|
Scaling ZITADEL instances virtually enables you to easily distribute your limited compute resources to all your customers.
|
|
|
|
|