Our Spring 2026 product roadmap is built around the idea that AI network management should start with what’s actually happening on your network, not a blank prompt. Over the past six months we’ve built Auvik AI into alerting, troubleshooting, the remote terminal, and Command Runner. We’ve also added, faster fixes for servers and workstations, and a ServiceNow CMDB integration.
We walked through all of this, plus what’s coming next, in our Spring 2026 roadmap webinar. Below are the highlights; 10 updates we covered and 4 items coming next, with what each one means for your team, who on our product team presented it, and how to test it yourself.
Key takeaways:
- Auvik AI works inside the tools you already use. It runs in alerting, troubleshooting, the remote terminal, and Command Runner, using the device, topology, and syslog data Auvik already collects.
- Auvik AI suggests, and your team decides. It shows confidence scores and sources, and it doesn’t run fixes on its own.
- Next on the roadmap: AI-powered CVE monitoring, commands across multiple devices, a global collector dashboard, and process-level server monitoring.
This post is based on our Spring 2026 product roadmap update, presented by the Auvik product management team on May 27, 2026. It reflects the roadmap as presented that day. We add status notes as features move from beta to general availability, but for the latest, check our public release notes.
| What’s in this roadmap | 8 updates and 4 items coming next |
| Auvik AI | Update 1: Alert Insights and AI-assisted alert creation Update 2: Troubleshooting Assistance Update 3: Remote Terminal Assist Update 4: AI-powered device lifecycle |
| Platform updates | Update 5: Multi-vendor syslog alerting Update 6: Quick Actions and Command Assist Update 7: ServiceNow CMDB integration Update 8: Reporting, API, and device support |
| Coming next | 1: AI-powered CVE monitoring 2: Commands across multiple devices 3: Global collector dashboard 4: Process-level server monitoring |
| Also on this page | How to test each feature, and FAQs (including where each item stands today) |
Auvik AI now takes on the first steps of alert tuning and troubleshooting
Updates 1 to 4 of 8
The biggest difference between Auvik AI and pasting a question into a general chatbot is context. Auvik AI already knows the device, its vendor and model, where it sits in your topology, and what it has been logging.
Update 1: Auvik Network Management now shows which alerts are noise and how to cut them
Alert Insights compares your last 30 days of alerts to the 30 days before and shows which alerts and sites are trending up in count and duration. A Flagged Entities section surfaces devices with critical or emergency alerts that have stayed open too long, and the report calls out quick wins, such as when smart alert suppression is turned off.
The most useful piece is the alert delay analysis. Auvik AI looks at how quickly your alerts clear on their own and tells you what delay would remove a given share of the noise. As Trent Cutler, Senior Product Manager, put it, “We look at your alerts holistically and say, for example, most of these resolve within two minutes, so a two-minute alert delay would cut 50% of your alerts.” Alert delay requires V2 alerting, and Auvik AI can also build V2 alert definitions from a plain-language description, which helps if you’re still migrating off legacy alerts.
What that means for you: You get a data-backed way to reduce alert fatigue without guessing which alerts are safe to tune.
 | Presented by: Trent Cutler, Senior Product Manager Status at the webinar: Beta Status update: Alert Insights and AI-assisted alert creation became generally available on September 14, 2026, and Alert Insights expanded to the multi-site level (see the September release notes) |
Update 2: Auvik AI Troubleshooting Assistance works an alert with you, using the data Auvik already has
Open an alert and click the Auvik AI button, and Auvik hands over the alert’s context automatically: interface stats, device attributes, device type, vendor, model, network topology, and any attached syslog. Auvik AI returns likely causes with a confidence score and recommends diagnostic commands. You paste the output back in, it narrows things down, and you can attach the whole investigation to your ticket if it needs to be escalated.
Trent described why it feels different from a standalone AI tool: “we’re automatically feeding it all the data Auvik already has.” Auvik AI gives hypotheses and next steps. It doesn’t take remediation actions on its own.
What that means for you: Your team gets to a likely root cause faster, and junior technicians get a guided starting point instead of a blank screen. Learn more about AI troubleshooting in Auvik.
| Presented by: Trent Cutler, Senior Product Manager Status at the webinar: Upcoming (beta expected the following month) Status update: Entered open beta in July 2026 (July release notes) Added TrafficInsights flow data in August 2026 (August release notes) Became generally available on September 14, 2026 (September release notes) |
Update 3: Auvik Network Management now puts device-specific CLI help inside the remote terminal
Remote Terminal Assist brings Auvik AI into the terminal session. Ask how to check interface errors, validate a firmware version, or handle a common configuration task, and it suggests commands based on the make, model, and firmware of the device you’re connected to. It can interpret terminal output, and you can paste in a command to review before you run it.
Steve Chan, Principal Product Manager, explained the payoff for teams that support a mix of vendors: “Ultimately, you can complete more tasks without always going to an expert, and you may not have an expert for every vendor.”
What that means for you: Fewer syntax mistakes and less time searching vendor documentation, whether you’re a lean internal IT team or an MSP technician moving between client environments.
 | Presented by: Steve Chan, Principal Product Manager Status at the webinar: Upcoming Status update: Entered open beta in August 2026 (August release notes) Became generally available on September 14, 2026 (September release notes) |
