What is an OSIRIS JSON producer

an OSIRIS JSON producer generates a private snapshot of your infrastructure at a point in time without need to connect to any third-party service or AI Platforms and MCP Servers. You execute it fully under your complete control.

It connects directly from your own environment to infrastructure sources such as hyperscalers, public cloud and hosting providers, on-premise IT systems (like for example hypervisors,bare metal servers,storage,network etc.) and OT systems. It discovers inventory and topology data, normalizes proprietary informations and emits a valid OSIRIS JSON Document like OSIRIS JSON IT infrastructure example and OSIRIS JSON OT infrastructure example.

• No AI platform, MCP server or AI agent are required
• No SaaS or intermediary API are required
• No pay per use or expensive consultancy are required
• No additional software development is required
• Your infrastructure data stays under your control like your API keys and credentials to retrieve the informations and generate an OSIRIS JSON document

OSIRIS JSON producer bridge the gap between proprietary infrastructure language/format and the freedom of an open, vendor-neutral JSON format.

flowchart TB
    A["Provider/Vendor<br>AWS,Azure,GCP,Cisco,Arista,HPE<br>on-premise IT/OT resources"] <--> B["`**OSIRIS JSON Producer run under your full control**`"]
    B --> C["it generate an OSIRIS JSON document at a point-in-time of your infrastructure"]
    C --> n1["You can use the document<br>under your own control to develop"] & I["use OSIRIS JSON Consumers<br>(under development) to"]
    I --> D["create reports an<br>audit documents"] & E["create diagrams<br>Draw.io/Mermaid"] & F["generate diffs and<br>identify configuration drift"]
    n1 --> H["feed AI platforms<br>MCP, Agents"] & G["feed CMDB/IPAM/DCIM <br>workflows"] & F & E & D

What an OSIRIS JSON producers will do in detail

When you execute an OSIRIS JSON producer il will performs four steps:

Available producers

Producers are released incrementally while others are planned and will follow. If you are using a provider or vendor not currently listed in the roadmap you can open a new discussion and suggest to be considered for the OSIRIS JSON Roadmap.

Installing OSIRIS JSON Producers

see the How to Install page for more install options.

Typical workflow

For solution architects and auditors, the recommended workflow is:

1. Run the producer against your target platform with appropriate credentials.
2. Validate the output using @osirisjson/cli with the strict profile.
3. Review the snapshot as an architecture artifact store it, compare it over time, attach it to audits.

# Generate snapshot
osirisjson-producer cisco apic -h apic.example.com -u admin > snapshot.json

# Validate
npx @osirisjson/cli validate --profile strict snapshot.json

# Compare with previous snapshot
diff <(jq -S . previous.json) <(jq -S . snapshot.json)

Security

Producer source code is continuously analyzed by SonarCloud for vulnerabilities, code smells, and security hotspots. Every pull request must pass a quality gate that enforces an A security rating before it can be merged.

Additionally, producers include built-in safety guardrails:

• Secret redaction - the --safe-failure-mode flag (default: fail-closed) prevents credentials and sensitive values from leaking into the JSON output.
• Read-only access - producers never modify device configuration. All API calls and NETCONF RPCs are read-only operations.
• No persistent storage - producers do not cache credentials or store data beyond the emitted JSON file.

What to read next

• See the How to Install page for more install options.
• Browse the vendor-specific producer pages for details on installation, source systems, authentication, and output scope.
• Read the validation guide to understand how to verify producer output.
• See the IT infrastructure example and OT infrastructure example for a complete OSIRIS JSON document sample.