Roadmap

A roadmap page should show direction without reading like a changelog dump.

Keep the public roadmap focused on themes that matter to buyers: broader platform coverage, better operational visibility, deeper topology, and stronger automation. It should feel credible, not speculative.

Now / next / later

Use roadmap buckets buyers can understand at a glance.

Now

Operational visibility foundation

Agent deployment across Windows, Linux, and Raspberry Pi-style targets
Multi-site inventory, locations, and networks
Device detail, credentials, and discovery job workflows
Topology and interface relationship views
Automation run and job detail visibility

More discovery and enrichment depth across supported protocols
Expanded dashboard views for operations teams
Improved automation orchestration and action workflows
Richer alerting and monitoring context
More mature reporting around network changes and history

Later

Platform maturity and broader reach

Expanded enterprise controls and policy depth
Broader operational automation coverage
More advanced topology intelligence and relationship validation
Deeper product polish for executive and NOC views
Additional deployment and theming flexibility across the platform

Public roadmap notes

What this page should communicate.

Direction over dates

Unless dates are firm, speak in themes and priorities. Buyers want confidence more than calendar theater.

Operational maturity

Roadmap items should reinforce that NetLoom is moving toward a fuller operations platform, not just broader scanning.

Deployment confidence

Call out ongoing support for practical agent deployment targets, including server Linux and Raspberry Pi edge hardware.

Design consistency

The roadmap page should use the same dark shell and bright screenshot-style cards as the rest of the marketing site.

Keep browsing

Roadmap pages work best when they are part of a coherent story.

Use this page to support the overview and product tour, not replace them.

Get Access Back to Overview