Introducing OSIRIS JSON

I started drafting OSIRIS in late 2025 after years of architecting and maintaining highly heterogeneous infrastructure stacks. If you’ve ever had to manage a footprint that spans multiple public clouds, on-premises datacenters, and industrial OT facilities, you know the pain of getting or documenting a clear end-to-end picture of your entire environment.

Along the way, I experimented, failed, and learned a lot. But one recurring headache kept coming back: How do we get a clean, point-in-time snapshot of all our resources and their relationships, and then track how they change over time?

Usually, the answer is to either build bespoke, fragile API integrations for every single vendor tool, or rely on the tribal knowledge of colleagues (which is rarely written down and vanishes the moment they change jobs).

OSIRIS JSON is my attempt to solve this. It defines a vendor-neutral, open JSON interchange schema for infrastructure topology.

Rather than forcing every monitoring tool, CMDB, or visualization engine to implement vendor-specific parsers, OSIRIS separates the responsibilities:

1. Producers translate source data (like AWS APIs, VMware clusters, or OT sensors) into standard OSIRIS JSON files.
2. Consumers ingest and process these structured documents.

In this first release, OSIRIS is intentionally a static snapshot format. It describes what exists and how it relates at a specific second, leaving plenty of room for future dynamic updates.

• Specification Website: osirisjson.org
• GitHub Organization: github.com/osirisjson