Real-World use cases

OSIRIS JSON is a vendor-neutral JSON interchange schema for describing infrastructure resources, their properties and their topological relationships across heterogeneous IT and (where applicable) OT environments.

OSIRIS JSON is a static snapshot format: each document represents “what exists and how it relates” at a specific point in time. This makes OSIRIS JSON suitable as a stable interchange layer for diagramming, documentation, audit evidence, inventories, and integrations.

Where OSIRIS JSON fits

Optimized for scenarios where documentation and topology must be exchanged between systems and teams.

photo_camera Reliable, flexible infrastructure snapshots

Capture "what exists" and "how it relates" at a point in time.

description Documentation-ready outputs

Enable consistent inventories, technical summaries and system context.

flowsheet Diagram-friendly topology

Provide normalized relationships for automated visualization and diagram generation.

sync_alt Feeding CMDB / IPAM / DCIM workflows

Export normalized data into systems of record and asset management tools.

security Audit support

Assist evidence collection and traceability by standardizing structure and relationships.

swap_horiz Interchange between tools

Producers translate vendor formats into OSIRIS JSON; consumers read OSIRIS JSON without implementing vendor-specific parsers.

Common adoption scenarios

Automated diagramming and topology visualization

Use OSIRIS JSON as the input format for diagramming tools that need a consistent model for:

physical and logical connectivity
dependencies between services/components
hierarchical grouping (sites, rooms, zones, environments, accounts, regions, etc.)

Typical outcome: repeatable diagrams generated from snapshots, without re-implementing parsing logic for every vendor export.

Inventory normalization (CMDB / asset inventory / documentation portals)

Use OSIRIS JSON to normalize inventories from different stacks and providers into a single, comprehensible schema:

compute, network, storage, application resources
consistent identity fields and provider attribution
portable ingestion into internal tools and reporting pipelines

Typical outcome: one normalized dataset that can feed inventories and documentation systems.

Point-in-time snapshots and change tracking (diff between snapshots)

Use OSIRIS JSON snapshots as comparable artifacts:

export a snapshot “now”
export a snapshot “later”
diff the two documents to identify additions, removals, and relationship changes

Typical outcome: change tracking and topology drift visibility using plain JSON artifacts.

Audit evidence and compliance workflows

Use OSIRIS JSON as a structured evidence format for infrastructure state:

consistent capture of resources and relationships at a given time
portable artifacts that can be stored alongside audit documentation
repeatable exports across environments and vendors

Typical outcome: standardized inputs for audit evidence and control checks.

Multi-cloud and hybrid environments

Use OSIRIS JSON to represent environments that span:

multiple hyperscalers
public cloud providers
private cloud / virtualization platforms
on-premises data centers and network topologies

OSIRIS JSON enables unified reporting and visualization because snapshots share the same core schema even when sources differ.

Typical outcome: cross-domain visibility without bespoke, per-platform interchange formats.

IT/OT coexistence and boundary visibility

Where applicable, use OSIRIS JSON to include OT-adjacent resources alongside IT infrastructure:

building automation / access control / cameras / industrial endpoints
network attachment and relationships between IT and OT segments
partial data scenarios where OT exports are limited

Typical outcome: a single snapshot format that can represent IT + OT relevant topology when integration is required.