Delegated access management

Hosted Login

Multifactor Authentication

Passwordless Authentication

Audit Trail

Identity Brokering

Platform

Service Accounts

Features

Easy integration

B2B (Business to Business)

Self Service

Existing identities

Secure authentication

Use Cases

Learn how to install, setup, and use ZITADEL.

Documentation

ZITADEL Cloud

Self-hosting

Trust center

Examples and Guides

Github Repository

Develop

Get Started

Contribute

Roadmap

Changelog

About Us

Jobs

Contact

Company

Read the blog

Sign up

Login

Pricing

Blog


## Where should I start if I want to try out or run ZITADEL?

The first step to integrate a new application into an existing infrastructure is always to determine what the requirements are and the process you need to follow until it is ready to start with the first tests. See what we prepared to make it easy for you to start with ZITADEL and how few requirements you have to try out ZITADEL in the near future yourself.

## What is ZITADEL

ZITADEL is a "Cloud Native Identity and Access Management" solution built for the cloud era. ZITADEL uses a modern software stack consisting of Golang, Angular and CockroachDB as storage and follows an event sourced pattern. The Project is Open Source and we offer a SaaS solution or managed instances. Our approach is somewhat different to other open source alternatives, as we want to ship the APIs, GUIs, Database, and, if necessary the infrastructure automation, together for secure and easy day 2 operations.

