Conflux for organizations
Run Conflux inside your company. Your data stays on your infrastructure, your people sign in with the accounts they already have, and your directory decides who is on which team.
What your organization gets
The same desktop app your engineers already use, with control where it matters.
Data stays with you
Collections, environments and history live in your own database, in your own network. Nothing is sent to conflux.uz.
Sign in the way your company already does
Microsoft Entra ID, Okta, Keycloak, Google Workspace, AD FS or on-prem Active Directory. No separate Conflux passwords to manage.
Access follows your directory
Add someone to a group and they're on the team. Disable their account and they're out of Conflux. Nobody has to remember to offboard.
How it works
Three steps from decision to first sign-in. Your IT team does the first two once; everyone else just signs in.
- 1
Deploy the server next to your database
One service inside your network, behind your firewall. No queues, no outside dependencies.
- 2
Connect it to your identity provider or Active Directory
Tell the server where your users and groups live. OpenID Connect and LDAP are both supported.
- 3
People open the same Conflux app
They pick "Sign in with company SSO", enter your server address and sign in the way they always do.
Deployment guide for IT
What your IT team controls
Everything that matters for security is decided by your team, not by us.
- Which directory groups become which teams, and who is an admin.
- Who may join: a domain allow-list, invite-only, or automatic join.
- How often group membership is re-checked.
- Where the server runs and who can reach it.
What your engineers see
Nothing new to learn. The company account lives in the same app as everything else.
- One desktop app for personal and work accounts, side by side.
- Membership managed by the directory is shown as locked, labelled "Managed by Active Directory".
- If the company account is disabled, only that account signs out. Personal accounts are untouched.
Frequently asked questions
Do you support SAML?
Not yet. Self-hosted Conflux uses OpenID Connect, which the same providers (Microsoft Entra ID, Okta, Keycloak, AD FS) all support. In practice it covers the same scenarios.
Where is my data stored?
In your own database, on infrastructure you control. Collections, environments and user data are never sent to conflux.uz.
Does this change conflux.uz?
No. conflux.uz keeps working exactly as before. A company server is a separate, independent installation.
Can people use conflux.uz and the company server at the same time?
Yes. Accounts are per server: a personal account stays on conflux.uz and a work account is added for each company server, all in the same app.
What do we need to run it?
A server or container, a PostgreSQL database and a hostname your people can reach. The deployment guide has the details.