junctional.io
EN-GB EN-US View on GitHub
Product tour

See JIM in action.

A walk through the JIM admin portal, the synchronisation lifecycle, and the headless surfaces that make Identity as Code possible. Every screenshot is from a recent release.

Switch the screenshots between light and dark.

  1. JIM admin portal home page. Sidebar navigation on the left, a main pane showing system health summary tiles, recent activity feed, and an operations panel with live progress bars.
    01 / 12 #

    The dashboard

    JIM opens to a real-time dashboard. System health, recent activity, and operation progress at a glance, with live updates as work happens in the background.

  2. Connected Systems list view. A table of configured systems with type, status, last sync time, and counts; a 'New Connected System' action in the toolbar.
    02 / 12 #

    Connected Systems

    Every system JIM talks to is a Connected System. HR platforms, directories, applications, files. Configure them once, then let JIM keep them in sync.

  3. Connected System detail page open on the Schema tab. Object class definitions auto-discovered from the source system, each expandable to attributes, with checkboxes for what to bring into the Metaverse.
    03 / 12 #

    Schema discovery

    JIM auto-discovers schema from supported systems and lets you choose what to bring into the Metaverse. No hand-edited XML, no static configuration files to keep up to date.

  4. Connected System detail page open on the Object Matching tab. Object Matching Rule editor with attribute predicates and rule priority.
    04 / 12 #

    Object Matching

    Self-contained Object Matching Rules correlate identities across systems. Constant-time matching keeps performance flat as connector spaces grow.

  5. Synchronisation Rules list view. Table of rules showing direction (inbound, outbound, bidirectional), source and target objects, and enabled state.
    05 / 12 #

    Synchronisation Rules

    Rules define how identity data flows between systems. Inbound, outbound, or bidirectional, with full attribute-level control.

  6. Synchronisation Rule editor open on Attribute Flow. A two-column mapping between source and target attributes, with an expression preview for each transformation.
    06 / 12 #

    Attribute Flow

    Map any source attribute to any target attribute, with transformations expressed in JIM's built-in expression language. If you've written a spreadsheet formula, you'll be writing flow rules in minutes.

  7. Metaverse Users page showing fused identity records. Each row has the canonical attributes assembled from one or more Connected Systems.
    07 / 12 #

    The Metaverse

    All identity data fuses into a central Metaverse. One canonical view of every identity, regardless of how many systems contributed to it.

  8. Metaverse Object detail page on the Changes tab. Each attribute change is listed with timestamp, contributing connector, and the inbound rule that applied the value.
    08 / 12 #

    Full causality

    Every attribute on a Metaverse Object knows where it came from. Every change knows what caused it. Trace any value back to its source, end-to-end.

  9. Activities history page. Timeline of synchronisation runs with run id, start and end times, status, and counts of objects added, updated, and deleted.
    09 / 12 #

    Operational visibility

    Every synchronisation run, every change, every operation. Live progress, full history, audit-grade detail.

  10. Schedules page. List of scheduled jobs with cron and interval triggers, multi-step pipelines, and the next run time for each.
    10 / 12 #

    Automation

    Built-in scheduler with cron and interval triggers. Multi-step and parallel execution. JIM runs itself once configured.

  11. PowerShell terminal session running JIM cmdlets. Output rendered as a table; previous commands visible in scrollback.
    11 / 12 #

    Identity as Code

    Every operation in JIM is scriptable through 168 PowerShell cmdlets. Configuration becomes code: version-controlled, repeatable, auditable.

  12. JIM REST API documentation page rendered with Scalar. Endpoint list grouped by controller on the left, request and response schema for the selected endpoint on the right.
    12 / 12 #

    Full REST API

    Over 250 endpoints across 21 controllers, documented with an interactive Scalar reference inside every environment, including air-gapped deployments.

Try it yourself.

Every screenshot here is from a recent release. The source is on GitHub, and you can stand up a working instance with one command.

View on GitHub Explore the capabilities Read the documentation Join Early Access

Screenshots from a recent JIM release.