SailPoint IIQ in 2026 — What's Actually Changed
IdentityNow gets the spotlight, but IIQ isn't going anywhere. For complex enterprise environments it's still the right call — the honest state of the platform.
I've spent a significant portion of my career inside SailPoint IdentityIQ environments — building connectors, writing BeanShell rules, debugging provisioning workflows at 11pm. So when people ask me whether IIQ is still worth investing in, I don't give a marketing answer.
The platform shift is real
SailPoint has been pushing IdentityNow (their SaaS offering) hard. Roadmap investments, new connectors, and most of the marketing budget are flowing that direction. If you're starting a net-new identity program and don't have complex customization requirements, IdentityNow is genuinely a good option.
But here's the thing: most enterprise environments aren't starting from scratch. They have years of IIQ configuration, custom connectors to legacy systems, JML workflows tuned to their HR processes, and compliance requirements that the out-of-the-box SaaS model doesn't easily accommodate.
Where IIQ still wins
- Complex on-prem or hybrid environments where cloud SaaS isn't viable
- Highly customized provisioning logic that requires BeanShell or Java
- Legacy application connectors with no SaaS equivalent
- Organizations with strict data residency requirements
- Environments already running IIQ with significant existing investment
What's actually changed in practice
The IIQ developer community has contracted. Fewer new IIQ deployments means fewer people learning the platform from scratch, which means experienced IIQ developers are harder to find — and the ones who are available often come through large SI firms at significant markup. That gap is most of what EternalDev's identity work is.
"If you have an IIQ environment that needs work, an independent consultant who knows the platform is almost always faster and cheaper than going through a large firm. The platform knowledge is the same — the overhead isn't."
The AI angle
One thing I've been experimenting with is using AI to assist with IIQ development work — specifically, using LLMs to help write and review BeanShell rules, generate documentation for existing workflows, and analyze access certification data. It's not replacing the platform expertise, but it's making the work faster.
If you're maintaining an IIQ environment and wondering whether to migrate to IdentityNow or invest in your existing setup, the answer depends entirely on your environment's complexity. Happy to have that conversation.
