Skip to content

Product Roadmap

JIM has completed pre-release stabilisation. The core identity lifecycle - Import, Sync, Export, and Schedule - is fully functional, and the platform has been hardened for production with bounded-memory pipelines validated at 500,000-user scale (synchronised cross-domain across two directories, with groups of up to 495,000 members), an OWASP Top 10:2025 assessment, supply chain hardening, and comprehensive integration test coverage across all sync scenarios. The roadmap below outlines the milestones ahead as JIM progresses towards its first stable release and beyond.

For the latest status and issue tracking, see the public JIM Roadmap project board.

🎯 v1.0 - Identity Lifecycle Complete

The first stable release, delivering a production-ready identity lifecycle platform.

  • Expression engine enhancements (additional functions, improved error reporting)
  • Advanced scheduling capabilities (dependencies, conditional execution)
  • Comprehensive REST API coverage for all administrative operations
  • Full PowerShell module coverage with parity across all API endpoints

🌳 v1.x - Connector Ecosystem

Expanding the range of systems JIM can connect to out of the box. The SCIM 2.0 Client Connector has already shipped and is listed here for continuity.

Connector Description Status
JIM SCIM 2.0 Client Connector SCIM 2.0 endpoints ✅ Available
JIM SQL Connector Microsoft SQL Server and Oracle Database ✅ Available
JIM SQL Connector: PostgreSQL and MySQL The same connector, extended to two further engines Planned
JIM PowerShell Connector PowerShell Core scripts Planned
JIM REST Connector REST API web services Planned

Each connector follows JIM's established connector architecture, supporting schema discovery, full and delta import, and export with the same reliability guarantees as the built-in connectors.

🏛️ v2.0 - IGA Foundation

Evolves JIM's core IDAM capabilities so identities can be managed directly in JIM, without depending on Source-of-Record systems for everyday changes. The focus is depth in the existing identity surface (Users, Groups, custom types) rather than branching into adjacent domains.

Entitlement Management

  • Direct group management
    Create, update, and delete groups directly within JIM rather than only synchronising them from Connected Systems.
  • Governance
    Access reviews and attestation, delegated administration, dynamic memberships, time-based memberships, self-service requests, and approval workflows, etc.

Identity Lifecycle Management

  • Direct user management
    Create, update, and delete users directly within JIM rather than only synchronising them from Connected Systems.
  • Self-service for locally-managed attributes
    Allow users to maintain attributes owned by JIM (photos, pronouns, bios, and similar) rather than relying on upstream systems.
  • Lifecycle Workflows
    Event-driven workflows that automate joiner/mover/leaver processes end-to-end.

Fine-grained RBAC

  • Custom permission models
    Granular roles and permissions inside JIM itself, so administrators can shape access to JIM's functionality to match their organisation's structure.