Where JIM is going.
JIM is built in the open. The roadmap below tracks the major milestones from a production-ready core to a full identity governance platform; the live status of each comes straight from the project's GitHub milestones. No dates promised, just honest order and direction.
Four milestones, one direction.
Each milestone is a meaningful step: a stable core, a complete ILM platform, a growing connector range, and then governance. Status reflects the live state of each milestone in the JIM repository.
- v0.9 Shipped
Stabilization
Maturing the platform from MVP to production-ready: completing configuration controls, deepening integration test coverage, and hardening the core synchronization pipeline. The engine internals were refactored into a clean domain core, laying the groundwork for connector extensibility and the governance features that come later.
- v1.0 In progress
ILM completion
The first production-ready release. Robust Synchronization Rules, richer identity-fusing options, more lifecycle automation triggers, and operational monitoring come together into a complete Identity Lifecycle Management platform, ready for production environments.
- v1.x Planned
Connectors
Expanding the range of systems JIM connects to. The SQL and SCIM 2.0 connectors shipped ahead of this milestone; still to come are PostgreSQL and MySQL support in the SQL Connector, generic PowerShell and REST connectors, and Entra ID, alongside connector-framework improvements drawn from real v1.0 deployments.
- v2.0 Future
IGA foundation
Evolving JIM from synchronization into governance, with identities and entitlements managed directly in JIM: entitlement management with access reviews and approval workflows, self-service identity lifecycle, and fine-grained role-based access control inside JIM itself.
Direction, not commitments.
Some things we think are right have not been scheduled, and we would rather list them here than let them read as though they already exist. Nothing below has shipped and nothing below is promised; the milestones above are what we are actually building.
-
JCL (JIM Configuration Language)
A declarative format for a whole JIM deployment: describe Connected Systems, Synchronization Rules, and Attribute Flow as data, then apply it. Identity as Code works today through the PowerShell module, which covers every operation in the product; JCL would add a second, declarative surface alongside it. Not started.
What's just shipped.
JIM releases early and often. Every release is signed, carries an SBOM attestation, and ships with full notes on GitHub. The headline below is always the latest stable release; follow the links for the detail and the full history.
Track the work directly
Want to shape what comes next?
The Early Access Program puts your real-world deployment in front of the team building JIM, with direct influence over what lands in v1.0 and the connectors that follow. Upvotes in GitHub Discussions genuinely move priorities.