Tia Zanella's profile on Product Hunt

About

I started writing OSIRIS in 2025 after years of designing and helping maintain heterogeneous infrastructure stacks: public cloud providers and hyperscalers, on-prem data centers and complex environments where IT and facility OT systems coexist. Along the way I experimented, failed and learned a lot, but one recurring problem kept showing up: getting a clear, point-in-time view of resources and their relationships and then comparing snapshots over time without rebuilding bespoke integrations for every tool and vendor, or relying on tribal colleagues knowledge that most of the time isn’t consistently documented.

Links

OSIRIS JSON

Badges

Tastemaker

Gone streaking

Gone streaking 5

Forums

•

21d ago

OSIRIS JSON - Open Standard for Infrastructure Resource Interchange Schema

OSIRIS (Open Standard for Infrastructure Resource Interchange Schema) defines a vendor-neutral JSON format for describing infrastructure resources, their properties and their topological relationships across heterogeneous IT and OT environments. OSIRIS is a neutral interchange schema: it is designed to normalize and standardize infrastructure data exports from diverse domains and enable portable consumption by tools without requiring consumers to develop and maintain vendor-specific parsers.

•

1mo ago

pingtrace - terminal-first CLI designed for rapid troubleshooting

pingtrace is a terminal-first CLI designed for rapid network troubleshooting, combining ping and traceroute with a clear, intuitive output enriched by DNS and ipinfo.io data.

p/net-commander

•

2mo ago

What’s your most annoying context-switch during troubleshooting sessions?

If you spend your day bouncing between terminal tabs, websites lookups most of them filled with annoying ads, spreadsheets files spreading like forest and half-written incident notes, you know the real cost: missed details and slower RCA.

What s your single most annoying context-switch during troubleshooting?

e.g. copy/paste config snippets into chats/group conversations/docs
e.g. jumping from CLI to websites like what's the ip or PeeringDB/IANA than jumpt to tickets then back to CLI than maybe chats with colleagues
e.g. saving ping/traceroute outputs and screenshots for the incident report