ZITADEL - Identity infrastructure, simplified for you.
Go to file
Livio Amstutz 8830896199
feat: setup as separate command (#604)
* feat: separate setup from startup

* health

* move setup config

* add env vars to caos_local.sh

* fix domain and set devMode explicit
2020-08-18 10:04:56 +02:00
.codecov chore(codecov): make codecov configurable in repo (#40) 2020-04-08 07:37:24 +02:00
.github feat(documentation): svelte app as document generator (#566) 2020-08-11 09:53:09 +02:00
build feat: port reduction (#323) 2020-07-08 13:56:37 +02:00
cmd/zitadel feat: setup as separate command (#604) 2020-08-18 10:04:56 +02:00
console fix: claim verified domain from usernames (#603) 2020-08-18 08:57:16 +02:00
docs fix: app by id, views with computed objects (#583) 2020-08-13 08:28:18 +02:00
internal feat: setup as separate command (#604) 2020-08-18 10:04:56 +02:00
k8s/base added flow for loggin (#429) 2020-07-09 16:34:56 +02:00
migrations/cockroach fix: claim verified domain from usernames (#603) 2020-08-18 08:57:16 +02:00
pkg/grpc fix: claim verified domain from usernames (#603) 2020-08-18 08:57:16 +02:00
site feat(documentation): svelte app as document generator (#566) 2020-08-11 09:53:09 +02:00
.gitignore fix(spooler): correct workers (#508) 2020-07-28 09:42:21 +02:00
.releaserc.js chore: matrix build (#106) 2020-05-14 07:38:58 +02:00
go.mod chore(deps): bump github.com/cockroachdb/cockroach-go/v2 (#545) 2020-08-17 09:57:55 +02:00
go.sum chore(deps): bump github.com/cockroachdb/cockroach-go/v2 (#545) 2020-08-17 09:57:55 +02:00
LICENSE Initial commit 2020-03-16 14:51:32 +01:00
README.md docs: Update README.md (#530) 2020-07-28 10:49:17 +02:00
SECURITY.md docs(readme): security policy (#19) 2020-03-20 06:30:10 +01:00

ZITADEL

ZITADEL

semantic-release Release license release Go Report Card codecov

This project is in a alpha state. The application will continue breaking until version 1.0.0 is released

What Is It

ZITADEL is a Cloud Native Identity and Access Management solution. All server side components are written in Go and the management interface, called Console, is written in Angular.

We optimized ZITADEL for the usage as service provider IAM. By service provider we think of companies who build services for e.g SaaS cases. Often these companies would like to use an IAM where they can register their application and grant other people or companies the right to self manage a set of roles within that application.

How Does It Work

We built ZITADEL around the idea that the IAM should be easy to deploy and scale. That's why we tried to reduce external systems as much as possible. For example, ZITADEL is eventsourced but it does not rely on a pub/sub system to function. Instead we built all the functionality right into one binary. ZITADEL only needs Kubernetes for orchestration and CockroachDB as storage.

Why Another IAM

In the past we already built a closed sourced IAM and tested multiple others. With most of them we had some issues, either technology, feature, pricing or transparency related in nature. For example we find the idea that security related features like MFA should not be hidden behind a paywall or a feature price. One feature that we often missed, was a solid audit trail of all IAM resources. Most systems we saw so far either rely on simple log files or use a short retention for this.

How To Use It

Use our free tier

Stay tuned, we will publish how you can register an organisation in our cloud offering zitadel.ch soon. Yes we have a free tier!

Run your own IAM

Stay tuned, we will soon publish a guide how you can deploy a hyperconverged system with our automation tooling called ORBOS. With ORBOS you will be able to run ZITADEL on GCE or StaticProvider within 20 minutes. To achieve this, ORBOS will bootstrap and maintain a Kubernetes cluster, essential platform components (logging, metrics, ingress, ...), a secure CockroachDB cluster and ZITADEL itself.

The combination of the tools ORBOS and ZITADEL is what makes the operation easy and scalable.

See our progress here

Give me some docs

This is work in progess but will change soon.

How To Contribute

TBA

Security

See the policy here

License

See the exact licensing terms here

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.