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.

OSIRIS JSON

Open Specification Infrastructure Resource Interchange Schem

Open Specification Infrastructure Resource Interchange Schem