- Company sizes or stages where this product is overkill or insufficient
- Small organizations (for example, under ~500 employees) that primarily need SSO/MFA and basic provisioning may find the implementation effort and total cost of ownership disproportionate.
- Industries or use cases where competitors are preferable
- If privileged access management (PAM) with vaulting and session recording is the primary requirement, PAM-first platforms may be a better primary choice; an IGA product can be complementary for governance.
- Technical or procurement constraints
- If immediate, self-serve access to SOC reports and security documentation is required without vendor engagement, the vendor approach of providing certain audit materials via the trust portal or on request may extend procurement timelines.
- Budget constraints and operational capacity
- Organizations that cannot fund partner services or allocate dedicated IAM engineering resources may struggle to achieve desired outcomes without a simplified, lower-touch governance product.
- Workflow or integration constraints
- For narrow-scoped projects that require very fast wins (weeks) and minimal integration effort, lighter governance products and IdP extension options may be more appropriate.
- Red flags to address during procurement
- Confirm contractual terms for renewals, module and connector inclusion, professional services scope and pricing, and support tiers and escalation paths before executing a purchase order.
- Vendor-acknowledged limitations
- Public sources do not provide a single, comprehensive limitations list; limitations tend to be identified during proof-of-concept and connector deep dives.
- Roadmap and forthcoming features
- Roadmap items are not systematically captured in the public sources reviewed. Buyers should request a product roadmap and release cadence during procurement.
- Scale considerations
- No public hard thresholds were identified. Performance and operational behavior will depend on connector architecture, number of identities, entitlements, campaign design, and API usage.
- Security or compliance gaps
- SOC 2 and additional audit reports are provided on request rather than fully public; procurement should include requests for current SOC 2 reports and confirmation of scope where strict procurement timelines apply.
- Technical debt or architectural considerations
- Practitioner commentary has discussed differences between product editions and historical parity issues. These should be validated with current product releases.
- API and admin UX considerations
- Some practitioner comments have described administrative UX patterns that required use of API tooling for advanced tasks. This is an operational consideration when planning staffing and automation efforts.