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 IT and OT environments. OSIRIS is a neutral interchange schema: it is designed to normalize and standardize infrastructure data exports from diverse domains and enable portable consumption by tools without requiring consumers to develop and maintain vendor-specific parsers.
I started writing OSIRIS in 2025 after years of designing and helping maintain heterogeneous infrastructure stacks: public cloud providers and hyperscalers, on-prem data centers and complex environments where IT and facility OT systems coexist. Along the way I experimented, failed and learned a lot, but one recurring problem kept showing up: getting a clear, point-in-time view of resources and their relationships and then comparing snapshots over time without rebuilding bespoke integrations for every tool and vendor, or relying on tribal colleagues knowledge that most of the time isn’t consistently documented.
OSIRIS addresses this by defining a vendor-neutral JSON interchange schema for infrastructure topology. Rather than requiring every consuming tool to implement vendor-specific parsers, OSIRIS separates responsibilities: producers translate source data into OSIRIS documents, and consumers read and process OSIRIS documents. In its first release, OSIRIS is intentionally a static snapshot format: it describes what exists and how it relates at a specific time, while leaving room for future growth and expansion.