Update 4: Auvik AI now finds end-of-sale and end-of-support dates for about 80 network vendors
Auvik AI takes your device inventory and finds published end-of-sale and end-of-support dates. It goes beyond our existing Cisco integration, covering roughly 80 network infrastructure vendors and thousands of models, and it even surfaces older Cisco devices that Cisco’s own API no longer returns. You can export the data or pull it through the V2 API.
Trent was direct about how to use it: “Because AI is going to make mistakes, and we’ve already found some examples, check the source.” Every date shows its source when you hover over it, along with a confidence score, and anything scoring below 70 is hidden. If a device is missing, the vendor may not have published dates for it, or the result fell below that threshold.
What that means for you: You can plan hardware lifecycle management and refresh budgets from one report instead of checking vendor sites model by model.
| Presented by: Trent Cutler, Senior Product Manager Status at the webinar: Open beta Status update: Entered public beta in May 2026 (May release notes) |
| Pro Tip: Auvik AI is built to be checked, so check itConfidence scores, cited sources, and a thumbs up or thumbs down on troubleshooting suggestions are there for a reason. Build a habit of verifying Auvik AI’s output before acting on a hardware refresh or a config change, and rate what you see. That feedback goes straight to our product team. |
Recent platform updates make alerting, servers, and integrations easier to manage
Updates 5 to 8 of 8
Update 5: Auvik Network Management now builds multi-vendor syslog alerts with grouped logic
V2 alerting supports grouped conditions for syslog, so a single alert can catch high-availability failovers across different vendors. You can also alert on counts, such as five events in ten minutes, set custom clear conditions, and alert on security events like authentication attempts. Native HA pair monitoring is available for Fortinet, and syslog covers vendors that aren’t natively supported yet.
What that means for you: You can alert on exactly the events that matter in your environment without waiting for native support for every vendor. See more about customizable network alerting.
| Presented by: Trent Cutler, Senior Product Manager Status at the webinar: Released Status update: Count-based clear delay added in September 2026 (September release notes) |
Update 6: Auvik Server and Endpoint Monitoring now handles common fixes in a click or a plain-language request
Quick Actions puts common remediation behind a point-and-click menu on server and workstation dashboards: start and stop services, restart systems, flush DNS, renew DHCP, and clear file system issues. Command Assist adds Auvik AI to Command Runner, so technicians can describe what they need and get the right command for that specific device. In his demo, Rob Bayley, Senior Product Manager, found and removed a saved coffee shop Wi-Fi profile in two prompts.
Rob summed up the difference: “So I don’t need to remember commands I may or may not have been trained on, open a separate tab to Google them, or type them into a ChatGPT window with no context.”
What that means for you: Routine fixes take seconds instead of a remote session, and less experienced staff can resolve more tickets on their own.
 | Presented by: Rob Bayley, Senior Product Manager Status at the webinar: Quick Actions released; Command Assist in beta Status update: Command Assist became generally available on September 14, 2026 (September release notes) |
