Open Standard for Infrastructure Resource Interchange Schema

OSIRIS JSON produces vendor-neutral JSON documents to describe infrastructure resources and their topological relationships across heterogeneous IT and OT environments. An interchange format designed for portability, end-to-end clarity, and OT inclusion from the ground up.

$
crisis_alert

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.

warning
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.
verified

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.

check_circle
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.

schema

Unified design

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

hub

Explicit relationships

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

account_tree

Flexible grouping

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

dns

Provider attribution

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

extension

Designed for extensibility

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

verified_user

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.

block OSIRIS JSON is NOT

close
Monitoring/Telemetry
Use Prometheus, Grafana, Zabbix, OpenTelemetry.
close
Observability platforms
Use Cilium, Grafana Tempo/Loki etc.
close
Infrastructure as Code
Use Terraform, Pulumi, TOSCA.
close
Configuration management
Use Ansible, Puppet, Chef, Salt.

check_circle OSIRIS JSON IS

Optimized for scenarios where documentation and topology must be exchanged between systems and teams.

photo_camera
Reliable, flexible infrastructure snapshots
Capture "what exists" and "how it relates" at a point in time.
description
Documentation-ready outputs
Enable consistent inventories, technical summaries and system context.
flowsheet
Diagram-friendly topology
Provide normalized relationships for automated visualization and diagram generation.
sync_alt
Feeding CMDB / IPAM / DCIM workflows
Export normalized data into systems of record and asset management tools.
security
Audit support
Assist evidence collection and traceability by standardizing structure and relationships.

Get hands-on with OSIRIS JSON examples

Explore real-world OSIRIS JSON topology snapshots with relationships, providers and groupings captured in one portable JSON document.

IT Examples

Application running on Azure with API Services on AWS

OSIRIS multi-hyperscaler example showing Azure and AWS resources in a shared topology

Get involved in the community

Ways you can contribute

code

Code

Build producers/parsers for hyperscalers, cloud platforms and on-prem IT/OT systems.

description

Documentation

Improve guides, write tutorials and real-world use cases to help others adopt OSIRIS JSON.

science

Testing

Validate the spec and schema with real infrastructure topologies and edge cases.

lightbulb

Feedback

Report issues, suggest improvements, or propose extensions and new features.

build

Tooling

Create SDKs, CLI tools, validators, exporters and documentation/diagramming tools.

share

Spread the Word

Write posts, give talks, record demos and share OSIRIS JSON with your network.

design_services

Design & templates

Design high quality diagram templates, graphic layouts for docs and website, icons, sample datasets and reusable assets for the community.

Roadmap

OSIRIS JSON is community-driven

OSIRIS JSON was born facing real-world problems and continues to grow through feedback, new ideas and practical contributions. If you have suggestions or want to help, jump in your input helps shape both the roadmap and the standard.

Support OSIRIS JSON

OSIRIS JSON is in its early days. Right now, adoption and feedback matter more than funding. Try the tooling, test it against real infrastructure, and tell us what's missing.

terminal

Use it and report back

Run a producer on your infrastructure, validate the output, and open an issue when something breaks.

edit_note

Contribute

Submit real-world examples, improve docs, or build a producer for your platform.

campaign

Spread the word

Share OSIRIS with your team, write about your experience, or mention it in relevant communities.