Real-World use cases

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

Where OSIRIS fits

account_tree Topology and relationships

Represent connectivity, dependencies, containment and grouping explicitly, so consumers can build consistent topology views across domains.

swap_horiz Interchange between tools

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

Common adoption scenarios

1 Automated diagramming and topology visualization

Use OSIRIS 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.

2 Inventory normalization (CMDB / asset inventory / documentation portals)

Use OSIRIS 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.

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

Use OSIRIS 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.

4 Audit evidence and compliance workflows

Use OSIRIS 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.

5 Multi-cloud and hybrid environments

Use OSIRIS to represent environments that span:

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

OSIRIS 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.

6 IT/OT coexistence and boundary visibility

Where applicable, use OSIRIS 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.