To get more information about ZITADEL you can head over to our Website [zitadel.com](https://zitadel.com) or to the published blog "[Our Vision for ZITADEL](https://zitadel.com/blog/our-vision-for-zitadel/)" and if you want to try out ZITADEL without the hassle to prepare infrastructure or to just integrate an IAM into you application then I would recommend to use our cloud service at [zitadel.com](https://zitadel.com).

## What is ORBOS

In this post I will sometimes mention [ORBOS](https://github.com/caos/orbos), which is our solution to provide you with our option of optimal automation to streamline your ZITADEL, or any other application for that matter. It consists of different types of operators, where every single one covers a different component from infrastructure to Kubernetes, ops-tooling, networking, database and also ZITADEL.

## Where do I start?

As I already mentioned, if it’s just to test ZITADEL I would recommend registering your organisation on [zitadel.com](https://zitadel.com), otherwise there are still a lot of possible options. Our focus will be to run ZITADEL on a Kubernetes cluster, so as long as you have a Kubernetes cluster available in any way, you can use ZITADEL. Other constellations are possible as well, but we will currently only focus on running ZITADEL on Kubernetes as it brings so many advantages with the provided orchestration.

<img
  src="/blog/2021-05-27-where-to-start-running-zitadel-1-01.png"
  width="100%"
  alt="options to run ZITADEL"
/>

There are different points where you can start off to get a working Kubernetes cluster, if you not already have one available already:

- Managed K8s-cluster with GKE, Amazon EKS, AKS
- No available K8s-cluster, but an account on a Hyperscaler for VM provisioning (for example Google Cloud)
- No available K8s-cluster, but an account for a VM-provider(for example Cloudscale)
- No available K8s-cluster, but available VMs or servers internally

If you currently have no available cluster and don’t/can’t use any managed instances, you can use [kubeadm](https://kubernetes.io/docs/reference/setup-tools/kubeadm/) or our product [ORBOS](https://github.com/caos/orbos) to quickly have one up and running on any VMs or hardware-nodes you have available.

We focus fully on the operator pattern to manage our infrastructure and our applications on the resulting Kubernetes cluster, which gives us full control over the applied resources and the possibility to reconcile the current state with the desired state. For example, if you want to upgrade an application, you only upgrade the operator and the newly deployed operator will take it from there.  
To make it as easy as possible upgrading to a newer version, the operators are self-reconciling, which is only possible through the orchestration-functionality of Kubernetes and provides the option to change the desired version of the operator in the respective desired state and the operator will deploy itself with the newer version.

## How do I start with ZITADEL

The fastest way to start ZITADEL in your cluster is currently to use our provided [ZITADELCTL](https://github.com/zitadel/zitadel/releases/latest) and all the necessary steps are explained in our [quickstarts](https://docs-v1.zitadel.com//docs/guides/installation/crd). As result you will have two running operators in your cluster, that start ZITADEL and CockroachDB in your desired configuration. These operators can be run in two modes, the [GitOps-mode](https://docs-v1.zitadel.com/docs/guides/installation/gitops), which reads the desired configuration out of a git repository, and the CRD-mode which reads the desired configuration out of an CRD inside the cluster.

Our recommendation is to run the operators in [GitOps-mode](https://docs-v1.zitadel.com//docs/guides/installation/gitops), to always have the desired state reconciled into the cluster, but it’s also possible to start the operators in [CRD-mode](https://docs-v1.zitadel.com//docs/guides/installation/crd) and provide the configuration you want to see in ZITADEL as CRD, which you can also reconcile with a GitOps-tool like [ArgoCD](https://github.com/argoproj/argo-cd) or [Flux](https://github.com/fluxcd/flux) if you still want to work with the GitOps-pattern.

## Requirements to run ZITADEL

First off, there are minimal requirements to run ZITADEL which also depend on how you intend to use it and on what functionality you need. That being said, for this we go for a full configuration to provide an example to run ZITADEL with all functions it provides.

The requirements can be split into three groups:

- “used by ZITADEL”
- “needed to run ZITADEL”
- “optional to better operate ZITADEL”

<img
  src="/blog/2021-05-27-where-to-start-running-zitadel-1-02.png"
  width="100%"
  alt="requirements to run ZITADEL"
/>

Let’s start with the **requirements which are used**, to this group belongs the SMTP configuration to be able to send emails, access to a Twilio account to send SMS’s and a database to store the data which has to be [CockroachDB](https://github.com/cockroachdb/cockroach) currently.

For the group **“needed to run ZITADEL”** there is only the need for a domain, where different subdomains can be registered to point at ZITADEL, optional through an Ingress/ API-Gateway/ LoadBalancer which manages the connections from outside the cluster to inside.

In **“optional to operate ZITADEL”** are some components that are less important for a first test, but will get more important later. Most functionalities are covered through our second product ORBOS with a component called BOOM which reconciles a defined toolset. If you need to manage the infrastructure yourself and/or can’t use BOOM then take this as our recommended components to add to your ops-stack.  
As with most of the current applications you have exposed metrics from ZITADEL in format of the [Prometheus data model](https://prometheus.io/docs/concepts/data_model/) which can be handled by most current time-based databases. Some examples for this are (obviously) Prometheus, [OpenTSDB](http://opentsdb.net/), [InfluxDB](https://www.influxdata.com/) and a lot of others. Besides the metrics there are also logs which can be persistent to have the ability to analyse them if an error occurs.

---

Stay tuned for the second part where I will provide more details about our current setup to run [zitadel.com](https://zitadel.com).

---

Stefan is a software engineer specialized, amongst many other domains, in DevOps and is deeply committed to Cloud Computing. When he's not listening to music while typing away, you may spot him cruising the mountain roads by motorcycle or car.

<div className="flex items-center">
  <img
    src="/blog/2021-05-27-where-to-start-running-zitadel-1-00.jpeg"
    width="60px"
    height="60px"
    alt="Stefan Benz"
  />
  <span className="mx-2 flex items-end">
    <span>Follow Stefan on&nbsp;</span>
    <a href="https://twitter.com/stebenz1" target="_blank" rel="noreferrer">
      Twitter
    </a>
    <span>&nbsp;or&nbsp;</span>
    <a
      className="m-0"
      href="https://github.com/stebenz"
      target="_blank"
      rel="noreferrer"
    >
      Github
    </a>
    <span>.</span>
  </span>
</div>


Part (1/2) The first step to integrate a new application into an existing infrastructure is always to determine what the requirements are and the process you need to follow until it is ready to start with the first tests. See what we prepared to make it easy for you to start with ZITADEL and how few  requirements you have to try out ZITADEL in the near future yourself.

Where should I start if I want to try out or run ZITADEL?

A company's way to build and deploy modern software comes with many different advantages and disadvantages, joy and sweat in real life. See which challenges we had or still have and which strategy we follow to deal with it.

Always run a changing system - The CAOS approach


## What is ZITADEL

ZITADEL is a "Cloud Native Identity and Access Management" solution built for the cloud era. ZITADEL uses a modern software stack consisting of Golang, Angular and CockroachDB as sole storage and follows an event sourced pattern.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-01.png"
  width="100%"
  alt="ZITADEL Architecture"
/>

We built ZITADEL not only with the vision of becoming a great open source project but also as a superb platform to support developers building their applications, without need to handle secure user login and account management themselves. By platform we mean a system where multiple parties can integrate custom use-cases for digital identities on top of solid core features. To enable easy integration into your business case, nearly all functions can be accessed via an API. With this we achieve a proper separation of concern and don’t need to integrate custom code within our codebase.

## What features does the platform provide?

### Single-Sign-On / Single-Sign-Out

Use the convenience of a single sign-on (SSO) solution to login with every possible service. ZITADEL enables SSO via standard protocols such as OpenID Connect. Services that cannot be directly integrated can be integrated with identity aware proxy or web application firewalls (WAF). Session management is therefore handled identity-based within identity access management (IAM) and no longer solely in the application. In addition, third-party cloud applications can be easily connected in this way.

### Passwordless / Multi-factor authentication

Although you can use password policies and a range of 2FA and MFA options with ZITADEL to reduce security risks during login, even complex passwords can be compromised, for example through phishing, while user experience suffers greatly from cumbersome passwords and looking up secrets. ZITADEL allows your users to configure passwordless Login based on WebAuthN & CTAP (FIDO2). Passwordless works on all browsers and platforms, requires only one gesture such as FaceID, Fingerprint or PIN, and is phishing resistant through public-key cryptography.

### Identity Brokering

Identity Brokering enables you and your customers to reuse existing identity providers. For example, if you rely on Microsoft's AzureAD for identity management, then you can use ZITADEL’s Identity Brokering feature to link your existing account from AzureAD to your ZITADEL account. The benefits of this feature is that a user can link multiple external identities to it’s ZITADEL identity. Moreover, Identity brokering enables you to grant roles to the brokered users and disable their accounts if the need arises.

### Role Based Access Control

To manage the users' access to projects connected to ZITADEL it supports the use of Role Based Access Control (RBAC). RBAC allows you to design a sophisticated role catalog for each of your projects and granting granular access to users. To integrate these roles into your application you can simply integrate them by utilizing well established protocols like OAuth 2.0 and OpenID Connect. ZITADEL also lets you configure whether you want to assert the roles into access tokens or simply rely on the userfinot and introspect endpoints.

### Delegation

ZITADEL allows you to “delegate” roles of your projects to other organizations. With this feature you can enable other organizations to self-manage their users and the effective role they possess of your project. For example if you create an eCommerce service and you want to delegate the management of a specific tenant to your customer you could easily create a role “tenant owner” which you could grant to the customers organization.

### Strong Audit Trail

Traceability is an important basis for an IAM, which is why ZITADEL offers you an audit trail of all operations of an account and its actions. The audit trail is firmly anchored in the ZITADEL because the internal data model does not save it separately but derives it from an event stream. You have the ability to export the audit trail for advanced analytics or storage to other systems.

### API’s

To make for a great IAM platform ZITADEL provides close to all of its functionalities as APIs. Most important for integrators is the Management API: It provides all features to manage Organisations, Users, Projects for a certain Organisation. Furthermore OpenID Connect 1.0 and OAuth 2.0 are available to integrate your projects Authentication and Authorization requirements. Two more API’s that are available are the IAM and Auth API. The IAM API can be used to configure the whole IAM, this is mostly used in self-deployed (ZITADEL Enterprise) or managed deployments (ZITADEL Enterprise Cloud). Authentication and user information can be accessed through the Authentication API.

## How ZITADEL compares to other solutions

Let’s compare ZITADEL to other well established solutions with a strong focus towards Developers or Open Source.

### Auth0

Auth0 is a great IAM platform to integrate with your projects. Their developer support is exceptional and the API is well thought through. However we find that some things are not ideal, such as pricing, Closed Source, Audit Trail and improper on-premise support.

Where Auth0 is more mature

- More Protocols Supported (e.g SAML 2.0)
- Customization Support (Rules, UI, and so on)
- More stable API’s
- A lot of documentations and howtos

Where ZITADEL excels

- Runs on any cloud provider and on-premise (Cloud-Native)
- Built for multi-tenancy and [self-service delegation](https://zitadel.com/docs/guides/manage/console/organizations/)
- Better Audit Capabilities
- Tiered pricing depending on SLA and non-security requirements

### Keycloak

Keycloak is a mature IAM System with a lot of great features. It is also Open Source with an Apache 2.0 license (like ZITADEL) and has a well established reputation.

Where Keycloak is more mature

- More Protocols Supported (e.g SAML 2.0)
- Better customization (Private Labelling)
- Big Community

Where ZITADEL excels

- Built for Cloud-Native
- Better Audit Capabilities
- Multi- Cloud / Datacenter Support
- Less Resource Requirements

## Platform ecosystem

We think ZITADEL is a great platform for third parties (and ourselves) to integrate business requirements on a robust platform and enable people to build business value instead of focusing on secure Authentication and Authorization implementations.

In this chapter we will provide some use-case where ZITADEL can help you excel.

### Network Integration, Identity Aware Proxy (Zero Trust)

If you use ZITADEL, you can easily integrate your network equipment (Reverse Proxy / WAF) with ZITADEL for things like secure authentication. For example you might want to enforce multi-factor authentication when a user is not at a trusted site. Your identity aware proxy could easily (re)authenticate the user when someone leaves a trusted site by prompting for a more secure authentication method. ZITADEL will then proceed with ensuring the more secure method.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-02.png"
  width="100%"
  alt="Zero Trust"
/>

### Custom User Registration

If you have special requirements for your user registration (KYC, eHealth, eGovernment), you can easily rely on ZITADEL to build your own registration process by integrating your project with the ZITADEL management API. By building your integration you can reuse existing features to manage identities from our platform and combine them with your unique registration requirements.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-03.png"
  width="100%"
  alt="Custom User Registration"
/>

### Business Process integration (SaaS, MSP)

When building a service for your customers you may want to integrate your access management process into your order management. For example, if you have a SaaS solution where a customer can set up a new tenant by himself, you can delegate the ability to manage their own users directly to the customers. This may greatly reduce support requests from customers to setup users and access rights. With ZITADELs unique self-service capabilities it's even possible to let your customers register their existing identity solutions on their own.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-04.png"
  width="100%"
  alt="Business Process integration"
/>

### Custom Lifecycle Requirements (HR Systems)

If your business already has some systems in place that are responsible for managing your Human Resources or Business Processes, you can easily integrate them with ZITADEL. For example, if you have an HR System which already manages the employee lifecycle, you can use ZITADEL to handle the users identity, but leave the business process in the proper domain - within your HR System. With this approach you can reuse your employee process (joiner, mover, leaver) without leaking business processes into the IAM platform. We think that an IAM platform should not be the component in your architecture which executes business processes. Because if you implement business processes from domains like HR, CRM into the IAM Domain, you will eventually create a IAM which can not be easily replaced even if you use standard interfaces.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-05.png"
  width="100%"
  alt="Custom Lifecycle Requirements (HR Systems)"
/>

### Custom Access Management Requirements (ITSM)

Quite a lot of companies already rely on IT service management (ITSM) systems like ServiceNow to handle their fulfillment processing (access request, account reset, etc.). In such cases it makes sense to leave the IT service workflows in the tool that is optimized for business processes and integrate ZITADEL as an access Management system. Such an integration allows you to fully integrate your IT services process. For example the account of a user could be locked from the ZITADEL management interface and the unlock process could be built as a workflowinto your ITSM. This helps you build and maintain lean processes with low implementation and change cost.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-06.png"
  width="100%"
  alt="Custom Access Management Requirements (ITSM)"
/>

### Custom Sync of data (Sync any data source)

ZITADEL’s APIs enable you to manipulate and synchronize data from any system. For example, you can sync your applications users list with ZITADEL and even change user data from within your application. All of this without relying on ZITADEL’s management interface (console). If you care about a deep integration of the user experience this is a great way to enable your project. Furthermore some applications require an up-to-date list of all users for their processes. These applications can easily query ZITADEL for said data.

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-07.png"
  width="100%"
  alt="Custom Sync of data"
/>

## How people use ZITADEL

Most of the time, our customers choose to use our platform's core features like Authentication and Authorization by utilizing protocols like OpenID Connect and OAuth 2.0. But in some cases they integrate even deeper with our API to improve their time to market, operational efficiency and security. Read about what people have already built in this chapter.

### Integration Case - Task Management

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-08.png"
  width="60%"
  alt="Hygeia"
/>

One of our customers built a SaaS Service for tracing pandemics. Right now this solution is used to trace the SARS-CoV-2 spread in some parts of Switzerland.
The special integration in this case is that the workers who use the solution need to be able to assign work to entitled people. To accomplish this, the software utilizes a service account to query ZITADELs management API in a scheduled manner and syncs this list into their database. With this they are able to provide an up-to-date list of all entitled users. Further ZITADEL enables their development by providing an IAM as a Service model, where CAOS takes care of all operation security questions.

Kudos to [JOSHMARTIN](https://joshmartin.ch/) for helping us through the pandemic by providing the government with a progressiv application that really enables the tracing effort.

**Used Features**

- Authentication (incl. MFA, Passwordless)
- Authorization
- OpenID Connect / OAuth 2.0
- Management API, Query Granted Users
- Service Accounts

**Tech Stack**

- Elixir
- Phoenix Live View

**Resources** <br></br>
[joshmartin.ch/en/projects/kanton-st-gallen-contact-tracing/](https://joshmartin.ch/en/projects/kanton-st-gallen-contact-tracing/)

### Integration Case - eCommerce Framework

<img
  src="/blog/2021-05-04-our-vision-for-zitadel-09.png"
  width="60%"
  alt="Velox"
/>

The great people of [sly](https://sly.ch) are building a modern microservice oriented headless eCommerce Framework called [VELOX](https://velox.swiss) and choose ZITADEL as the solution for handling all of their authentication and authorization needs.

Kudos to sly for creating such a great and adaptive eCommerce solution!

**Used Features**

- Authentication incl. multi factor
- Authorization
- Single Sign On
- OpenID Connect / OAuth 2.0
- Management API
- Service Accounts

**Tech Stack**

- Java

**Resources** <br></br>
[velox.swiss](https://velox.swiss)

### Integration Case - multiple ASP.net Core Projects

The Zurich located development agency called [smartive](https://smartive.ch/) utilizes ZITADEL for their projects. As they often rely on ASP.net Core to build award winning projects they wanted to improve their time to market. To integrate ZITADEL with the existing Microsoft authorization ecosystem, they implemented the .net library and open sourced it. Go checkout the library on [Github](https://github.com/zitadel/zitadel-net).

Kudos to Christoph Bühler for implementing this!

**Used Features**

- Authentication (incl. MFA, Passwordless)
- Authorization
- Single Sign On
- OpenID Connect / OAuth 2.0 (incl. JWT Profile and introspect support)
- Management API
- Service Accounts

Tech Stack
ASP.NET Core

Resources
https://github.com/zitadel/zitadel-net

## Future Enhancements (subject to change)

We will improve ZITADEL over time with new features. To give you a small hint of what we are planning to release, have a look at the following list.

- API Docs with Swagger / OpenAPI - [Since creating this blog we released this feature](https://zitadel.com/docs/apis/introduction#swagger-documentation)
- Outbound Webhooks
- SCIM 2.0 API
- Expose Authentication Functions as API
- Conditional Access Rules API

If you have ideas of question feel free to engage with us on [Github Discussion Board](https://github.com/zitadel/zitadel/discussions)

## TL; DR Why you should consider ZITADEL your goto IAM Platform

ZITADEL is a proper **Open Source** project, offers competitive and fair **pricing**, is built by an experienced **team** and a **committed company** and has a **high velocity for developing new features** and constantly improving security.

**In short ZITADEL is the identity & access platform for your business!**

Feel free to contact us on these channels

- [hi@zitadel.com](mailto:hi@zitadel.com)
- [twitter.com/zitadel](https://twitter.com/zitadel)
- [github.com/zitadel/zitadel/discussions](https://github.com/zitadel/zitadel/discussions)

If you consider contributing we would also be happy to welcome you!


We built ZITADEL not only with the vision of  becoming a great open source project but also  as a superb platform to support developers building their applications, without need to handle secure user login and account management themselves.

Our Vision for ZITADEL


<div className="my-4">
  <YouTube videoId={"6FGDaqF3scg"} containerClassName={"youtube-container"} />
</div>

## Topics covered

- What makes ZITADEL better than other IAM services?
- Why did you choose Cockroach DB?
- What is CQRS and how do you use it in ZITADEL?
- Why use a spooler in an event-sourcing workload?
- How does ZITADEL avoid bad data?
- What are challenges of Kubernetes?
- What is ORBOS?
- How to use GitOps? What are the benefits?
- How to solve DNS problems from running Kubernetes in multiple regions?
- How to use CloudFlare's magic WAN?
- How to handle hybrid-cloud challenges?
- Why use geo-partitioning?
- Secondary indexes in Cockroach DB

## CockroachDB & ZITADEL

We use [CockroachDB](https://www.cockroachlabs.com/) as our storage. Check out their great product!

Read our joint Case-Study: [ZITADEL is building an IAM-as-a-service platform with CockroachDB & CQRS](https://resources.cockroachlabs.com/case-study/zitadel).

## Further resources

- [ZITADEL Architecture](https://zitadel.com/docs/concepts/architecture/software)
- [ORBOS - GitOps everything](https://github.com/caos/orbos)
- [Cloudflare Magic WAN](https://www.cloudflare.com/magic-wan/)
- [DNS Chaining | Cockroach Labs](https://www.cockroachlabs.com/blog/experience-report-running-across-multiple-kubernetes-clusters/)


Our live stream with Cockroach Labs on how we built ZITADEL.

How we built it with Cockroach Labs


## ZITADEL v1.0.0

As [announced on April 9](https://status.zitadel.ch/incidents/44183) we released the version [1.0.0](https://github.com/zitadel/zitadel/releases) on April 20.

**API Breaking Changes**. We have decided to fundamentally restructure our APIs. All command requests will only return the relevant data instead of the whole object. For example, for a newly created object, this is the ID. Only via read functions the complete data can be accessed.

Subscribe to our [status updates](https://status.zitadel.ch/) to stay informed.

## Updates to ZITADEL Cloud

We started with an soft-launch last year to get early feedback on functions and root out some of the operational challenges running the distributed [multi-cloud service](https://zitadel.com/trust). We now host over 80 organizations on ZITADEL Cloud.

Sincerely, thank you to all our early adopters providing us with feedback, support and trusting us to provide a critical component to your applications!

So what changes with this release for our SaaS offering ZITADEL Cloud:

1. **We enforce our feature set per subscription plan**. For more information check out the detailed list on our [pricing page](https://zitadel.com/pricing). Early adopters will keep their plans for free for a bit longer to get to know the different plans better.
2. **You can buy a subscription plan via ZITADEL Console**. We have integrated Stripe as payment provider for now. If you have any concerns or don't want to pay via Stripe, please get in [touch with us](mailto:hi@zitadel.ch).

Head over to [ZITADEL Docs](https://zitadel.com/docs/) to learn more about how to use ZITADEL. If you have any questions or something is not working as expected, then please [contact us](https://zitadel.com/contact/).

## What's next

We realize that there is still an important feature outstanding. We will work the next weeks on **improving private labeling** in ZITADEL. If you have any other feature requests, then please join the [discussion over at GitHub](https://github.com/zitadel/zitadel/discussions). Also [contributions](https://github.com/zitadel/zitadel/issues) to the open source version of ZITADEL are always welcome.

Moreover we will continuously update the documentation with manuals, guides, and quickstarts. Lastly, we will provide more details on the support and SLA terms & conditions of the service.


We released version 1.0.0 of ZITADEL on Apr 20, enabled our subscription plans and activated online billing via ZITADEL Cloud console. A brief overview.

ZITADEL Cloud ends introductory phase.


<div className="my-4">
  <YouTube
    videoId={"coupAc7TmWM?start=3310"}
    containerClassName={"youtube-container"}
  />
</div>

## Topics covered

- About CAOS
- What makes ZITADEL special? Our Challenges & Goals
- How we run ZITADEL in GitOps mode with ORBOS
- What is ORBOS?
- Which resources do we manage with GitOps?
- What did we learn?
- What's the plan for the future?

[Have a look at the slides](https://docs.google.com/presentation/d/1Byg6C5xd3MeEDUWNY2r_fcIj9zBbI2qTCgBjenTTYxM/edit)

## Cloud Native Bern

A great community for companies in Bern (and far beyond), working on Cloud Computing

https://www.meetup.com/cloudnativebern

https://cloudnativeday.ch/

## Further resources

- [More about GitOps @ CAOS](/blog/dev-gitops-at-caos)
- [ORBOS - GitOps everything](https://github.com/caos/orbos)
- [ZITADEL - Cloud-Native IAM](https://github.com/zitadel/zitadel)
- [ZITADEL Architecture](https://zitadel.com/docs/concepts/architecture/software)


Our talk at the Cloud Native Bern Meetup about how to run our cloud-native IAM with GitOps

Blog.