# OSIRIS JSON Open Standard for Infrastructure Resource Interchange Schema
Vendor-neutral JSON format for describing infrastructure resources and their topological relationships across heterogeneous IT and OT environments

# What OSIRIS is
OSIRIS (Open Standard for Infrastructure Resource Interchange Schema) **defines a vendor-neutral JSON format** for describing infrastructure resources, their properties and their topological relationships across heterogeneous environments with an extension path for OT where applicable.

As an **interchange schema**, OSIRIS JSON normalizes exports from diverse sources and enables portable consumption by tools dedicated to diagramming, documentation, inventory/CMDB workflows, audit evidence and integrations without requiring each consumer to implement and maintain vendor-specific parsers.

OSIRIS JSON defines a canonical JSON schema that acts as a neutral middleware between infrastructure data sources and consuming applications. Instead of embedding vendor-specific parsing logic into every tool, OSIRIS JSON adopts a translation-layer approach:

- PRODUCERS (parsers, translators, discovery agents) translate source/vendor representations into OSIRIS JSON documents.
- CONSUMERS (diagramming tools, CMDBs, IPAMs, DCIMs, documentation pipelines) read and process a single, well-defined schema.

This decouples data sources from consuming applications, reducing integration complexity from S×C (S sources × C consumers) to P+C (P producers + C consumers).

This decouples data sources from applications and reduces integration complexity. In an environment with **S** source systems and **C** consuming applications, integration effort shifts from **S×C** direct mappings to **S** producer mappings (**source > OSIRIS**) plus **C** consumer mappings (**OSIRIS > application**).


## The challenge
Infrastructure data is exposed through vendor-specific formats and models, with inconsistent semantics for equivalent concepts identity, properties, relationships and hierarchy. In mixed environments spanning hyperscalers, public cloud, on-prem systems and OT infrastructure, the problem compounds. The result is fragmented sometime high-cost tooling, inconsistent exports and documentation with fragmented or low quality topology that quickly becomes outdated.


### The problem
Modern infrastructure spans multiple stacks and providers: hyperscalers (AWS, Azure, GCP etc.), public clouds providers, on-prem datacenters and complex OT environments integration.
While some platforms export inventories (often as JSON), the representations are inconsistent across vendors even for equivalent concepts like identity, properties, and relationships.
Cross-platform visibility and portable consumption by tools (diagramming, inventory, audit) without requiring each consumer to implement vendor-specific parsers.

Accurate topologies and systems architecture documentation is expensive and fragile. Teams rely on fragmented docs and hand-drawn diagrams. Critical context lives in people's heads.


### The solution
OSIRIS JSON defines a vendor-neutral JSON schema for describing infrastructure resources and topological relationships across heterogeneous environments.
The goal of OSIRIS JSON is to normalize exports from hyperscalers and cloud providers as well as on-prem datacenters devices like (compute, storage, network).
From initial release of the Specification OSIRIS JSON supports OT inclusion by design.

Cross-platform visibility and portable consumption by tools (diagramming, inventory, audit) without requiring each consumer to implement vendor-specific parsers.


---

## What you get
Six core capabilities that make OSIRIS JSON an open standard for infrastructure resource and topology interchange.

1. Unified design
   Built for heterogeneous IT environments, with a clear extension path for OT and other domains as adoption grows.

2. Explicit relationships
   First-class representation of connections, dependencies, containment, and other topology relationships.

3. Flexible grouping
   Support for logical and physical grouping that reflects real organizational and architectural structures without forcing a single taxonomy.

4. Provider attribution
   Resources preserve traceability to their source system/provider while using a standardized, vendor-neutral representation.

5. Designed for extensibility
   A defined mechanism for vendor-specific properties and custom resource types without breaking compatibility.

6. Three-Level validation
   Structural (schema), semantic and domain validation improving consistency and data quality when validation tooling is applied.

---

## Design principles
OSIRIS JSON is a static snapshot interchange format. It captures what exists and how it relates at a point in time. It was not designed as a real-time monitoring system, a deployment tool, or an Infrastructure-as-Code engine.

| OSIRIS JSON is NOT | OSIRIS JSON IS |
|---|---|
| Monitoring/Telemetry | Reliable, flexible infrastructure snapshots |
| Observability platforms | Documentation-ready outputs |
| Infrastructure as Code | Diagram-friendly topology |
| Configuration management | Feeding CMDB / IPAM / DCIM workflows |
| - | Audit support |

## Get hands-on with OSIRIS JSON examples
Explore a Microsoft Azure and AWS OSIRIS JSON topology snapshot with relationships, providers and groupings captured in one portable JSON document.

[OSIRIS JSON IT Examples](https://osirisjson.org/en/docs/osiris-examples/01-it-infrastructure)
[OSIRIS JSON OT Examples](https://osirisjson.org/en/docs/osiris-examples/02-ot-infrastructure)

---

## Resources
- [OSIRIS JSON Github](https://github.com/osirisjson)
- [OSIRIS JSON website](https://osirisjson.org)
- [OSIRIS JSON documentation](https://osirisjson.org/en/docs)
- [OSIRIS JSON core schema](https://osirisjson.org/schema/v1.0/osiris.schema.json)