Deployed in minutes, anywhere.
JIM is a single Docker stack with no external dependencies. It runs the same way on a developer laptop, on a small VM at the edge, or as a hardened production fabric, online or fully air-gapped. This is how it gets deployed; the docs have the commands.
From laptop to production.
Developer
Up and running in minutes, on a laptop.
Stand up a complete JIM instance with one command, or open the repository in a ready-made devcontainer or GitHub Codespace with everything preconfigured. Ideal for evaluation, development, and building configuration as code.
SME / Edge Sync
A single Docker stack on any host.
For smaller deployments and edge instances, JIM runs as one Docker Compose stack on a VM or server: web, worker, scheduler, and database. Templated with Identity as Code, the next instance is a parameterised copy of the first.
Enterprise
Hardened, sized, and built for scale.
For organisation-wide deployments, JIM sits behind your reverse proxy and TLS, authenticates against your identity provider, and is sized to your largest Connected System. Hardening, operations, and upgrades are documented for long-running production use.
Two shapes, one platform.
JIM deploys in two patterns that share the same engine and operational model. Choose per problem; you can run both.
Centralised
One JIM instance as the organisation's identity fabric, with every major system connected to a single Metaverse.
Edge Sync
Many lightweight instances, each solving one bounded synchronisation problem and managed independently.
Bundled database, or your own.
JIM keeps its state in PostgreSQL, and supports two database topologies. Run the one it ships with, or point it at your own.
Self-contained
A PostgreSQL container ships in the stack and is used by default. Nothing extra to provision: bring up JIM and the database comes with it.
External
Point JIM at an existing PostgreSQL server instead, to reuse a managed database service, or gain the high availability and backups your platform already provides.
Install commands live in the docs.
Step-by-step install, air-gapped setup, TLS and reverse proxy, host sizing, and upgrades are all in the documentation, kept current with each release.
Same platform, any footprint.
Same operational model whether it is one laptop or an air-gapped estate. See how the two topologies map to real scenarios, or jump straight to the docs.