Solution · Identity and access

Zero-Code puts sign-in in front of every internal tool, without touching it.

Zero-Code is our own technology. Dashboards, admin panels and internal APIs get single sign-on and access rules from one install on the cluster.

A cluster, after one install

The cluster reports itself: how many workloads are protected, how many are being watched, and which one to do next.

What changes

The problem as most companies have it today, and the same thing with AuthFI.

Today: Internal tools sit behind a VPN or a shared password

With AuthFI: People sign in to each tool with their own account

Today: Adding sign-in means a library and a release per tool

With AuthFI: One install on the cluster, and nothing added to any tool

Today: Nobody has the list of what is running

With AuthFI: Every service and its routes are listed for you

Today: Access is all or nothing

With AuthFI: Rules per route, by role and group

Each step, on the screen you would use.

Discover

Once installed, every workload and the routes it serves are listed, with what is protected and what is not.

No sidecars, nothing added to pods

Routes found from real traffic

Protected and unprotected, side by side

Protect

Give a service a hostname and assign groups to it. Rules start in watch-only, so you see what would be refused before anything is.

Watch first, then enforce

One service at a time

Refusals written to the record

Runs on Kubernetes on Linux. Nothing is refused until you switch a service to enforce.

Zero-Code

How it works, and its limits

Zero-Code docs

Requirements and the three steps

Workforce identity

Accounts, groups and single sign-on