Choosing identity governance
for 250 to 5,000 identities
Most identity governance tools were built for large enterprises with an IAM department, or for one identity platform. A mid-sized organisation weighs other things: how soon it sees a result, who keeps it running, and whether it covers the systems outside Microsoft. This page compares the five kinds of tools on those points.
The same questions for each kind of tool
Each column is a category. Within a category, products differ; ask every vendor the same questions.
| Question | Classical IGA suite | Provisioning tool | Governance in your identity platform | Visibility and posture tool | RapidValue |
|---|---|---|---|---|---|
| First result | Classical IGA suiteAfter the project phase, usually months | Provisioning toolOnce the connectors are set up | Governance in your identity platformQuickly, for the applications already in the platform | Visibility and posture toolQuickly, for the cloud and SaaS accounts it is connected to | RapidValueOne morning: HR and one application connected and the gaps on screen |
| Who sets it up and runs it | Classical IGA suiteUsually an integrator, for the set-up and for changes | Provisioning toolYour IT team | Governance in your identity platformYour IT team, in the platform’s console | Visibility and posture toolYour security or cloud team | RapidValueYour team, from proposals based on your own data. A partner is optional |
| Which systems it covers | Classical IGA suiteMany, through connectors built in the project | Provisioning toolThe systems it creates accounts in | Governance in your identity platformMostly the applications that sign in through the platform | Visibility and posture toolCloud accounts and SaaS, often wide | RapidValueHR, Entra ID, Active Directory, LDAP, SCIM, REST and application templates |
| Effective access and usage | Classical IGA suiteDepends on the product | Provisioning toolDepends on the product | Governance in your identity platformDepends on the product | Visibility and posture toolYes, where the system or the logs give it | RapidValueYes, where the system or the logs give it. Today: last sign-in per account from Entra, Google, Salesforce, ServiceNow and LDAP/AD; nested groups from Entra and AD/LDAP |
| Reviews, conflicting access and roles | Classical IGA suiteYes, with a lot of configuration | Provisioning toolOften limited | Governance in your identity platformDepends on the licence | Visibility and posture toolMostly findings. Decisions and approvals usually happen in another tool | RapidValueReviews, segregation of duties and roles in business language |
| Service accounts and AI agents | Classical IGA suiteDepends on the product | Provisioning toolRarely covered | Governance in your identity platformFor the platform’s own identities | Visibility and posture toolOften discovered. An owner and a review rhythm are usually not part of it | RapidValueAn owner, a reason and a review rhythm for each, across platforms |
| Where it runs | Classical IGA suiteDepends on the product | Provisioning toolDepends on the product | Governance in your identity platformIn the platform vendor’s cloud | Visibility and posture toolDepends on the product | RapidValueAt Scaleway in Amsterdam, backups in Paris. In agent mode credentials stay in your network |
| How the price works | Classical IGA suiteA licence plus a services budget | Provisioning toolPer user or per connector | Governance in your identity platformOften part of a licence tier | Visibility and posture toolDepends on the product | RapidValueOne price per identity, amounts at general availability |
RapidValue is not for everyone
It is built for organisations of about 250 to 5,000 identities without an IAM department. Look elsewhere in these cases.
A lighter tool, or the governance in your identity platform, is usually enough.
At that size you need things RapidValue does not offer yet. We would rather say so now.
When nearly all your applications sign in through one identity platform, start with what it offers. Read what changes when they do not.
When you need one first, or next to us
RapidValue does not find those yet. A visibility tool finds them; RapidValue gives the ones you find an owner and a review.
RapidValue reads AWS IAM users and keys only for the users you mark as agents, and Google Cloud service accounts only once you declare them.
Keep it. RapidValue answers the next question: who owns each account and who approved it.
Questions when choosing a tool
What is identity governance and administration (IGA)?
IGA decides and proves who may access what. It connects your HR system to the accounts in your applications, routes requests and approvals, runs access reviews, checks combinations you do not allow, and records every decision for your audit.
How long does an IGA implementation take?
A classic project usually runs for months with an integrator. With RapidValue you see a first result in one morning, with HR and one application connected, and run a proof of concept the week after, in about a week.
Can we run identity governance without an IAM team?
Yes, that is who RapidValue is built for. The platform proposes the configuration from your own data and your team approves, edits or dismisses each proposal. A partner helps where you want advice.
How is RapidValue priced?
One price per identity, with no modules or paid add-ons for what the product does. The amounts are published at general availability.
Where is it hosted?
RapidValue runs as a managed service at Scaleway, a French cloud provider, in Amsterdam, with backups in Paris.