Instance Structure

An instance is the top node in CNAP’s data hierarchy. Within an instance, all the default settings, such as branding, login policy, etc. for the system can be configured. One instance normally runs on one domain and represents one Cloud Native Application Platform installation.

One instance can contain multiple 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 settings guide.

This overview shows the general structure of CNAP. You will find more detailed explanations around the different concepts in the following sections.

Multiple Virtual Instances

CNAP has the concept of virtual instances. When installing CNAP from scratch, one instance is always automatically created for you. Nevertheless, you can add more virtual instances via the system API. This is useful if you have business customers, which in turn have their business customers with self-service and custom domain demands. By providing virtual CNAP instances, your customers have all the customization options available in CNAP. Scaling CNAP instances virtually enables you to easily distribute your limited compute resources to all your customers.

Key Points about Virtual Instances

  • Customization: Each virtual instance can have its own settings, branding, and policies, making it adaptable for various organizations or business customers.
  • Scalability: The concept allows for easy scaling of resources, enabling the distribution of compute resources across multiple customers without needing separate physical instances.
  • Hierarchical Structure: In CNAP, an instance serves as the top node in the data hierarchy, which can contain multiple organizations, further emphasizing the flexibility in managing different clients or departments within a single instance.

This terminology emphasizes the ability to create distinct yet interconnected environments that cater to diverse client needs, rather than simply isolating them as tenants within a shared infrastructure.