Solution · Identity and access

Identity that runs inside your own cloud.

For companies whose data cannot leave their boundary: AuthFI runs in your AWS, Google Cloud, Azure or Oracle account, or your own data centre.

The AuthFI console dashboard.The AuthFI console dashboard.

What changes

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

Today: Identity data sits in a vendor's cloud, in a region they chose
With AuthFI: It sits in the account and region you name
Today: The alternative is running open-source identity yourselves
With AuthFI: The same product, installed inside your boundary
Today: Signing keys are the vendor's
With AuthFI: Each project signs with its own keys, kept in that region
Today: Self-hosting means your own upgrades
With AuthFI: The same console and the same updates as everyone else

How it works

Each step, on the screen you would use.

Keys

Your keys, in your region.

Every project has its own signing keys. Rotating one does not sign anybody out.

Keys per project

Rotation with no sign-out

Secrets sealed on arrival

Keys and secrets in the AuthFI console.Keys and secrets in the AuthFI console.

Our region

Virginia, USA

AWS, US East

us-east-1

Our region

Mumbai, India

Google Cloud, Mumbai

asia-south1

Your own cloud

Any cloud

AWS, Google Cloud, Azure, Oracle, or your own data centre. Run by you, or by us inside your boundary.

Enterprise

Tell us where it has to run.