ODINv2 is the successor of ODINv1. ODIN has been completely rewritten and enables a wide range of new features such as layer-level links and styles, searchable #tags for features, layers, symbols, etc.

ODIN uses the Matrix protocol for real-time collaboration in distributed command and control environments. Matrix is an open, federated communication standard — the same technology used by NATO, the German Bundeswehr, and the French government for secure messaging.

• Federation — Each organisation can run its own server while still collaborating with partners. No single point of failure, no central authority.
• Open Standard — No vendor lock-in. Your data stays yours. Switch servers, self-host, or use a managed service — ODIN works with any Matrix-compatible server.
• Battle-Tested Infrastructure — Leverage existing server implementations like Synapse or Tuwunel instead of building and maintaining a custom sync protocol.
• Offline-First — Full sync on reconnect. Work offline, and ODIN catches up automatically when connectivity is restored.

All collaboration data in ODIN can be end-to-end encrypted by default. This means:

• Only participants can read the data. Not the server operator, not the network provider, not even Syncpoint. The encryption keys never leave the devices.
• Megolm/Olm cryptography — the same proven, audited crypto stack used by Signal and Element. AES-256 for message encryption, Ed25519 for device verification.
• Historical Key Sharing — When a new member joins a project, existing participants securely share historical encryption keys via Olm-encrypted channels. New members get full access to existing data without compromising security.
• SAS Emoji Verification — Verify device identity through emoji comparison to prevent man-in-the-middle attacks.
• Per-project control — Enable or disable encryption when sharing a project. Once enabled, it cannot be downgraded.

Standard Matrix E2EE provides Perfect Forward Secrecy (PFS): members who join a room cannot decrypt messages sent before their join. This is ideal for messaging, but incompatible with collaborative map editing — a new team member joining an operation must see the complete operational picture, not just changes made after their arrival.

ODIN deliberately trades PFS for full data availability: when a layer is shared, the encryption keys for existing content are proactively distributed to all project members. When new members join later, keys are shared automatically — even if the sharing member is offline at that point (keys are queued server-side for delivery).

This means: anyone with access to a project's layer can decrypt its entire history. This is a conscious design decision — ODIN is a C2IS, not a messenger. Operational data must be complete and consistent for all authorized participants.

Known limitation: After Megolm key rotation (triggered by message count, time, or membership changes), keys for the new session are shared with current layer members automatically during encryption. Members who join after a rotation receive older keys at share time and newer keys via the safety-net mechanism when an online member detects their join. In the rare case where no existing member is online during the join, post-rotation content may be temporarily undecryptable until an existing member comes online.

E2EE makes ODIN suitable for handling classified and sensitive operational data in environments where data sovereignty and confidentiality are non-negotiable.

Project owners and administrators can manage team membership directly from ODIN:

• Invite new members by searching the Matrix user directory
• Assign roles (Owner, Administrator, Contributor) with different permission levels
• Remove members from projects
• All role changes are enforced server-side through Matrix power levels

Make sure to join our Matrix ODIN Community Chat Room to get the latest news about ODIN.

ODINv2 supports RGB-encoded terrain tiles (Mapbox Terrain-RGB) for elevation data. Terrain sources can be configured from XYZ tile URLs, TileJSON endpoints, or TileJSON Discovery servers (e.g. mbtileserver) — where individual discovered tilesets can be independently marked as terrain. When configured, ODIN displays live elevation at the cursor position and provides an Elevation Profile tool that charts elevation vs. distance along any line — whether drawn on-the-fly or from an existing feature. Drawn profile lines are fully editable, and the chart updates automatically as the geometry changes. The tool works independently of the current viewport, sampling elevation data directly from terrain tiles.

For setup instructions and usage details, see docs/elevation-data.md.

NIDO (ODIN reversed) is a WebSocket-based API that enables external applications to integrate with ODIN in real-time. This opens up powerful possibilities for extending ODIN's capabilities:

• Digital Twin: Mirror ODIN data in external systems for monitoring or backup
• Automation: Programmatically create, update, or delete features from scripts or external tools
• System Integration: Connect ODIN to other C2 systems, sensors, or data sources
• Real-time Analytics: Stream project data to external analytics or visualization tools

External applications can subscribe to live data changes, query project data, send commands to modify layers and features, and even control the map view. All coordinates are exposed in standard GeoJSON format (EPSG:4326 lon/lat).

To connect an external application, click the LAN icon in the ODIN toolbar and configure your WebSocket server URL.

For detailed protocol documentation and examples, see docs/NIDO.md.

ODIN supports two different mechanisms for external data integration:

NIDO provides complete control over your project and should only be used with servers you fully trust. Live Data Sources are ideal for displaying real-time tracking data from external systems without affecting your project's stored data.

ODINv2 will migrate all of your existing ODINv1 projects on first start. You will be able to further use ODINv1 in parallel but we will not update newly or updated projects after the first start of ODINv2. If you do have any ODINv1 layer files (*.json) you can import them at any time via drag&drop onto the ODINv2 map.

Self-Update is enabled by default and ODIN will check for newer versions. In order to disable Self-Update one can use the environment variable ODIN_SELF_UPDATE with a value of 0.

If you are not connected to the Internet and you want to use the "Search for places" function you need to host your own OSM Nominatim server. In order to make ODIN use your on-premise instance of Nominatim you cat use the environment variable NOMINATIM_URL. The default value for this parameter is https://nominatim.openstreetmap.org/search.

You are an offline-first user and want to host your own map server (i.e. on your laptop)? GeoWebServer is way to big and uses too many resources? Just fire up mbtileserver, provide a mbtile file that contains all your map tiles and you are done.

Copyright (c) Syncpoint GmbH. All rights reserved.

Licensed under the GNU Affero GPL v3 License.

When using the ODIN or other GitHub logos, be sure to follow the GitHub logo guidelines.