We build network management, AV control, and venue automation tooling for sports, entertainment, and enterprise campus networks.
This page tracks our public, open-source components — the pieces of our stack we've extracted, hardened, and published for the broader networking community.
Nothing here yet — projects graduate from "research-grade" once they ship to a production customer and the API stabilizes.
| Project | What it is | Status |
|---|---|---|
| mediacast-netcatalog | Vendor command catalog + version matcher + protocol probe for multi-vendor network switches (Cisco IOS-XE, Cisco NX-OS, Aruba AOS-CX, Juniper Junos, Arista EOS, HPE ProCurve, Cisco Meraki MS). Rust core + Python bindings. | v0.1 — scaffold + research data; API unstable. Catalog YAML is research-grade and citation-backed. First consumer: NetCaster. |
| mediacast-displaycatalog | Vendor command catalog + version matcher + protocol probe for IP-managed displays (Samsung MDC, LG webOS, Sony Bravia, NEC NaViSet, PJLink projectors). Same architectural shape as mediacast-netcatalog, different device class. Rust core + Python bindings. |
v0.1 — scaffold; catalog data pending doc-crawl. API unstable. First consumer: Mediacast Platform / MediaControl. |
- 🟢 Stable — published to crates.io / PyPI, semver-respected, accepting external PRs, used by at least one production deployment outside Mediacast.
- 🟡 Research-grade / early access — usable but the API may break. We'll do our best to coordinate; pinning a version is reasonable.
- 🔴 Archived — no longer maintained. Try the linked alternative.
Most multi-vendor network tooling re-invents the same primitives — version matchers, protocol probes, vendor command catalogs — inside closed product codebases, badly. Every operator hits the same Aruba family-prefix gotcha, the same NX-OS-vs-IOS DHCP-relay difference, the same Junos transactional-config surprise. Solving it once in the open is cheaper than each shop solving it five times in private.
We publish what we believe will benefit the wider network-automation community more than it benefits us to keep private. Our products (NetCaster and the broader Mediacast Platform) are differentiated on integration, UX, and operational discipline — not on having a slightly-better-than-yours version comparator.
Each repo has its own CONTRIBUTING.md. Common rules:
- Open an issue first for substantive changes (new vendor, schema change, breaking API). Drive-by formatting PRs aren't great use of anyone's time.
- Cite vendor docs for any catalog data — we hold ourselves to that bar.
- Dual-licensed MIT OR Apache-2.0 unless a repo notes otherwise.
- Be kind. Disagree on technical merit, not on people.
- Issues / PRs — on the individual project repos.
- Discussions — enabled per-project as the community grows; check the
repo's
Discussionstab. - Email —
oss@mediacastnet.comfor security disclosures or business-side conversations. Day-to-day technical work happens on GitHub.
Mediacast Network Solutions is a venue and AV-network specialist. Our production deployments include the Major League Baseball stadium at Yankee Stadium, NFL stadiums, corporate campuses, and entertainment venues. The OSS components on this page are battle-tested in those environments before they get extracted and published.
If you're a network operator running multi-vendor switching at scale and some of this looks useful, get in touch — we'd love to hear what's working, what isn't, and what we should publish next.