Normalized inventory for fabrics, switches, ports, hosts, and storage
Planned
All tools
Storage operations
OUTSEED SAN Manager
A developing control plane concept for making SAN inventory, relationships, change intent, and evidence easier to review.
01
Problem
Why this direction matters
Operational clarity should not depend on stitching together the story by hand.
SAN operations depend on precise relationships across hosts, fabrics, ports, zones, arrays, and volumes. Those relationships are frequently spread across device interfaces, spreadsheets, and change records, increasing the effort required to assess impact and prove what changed.
Intended audience
Built around accountable operators.
01
Storage and SAN administrators
02
Data center infrastructure teams
03
Change managers and technical reviewers
Product direction
A deliberate operating layer, not another opaque console.
The product direction is an evidence-led SAN operations workspace: model the environment clearly, prepare changes deliberately, and retain the reasoning and review trail around every action.
Planned capabilities
The working product boundary.
These are roadmap intentions, not currently available features. Scope may change as the product is validated.
Relationship and path visualization
Planned
Zoning intent review and conflict checks
Planned
Change plans with approval and rollback context
Planned
Configuration evidence and drift review
Planned
Operational reporting and audit history
Planned
Planned architecture
Boundaries before integrations.
The planned architecture keeps discovered state, operator intent, validation, and execution approval as separate concerns to reduce ambiguity around infrastructure change.
- 01
A future collection boundary for explicitly supported environments
- 02
A vendor-neutral topology and configuration model
- 03
A validation layer for relationships, policy, and proposed change
- 04
A review workspace that keeps planning distinct from execution
Current integration boundary
No switch, array, hypervisor, or orchestration connectors are currently available. The first supported boundaries will be published only after implementation and validation.
Early conversations
Help us test the problem before we claim the solution.
OUTSEED is speaking with teams whose operating constraints match this direction. Contact us to share requirements or discuss potential early access. This is an expression of interest, not enrollment in an available product or a promise of a release date.
Discuss early access