OSIRIS JSON is an open, vendor-neutral specification for describing infrastructure resources, metadata, groups, and topological relationships across hyperscalers, cloud and hosting platforms, on-premises IT, and selected OT environments.

OSIRIS JSON Producers run locally on your workstation or server and generate private, portable, point-in-time snapshots of your infrastructure under your control. A single OSIRIS JSON document can support offline audits, topology diagrams, snapshot comparison and drift analysis, CMDB/IPAM/DCIM workflows, and governed AI or MCP context without granting third-party platforms or tools direct access to your infrastructure.

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 believe that 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.

We also believe in 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.

Read the full manifesto

flowchart TD
    subgraph VP ["Vendor / Platform"]
        A["Hyperscalers, Cloud & Hosting Providers"]
        B["On-Premises<br/>IT and OT"]
    end

    subgraph SP ["The OSIRIS JSON Specification"]
        S["The autoritative</br>Source of Truth for</br>Specification and JSON Core Schema"]
    end

    subgraph PR ["The OSIRIS JSON Producers"]
        P["Discover, Normalize, Redact, Emit"]
        J["OSIRIS JSON Document<br/>Portable point-in-time infrastructure snapshot"]
    end

    subgraph VA ["The OSIRIS JSON Toolbox"]
        V["Validation toolbox<br/>Three-level validation"]
    end

    subgraph OC ["The OSIRIS JSON Consumers"]
        C["Read the OSRIS JSON file"]
        AD["Architecture documentation reports"]
        AU["Audit reports"]
        DF["Snapshot diff view"]
        TP["Automatic topology<br/>generation and updates"]
    end

    subgraph UC ["Under your full control"]
        U["One OSIRIS JSON file multiple use-cases"]
        M["CMDB / IPAM / DCIM Workflows"]
        AI["AI platforms, agents and MCP servers"]
        X["Custom analytics </br>and Third-Party tools"]
    end

    A <-->|"Discovered by"| P
    B <-->|"Discovered by"| P

    S -. "Defines the format" .-> J
    S -. "Guides implementation" .-> P

    P -->|"Generates"| J

    J -->|"Validated by"| V

    J -->|"Consumed by"| C
    C -->|"Generates"| AD
    C -->|"Generates"| AU
    C -->|"Generates"| DF
    C -->|"Generates"| TP

    J --> U
    U --> M
    U --> AI
    U --> X

    style VP fill:transparent,stroke:#555,stroke-width:1px,color:inherit
    style SP fill:transparent,stroke:#555,stroke-width:1px,color:inherit
    style PR fill:transparent,stroke:#555,stroke-width:1px,color:inherit
    style VA fill:transparent,stroke:#555,stroke-width:1px,color:inherit
    style OC fill:transparent,stroke:#555,stroke-width:1px,color:inherit
    style UC fill:transparent,stroke:#555,stroke-width:1px,color:inherit

If you are new to OSIRIS JSON, begin with the core documentation and explore practical examples:

• Welcome
• OSIRIS JSON Use cases
• Getting Started with The OSIRIS JSON Producer
• The OSIRIS JSON Format Specification
• The OSIRIS JSON Core Schema v1.0
• IT Infrastructure Examples
• OT Infrastructure Examples

OSIRIS JSON is developed in public. Contributions of any size are warmly welcomed.

Review the Community & Contribution Guide to get started.

See the LICENSE or LICENSE-CODE file in each repository. Each repo may use different open licenses.