OSIRIS JSON

The OSIRIS JSON manifesto

A system you cannot describe on architecture and operational documents with a clear, end-to-end topology is a system you cannot fully understand.

A system you cannot understand is harder to protect, hide single point of failures, is stressful to operate, and superficial to audit. Most, if not all of the time, handing it over happens completely in the shadows. It is often accompanied by the classic phrase, handover complete, while later the reality looks like a completely different movie.

We all know the high cost of tribal knowledge. We move or are forced to drive fast. There is rarely time to document properly, and even less time to create meaningful infrastructure topologies that reflect reality. The situation worsens when key people leave without doing a proper handover, and right in that moment problems rise from the abyss. Suddenly, we face a massive information gap.

We firmly believe that infrastructure knowledge MUST NOT live exclusively in people’s heads, hidden behind vendor portals, locked in proprietary software, poorly and superficially described in architecture or operating documents or sketched on outdated diagrams drawn in closed, proprietary formats.

We also believe that your infrastructure data is your undeniable property. No matter which vendor you use, which platform you deploy on, or which protocols you run, that data exists only because you or somebody else created it from scratch.

We firmly reject the artificial taxation of our own systemsdat. For too long, the industry has normalized a model where proprietary platforms shadow your infrastructure landscape behind proprietary language, formats or software solutions, and external consultancies charge exorbitant fees simply to untangle and grant you access to the data you already own. You SHOULD never have to pay a toll to see the reality of your own environments.

Getting visibility end-to-end into your infrastructure data MUST NOT be a premium feature; it is a fundamental right.

The problem of fragmentation

OSIRIS JSON exists because infrastructure visibility is fragmented by default. While operational technology (OT) is sometimes more static and mature, IT platforms are historically but mostly nowaday with AI wave under a chaotic evolution.

Giant hyperscalers, traditional hosting providers, and manufacturers of on-premise hardware all describe their worlds differently. Even when they adopt a format like JSON, there is no guarantee of a true unified format within the schema. Each vendor has its own APIs, models, CLI functions and assumptions. Engineering teams spend an incredible amount of effort translating between them often relying on fragile scripts, manual diagrams, and documentation that begins to decay the moment it is written.

We believe infrastructure communities need a common solid language to describe what exists and how it is connected end-to-end.

The specification

OSIRIS JSON is an open, vendor-neutral interchange format for infrastructure resource snapshots. It describes resources, metadata, topology relationships, groups, and provider provenance in a portable document written in JSON.

It is designed so that OSIRIS Producers can translate vendor-specific language into a standard document that can instantly be used for several use cases like automate topology diagrams creations and update, automate architectural or audit documents, CMDB workflows, drift validation by checking multiple OSIRIS documents, or strictly controlled AI context if and when your decide to give AI access to OSIRIS documents.

This separation matters. Every visualization tool SHOULD NOT need to implement every cloud API or create software integrations from scratch. Every documentation workflow SHOULD NOT depend on a proprietary AI platforms, agents or MCP solutions just to understand the infrastructure you already owns. OSIRIS is aimed to reduce this effort and lets communities build useful tools on an open shared foundations.

Principles

  1. Infrastructure knowledge belongs to you. No matter if you are alone or in team, you MUST be able to export, inspect, version, and interpret your own infrastructure data without pay any fee.

  2. One snapshot, many uses. A single OSIRIS JSON document MUST support different use cases such automated infrastructure topology diagrams, automated infrastructure documentation and reporting, in-depth audits report, inventory workflows, validation, time based diff and infrastructure drift identification, AI and MCP integration.

  3. Producers translate, consumers reuse. OSIRIS JSON Producers handle vendor-specific complexity. OSIRIS JSON Consumers read the OSIRIS document and generate the expected outputs.

  4. Vendor-neutral by design. OSIRIS JSON describes infrastructure across any vendor device or platform without favoring anyone.

  5. Simple scope, durable value. OSIRIS JSON is a static point-in-time interchange format, not a live control plane or a solution that tries to do a bit of everything. A clear boundary keeps the specification practical and easily implementable.

  6. Automation first. AI if needed. Reliable high quality documentation starts with deterministic, reproducible data generated by the OSIRIS JSON producers following a traditional automated process under your full control. AI, agents and advanced reasoning are useful only when grounded in a clean baseline, since the generated OSIRIS JSON document is yours you are the sole one who decide what to do with it freely.

  7. Open collaboration over hidden translation. Specification, Core schema, examples and source code available on GitHub making the OSIRIS JSON ecosystem transparent to understand and easy to adopt, no generated data or code is hidden.

  8. Generated data is your real data in open format OSIRIS JSON Producers connect to your infrastructure and generate the OSIRIS JSON document without altering any part of your data, the document is accessible and easy to read.

  9. Privacy first and complete freedom OSIRIS JSON was designed and created to work exclusively under your control without any dependencies, any license or any restrictions. You simply access what you already access with your account. Under companies organizations there could be some limitations for RBAC roles that you may have for which we suggest to align with your team before executing OSIRIS freely.

  10. Secure by design OSIRIS JSON Producers automatically redact documents to strip out sensitive data during generation.

Community

OSIRIS JSON will grow only if people use it, question it, test it, and improve it. We invite every professional as well as vendors to review the specification, build producers with consumers, publish examples, improve documentation, and help shape a practical open specification format that finally allow everyone to clearly understand end-to-end an infrastructure in total freedom.

If you share this goal, reach us and let us know how we can help.