OSIRIS JSON v1.0 specification now available

OSIRIS JSON v1.0 specification now available

The first stable OSIRIS JSON specification defines a vendor-neutral JSON interchange format for infrastructure topology across cloud, on-premises, and OT-aware environments.

February 1, 2026 Updated February 1, 2026 By Tia Zanella
Share
download Download MD

OSIRIS JSON v1.0 specification is now available

OSIRIS JSON has reached its first stable specification release on February 1, 2026.

Version 1.0.0 defines OSIRIS, the Open Standard for Infrastructure Resource Interchange Schema, as a vendor-neutral JSON format for describing infrastructure resources, their properties, and their topological relationships across heterogeneous environments. The initial release is centered on IT infrastructure and is designed with an extension path for Operational Technology where end-to-end visibility matters.

Why this release matters

Infrastructure data already exists in many systems, but it rarely arrives in a form that is portable. Hyperscalers, network vendors, virtualization platforms, and on-premises tools all export inventories differently, even when they use JSON. The result is repeated parser work, inconsistent topology semantics, documentation drift, and expensive integrations that do not scale well across teams or tools.

Rather than wasting time and money developing every software integrations from scratch to learn a hundred different vendor-specific dialects, OSIRIS JSON separates the responsibilities:

  1. The OSIRIS JSON producers translate the messy, fragmented data of the real world into a clean OSIRIS JSON document.
  2. The OSIRIS JSON consumers read that document to provide a clear, point-in-time view of what exists and how it all relates. With the OSIRIS JSON document the consumers can produce topologies, diff, high quality automated documents and more.

What v1.0 includes

The first stable specification focuses on the fundamentals needed for portable infrastructure topology:

  • A unified resource model for compute, network, storage, application, and related infrastructure components
  • First-class connections for dependencies, containment, and topology relationships
  • Grouping constructs for logical and physical structure
  • Provider attribution so normalized resources still preserve source traceability
  • An extension model for vendor-specific properties and custom types without breaking compatibility
  • Validation guidance spanning structural, semantic, and domain-level checks

This release is intentionally practical. It is designed for documentation, diagram generation, inventory workflows, audit evidence, and tool integrations.

What OSIRIS JSON is not

OSIRIS JSON is a static snapshot interchange format. It captures what exists and how it relates at a point in time.

It is not a real-time monitoring protocol, not an observability platform, not an Infrastructure-as-Code language, and not a configuration management system. The goal of the specification is narrower and more useful: provide a stable schema that producers and consumers can implement independently.

Read the specification

The specification is published as a stable open standard and is accompanied by the core schema and example topologies:

OSIRIS JSON v1.0 is released under CC BY 4.0 and published with the status Stable.

OSIRIS JSON for Cisco APIC, NX-OS and IOS

March 30, 2026

Cisco is a broad producer target for OSIRIS JSON, spanning APIC policy fabrics, NX-OS datacenter switching, and IOS routing and campus infrastructure through one portable topology model.

What an OSIRIS JSON producer is expected to do

March 24, 2026

The OSIRIS producer guidelines and SDK documentation define how exporters should discover, normalize, redact, validate, and publish deterministic OSIRIS JSON snapshots.

Validate OSIRIS JSON documents

March 21, 2026

OSIRIS now defines a layered validation model, a canonical validation engine, and a CLI contract designed for deterministic local and CI workflows.