Update 7: Auvik now syncs network devices into ServiceNow CMDB automatically
For teams that use ServiceNow CMDB as their system of record, the new integration syncs network devices from Auvik automatically. It’s available as a Service Graph Connector in the ServiceNow Store, with a guided setup. As Steve Chan put it, “it helps your team trust your configuration management database and spend more time acting on insights instead of trying to keep the data accurate.”
What that means for you: Fewer stale or missing CMDB records, and better data for audits, compliance, and incident response.
| Presented by: Steve Chan, Principal Product Manager Status at the webinar: Upcoming Status update: No public update yet. Check our release notes for the latest. |
Update 8: Smaller platform updates add reporting, API, and device support improvements
We also improved the scalability of our V2 APIs, added Power BI templates for reporting and dashboards, introduced an internal ping check on the collector, added support for Fortinet high availability pairs, and enabled FortiGate config backups via API. A new Device Inventory Report was days from release at the time of the webinar.
What that means for you: Better reporting and broader device coverage without extra tools.
 | Presented by: Glenn Gray, Vice President, Product Management Status at the webinar: Released, with the Device Inventory Report coming within days Status update: Device Inventory Report released in August 2026 (August release notes) |
You can test each released feature in a single afternoon
We’d love for you to try these out and tell us candidly what’s working and what’s not. Here’s the fastest way to do it.
Step 1: Turn things on. In Auvik’s settings page, enable server and endpoint monitoring with a toggle, then download and deploy the agent. The Auvik AI enablement setting is at the bottom of the same page and applies to all sites. Auvik AI is on by default for customers in US-based clusters, so check that setting first if your organization has an AI usage policy.
Step 2: Run one quick test per feature. Pick a single site or a small group of tagged devices so you can compare results against what your team already knows.
| Feature | Where to find it | Quick test | What good looks like |
| Alert Insights | Alerts > Alert Insights | Review Flagged Entities and the suggested alert delay | Flagged devices are ones you recognize as real problems |
| Troubleshooting Assistance | Any open alert > Auvik AI | Run it on an alert your team already solved | Its top hypothesis matches the root cause you found |
| Remote Terminal Assist | Remote terminal session | Ask how to check interface errors on an unfamiliar vendor | Commands match that device’s syntax and firmware |
| Command Assist | Server or workstation > Command Runner | Describe a task in plain language | The command is correct for that OS without a web search |
| Device lifecycle | Vendor Lifecycle view | Hover over five devices and open each source | Dates match the vendor’s published notices |
| Syslog alerting | Alerts V2 | Build one count-based syslog alert | It fires only when the threshold is met |
Step 3: Rate what you see. Use the thumbs up or thumbs down on Auvik AI’s suggestions so our product team can improve them.
Not an Auvik customer yet? Start a free trial and run the same tests on your own network, or book a demo and we’ll walk through each feature with you.
What’s next on the Auvik roadmap: vulnerability monitoring, automation, and visibility at scale
4 items coming next
Coming next 1: Auvik AI will match newly published CVEs to the devices on your network
Today, figuring out which devices a new vulnerability affects means checking multiple sites and sources by hand. Vinay Kammar, Senior Product Manager, called it “a heavily manual, fragmented process.” CVE monitoring will identify affected devices using authoritative sources such as the National Vulnerability Database and vendor advisories. We plan to deliver it in stages: reports first, then alerting, dashboards, management, and eventually remediation.
What that means for you: A shorter window between a CVE being published and your team knowing whether you’re exposed.
| Presented by: Vinay Kammar, Senior Product Manager Status at the webinar: In development, with the first release estimated three to four months out Status update: No public update yet. Check our release notes for the latest. |
Coming next 2: Auvik Network Management will run the same CLI commands across many devices at once
Steve Chan described the scenario this solves: a security policy changes, and someone has to log into each device, run the same command, and track which ones are done. “That kind of repetitive work is tedious on a normal day, and if the request is time sensitive, it adds a lot of stress to the whole experience.”
The new workflow uses job templates. Save the commands once, select target devices using the tags you already use in Auvik, run the job, and review the output in one place. Every change is recorded in the user activity audit log. This is the foundation for broader automation, including a scheduler and workflow engines, and golden configuration checks that alert when a device is missing a required setting are on our radar.
What that means for you: Faster, more consistent changes across your network, with a record of exactly what changed and when. If you’re comparing network automation tools, this is the one to watch.
| Presented by: Steve Chan, Principal Product Manager Status at the webinar: Upcoming Status update: No public update yet. Check our release notes for the latest. |
Coming next 3: A global collector dashboard will show every collector in one view
Checking collectors currently means going site by site. Vinay described the new dashboard as “a single pane of glass, providing global visibility across all your collectors.” It’s planned in four phases: a global view of the collector details you already see at the site level; health metrics such as CPU, memory, and disk, along with site, device, and interface counts; bulk actions like approve and reject; and indicators that flag collectors at risk. CPU and memory stats are easier to collect on Linux than on Windows, which usually requires elevated permissions.
What that means for you: Faster troubleshooting, better capacity planning, and fewer support tickets just to pull collector data.
| Presented by: Vinay Kammar, Senior Product Manager Status at the webinar: Upcoming, with phase one targeted for the end of July Status update: Phase 1 released in August 2026 (August release notes) |
Coming next 4: Auvik Server Monitoring will break down resource use by process
Server monitoring already shows services and their running status. The next layer lets you drill into individual processes and see how much CPU, memory, disk, and network each one is using.
What that means for you: You can find the process behind a slow server without remoting in.
| Presented by: Rob Bayley, Senior Product Manager Status at the webinar: Upcoming Status update: Released for servers and workstations in August 2026 (August release notes) |
Further out, we’re also working toward device lifecycle coverage beyond network infrastructure (phones and printers are among the most requested) and more automation built on top of multi-device commands. Our next roadmap webinar will be hosted by Val Abbott, our new Director of Product Management.
See Auvik AI on your own network before you decide
A roadmap only matters if the features hold up in your environment. Whether you run IT for one organization or manage networks for many clients, the fastest way to judge Auvik AI is to point it at alerts you’ve already solved and see whether it gets there faster than your team did.
Start a free trial to test it on your own network, or book a demo and bring the alerts and devices that give your team the most trouble.
Book an Auvik demo
See how Auvik simplifies network management in a live, guided demo.
Auvik Spring 2026 Product Roadmap FAQs
Have the items on this roadmap moved forward since the webinar?
Most have. We try to keep this page updated, but for the latest status on everything, see our release notes.
- As of September 30, 2026, five Auvik AI features became generally available on September 14: Alert Insights, AI-assisted alert creation, Troubleshooting Assistance, Remote Terminal Assist, and Command Assist (September release notes).
- The Device Inventory Report, Collector Dashboard phase 1, and process monitoring were released in August (August release notes).
- Troubleshooting Assistance entered open beta in July (July release notes), and AI-powered device lifecycle entered public beta in May (May release notes) and was still in beta in public release notes as of this update.
- CVE monitoring and commands across multiple devices haven’t appeared in public release notes yet.
Is Auvik AI turned on by default, and can we turn it off?
Auvik AI is enabled by default for customers in US-based clusters. Features that use customer data can be turned on or off globally from the enablement setting at the bottom of Auvik’s settings page. If your organization has an AI usage or data handling policy, review that setting before your team starts testing.
Will Auvik AI make changes to our devices on its own?
No. Troubleshooting Assistance gives hypotheses and recommended next steps but doesn’t perform remediation. Remote Terminal Assist and Command Assist suggest commands that a person reviews and runs. Multi-device command jobs are run by a user and recorded in the activity audit log.
What happens when Auvik AI gets something wrong?
We expect it to happen sometimes and built ways to catch it. Lifecycle results show their sources and confidence scores, and anything below a score of 70 is hidden. You can rate troubleshooting suggestions so our product team can improve them. Treat Auvik AI’s output as a strong starting point and verify it before acting on anything high-stakes.
Do we need to migrate legacy alerts to use the new alerting features?
For some of them, yes. Alert delay recommendations from Alert Insights only apply to V2 alerts, and the grouped syslog logic is part of V2 alerting. Auvik AI can help recreate legacy alerts as V2 alerts from a plain-language description.
Why doesn’t every device appear in the lifecycle report?
A device may be missing because its vendor hasn’t published end-of-sale or end-of-support dates, because it’s still actively sold, or because the result fell below the confidence threshold. Coverage is currently limited to network infrastructure like switches, routers, firewalls, and access points.
Do Quick Actions and Command Assist need anything installed on the device?
Yes. Server and workstation features rely on the Auvik agent. Enable server and endpoint monitoring in Auvik’s settings page, then download and deploy the agent to the machines you want to manage.
Does the ServiceNow CMDB integration require custom development?
No. It’s available as a Service Graph Connector in the ServiceNow Store. Search for the Service Graph Connector for Auvik, install it, and follow the guided setup.
Can we test these features without changing anything in production?
Most of them, yes. Alert Insights, Troubleshooting Assistance, and device lifecycle are read-only views or recommendations. For anything that runs commands, start with a single tagged test device. If you’re not a customer yet, a free trial lets you run the same tests on your own network.
