mirror of
https://github.com/zitadel/zitadel.git
synced 2025-04-20 06:51:32 +00:00
599a1ddd78
* Modified quick start guide to reflect the new onboarding changes. * Modified titles to optimize indexing. Left thet titles in title case for now. * Added side bar labels and also made minor changes to titles. * Update docs/docs/apis/openidoauth/endpoints.mdx Co-authored-by: Fabi <fabienne@zitadel.com> --------- Co-authored-by: Fabi <fabienne@zitadel.com>
33 lines
1.6 KiB
Plaintext
33 lines
1.6 KiB
Plaintext
---
|
|
title: ZITADEL 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](/concepts/structure/organizations),
|
|
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/instance-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](/apis/resources/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.
|
|
|
|
|