Hosted sign-in and access for SaaS
Skip the auth plumbing. Dhuri One gives your product sign-in, organizations, roles and usage behind one API.
What it covers
- Sign-in. An OpenID Connect provider per environment, test and live, with your own name and logo. Passwords, one-time codes, Google and two-step verification.
- Organizations and roles. Teams and roles defined by your project. Ask whether a user can do something and get a yes or no with the reasons.
- Entitlements and usage. Plans, features and metered usage in the same call.
- Operations. Signed webhooks, an audit trail of keys and grants, and API keys shown once and stored hashed.
Standards, not lock-in
Dhuri One speaks OpenID Connect and OAuth 2.0, so your app talks a standard protocol. It runs hosted or self-hosted, and has a Java SDK.
Built for assistants too
The reference docs at one.dhuritech.com/docs also ship as llms.txt, so an AI assistant can read the whole platform in one file.
Weighing it up? Read SaaS sign-in: build or buy.
Questions
What is a hosted OpenID Connect provider?
A service that signs your users in using the standard OpenID Connect protocol, so your application does not store passwords or implement login itself.
Can Dhuri One be self-hosted?
Yes. It is built to run hosted or on your own infrastructure.
Is there an SDK?
There is a Java SDK, and the API is standard OpenID Connect and OAuth 2.0.
Keep reading
Tell us what you are building.
Sign-in, payments or point of sale: one message to a real person.