OSIRIS JSON

The OSIRIS JSON 2026 Roadmap

OSIRIS JSON is an open specification and static snapshot format for describing infrastructure resources, metadata, and topology relationships at a point in time.

The 2026 roadmap focuses on three practical goals:

  • stabilize the v1.0 specification and documentation
  • ship usable validation and developer tooling
  • grow producer coverage across major infrastructure environments
  • ship first release of consumers creating draw.io topologies, markdown documents, reports and diff view from OSIRIS JSON documents

This roadmap is directional. Dates may change as implementation work, community feedback, and security or compatibility concerns require.

Guiding priorities

Specification first

OSIRIS JSON SHOULD remain a stable open-specification format. Changes to the specification SHOULD preserve compatibility within the v1.x line wherever possible and follow the versioning and deprecation rules defined by the project.

Producers and consumers stay separate

Producers translate vendor-specific infrastructure data into OSIRIS JSON. Consumers read OSIRIS JSON for validation, documentation, diagrams, inventory workflows, audits, diffing, and integration. This separation keeps tools simpler and reduces duplicated work. This difference also gives you the total freedom of choice.

Practical coverage before breadth

The project prioritizes useful support for core infrastructure domains before expanding too widely: cloud, network, compute, storage, virtualization, hosting, on-premise environments, and selected OT contexts where topology visibility matters.

Open interoperability

OSIRIS JSON should help independent tools work together through a shared schema, clear examples, validation guidance, and predictable extension rules.

2026 Delivery plan

Completed Foundation MVP

The first milestone established the public foundation for the project:

  • OSIRIS JSON v1.0 specification
  • public website and documentation structure
  • JSON Schema reference and validation guidance
  • example OSIRIS documents for IT and OT-oriented scenarios
  • core community material, including governance, maintainers, conduct, and contribution guidance

This milestone made OSIRIS usable as a published interchange specification for documentation, diagramming, inventory, and audit evidence workflows.

Completed Q1-Q2 2026

The second milestone focused on initial tooling and first producer implementations:

  • initial OSIRIS Toolbox work, including CLI, VS Code extension, validators, and SDK baseline
  • native, zero-dependency CLI and producer binaries for Windows, macOS, and Linux, so end users do not need a local Go runtime
  • macOS distribution through Homebrew for simpler installation and updates
  • validation workflows for schema-level and semantic checks
  • initial Cisco producer support for network-oriented OSIRIS JSON output
  • initial Microsoft Azure producer support for Azure subscriptions and resources
  • early feedback loops between producer output, schema validation, and documentation examples

This phase tested the producer and consumer model against real infrastructure sources, hardened the v1.0 workflow, and established a lightweight distribution model that respects user infrastructure environments.

In Progress Q3 2026

The current milestone focuses on covering major Hyperscalers improving existing one and continue the development of on-premise producers:

  • AWS producer for OSIRIS JSON snapshots from AWS inventory and topology sources
  • Google Cloud producer for OSIRIS JSON snapshots from GCP inventory and topology sources
  • Proxmox VE producer development for virtualization and on-premise infrastructure snapshots
  • HPE Aruba Central producer development for managed network infrastructure snapshots
  • improvements to validation reports and developer ergonomics
  • practical diff and comparison workflows based on stable resource identifiers and explicit relationships
  • additional examples derived from producer-generated snapshots

The goal is to make cross-cloud infrastructure snapshots more consistent and easier to validate, review, compare, and document.

Q4 2026 Planned

The final 2026 milestone expands producer coverage into additional network, on-premise, and edge-facing environments:

  • OSIRIS JSON consumer first MVP release. Creating automatically draw.io topologies, markdown documents, reports and diff view from OSIRIS JSON documents
  • Cloudflare producer for relevant Cloudflare inventory and topology data
  • reference snapshots and examples based on real producer outputs
  • compatibility checks for producer output across v1.x tooling

Continuous work

Interoperability hardening

Throughout 2026, the project will continue to improve compatibility and validation:

  • maintain compatibility tests across v1.x releases
  • keep v1.0 documents valid within the v1.x line wherever possible
  • document deprecations clearly before removal
  • improve migration guidance when behavior changes
  • verify that consumers tolerate unknown fields, custom types, and extension namespaces according to the specification

Extension guidance

OSIRIS supports extensions, but they SHOULD NOT become a substitute for common vocabulary. The project will continue to document:

  • namespace guidance for vendor, organization, and experimental extensions
  • when to use standard resource types and fields
  • when an extension is appropriate
  • how producers should preserve provider-specific provenance without breaking interoperability

Examples and documentation

Examples are part of the specification experience. The project will keep improving:

  • small examples for learning the model
  • realistic reference snapshots for producer and consumer testing
  • validation examples that show common mistakes
  • documentation for producers, consumers, SDK usage, and CLI workflows

Security and quality

Producer and tooling work should maintain a conservative security posture:

  • private vulnerability reporting and coordinated disclosure
  • dependency and static analysis monitoring
  • credential-safe producer behavior
  • review of networking, parsing, authentication, and release changes
  • reproducible validation steps where practical

How to influence the roadmap

The roadmap should be shaped by real use cases and working examples. Useful proposals include:

  • a clear infrastructure scenario OSIRIS should represent
  • a minimal OSIRIS JSON example or producer output sample
  • an explanation of why existing types, fields, or extension points are insufficient
  • validation expectations or consumer behavior that the project should support
  • implementation notes for a producer, consumer, SDK feature, or documentation improvement

Roadmap discussions are welcome in the project community:

https://github.com/osirisjson/osiris/discussions/categories/roadmap

Roadmap updates

This roadmap will be revised as milestones are completed, producer work matures, and community priorities become clearer.