About

OAuth clients belong in your manifests.

Clients clicked into a console drift from Git. We're building an identity provider whose clients will ship with the apps that use them.

How we build it

Manifests as the source of truth

nauthera.io/v1alpha1 · OIDCClient · Branding

An operator registers each OIDCClient from its app's namespace and writes its secret into a Secret. Branding is defined, not yet reconciled.

Standards, not inventions

Apps connect through published specs, not custom protocols. Gaps are marked spec by spec.

Refuse rather than misbehave

Contradictory client manifests fail at apply; most unsafe production settings stop the server before it serves traffic.

Contract first

HTTP endpoints from OpenAPI, the control plane from protobuf, resources from Go types. CI catches drift.

Where it stands

Pre-1.0

Built and tested:

the OAuth 2.0 and OpenID Connect server, hosted sign-in, organizations, TOTP MFA, the audit log, the operator for OIDCClients and a first admin dashboard.

Planned:

branding from manifests (#404), the rest of the dashboard (#502), passkeys (#200) and a first release (#307).

The source is private.

See the roadmap

Who builds it

Nauthera GmbH

Oberburg, Switzerland

The Swiss company building Nauthera.

Imprint

Michael Beutler

Founder

LinkedIn GitHub

Hear when the operator ships

Pre-1.0. We'll email you when the operator ships.

By joining, you agree to our Privacy Policy and Terms.