SolarWinds Avior IT Goals Begin With Guided Onboarding

SolarWinds’ October 14, 2026 announcement from Austin, Texas, introduced Avior as a standalone system that coordinates specialized AI agents around defined IT outcomes. Access began through guided onboarding, with network operations as the initial focus. For an eligible customer, the practical question is which goal Avior can pursue through a supported connection and which actions the IT team will permit.

In Network World’s launch report, SolarWinds interim CEO and chief product officer Cullen Childress said, “Everybody has a different level of conservatism,” while describing customers’ control over agent authority. The network engineering agent is the initial offering available through guided onboarding. That status gives participating teams a starting point for evaluation; it does not make every described goal or integration available to every account.

What an IT goal asks Avior to do

A goal gives Avior an operational target to pursue over time. The team defines its scope, cadence, data sources, allowed actions and approval requirements. Role-based agents can gather evidence, investigate a condition, test a possible explanation, recommend or take a permitted action, and then check whether the condition improved. The work returns to an operator when it needs human judgment.

Consider alert noise, one of the announced network goals. Correlating related events into an actionable incident gives an engineer a problem to investigate rather than a queue of separate alerts. Other described outcomes include checking devices against a compliance baseline, finding configuration drift, keeping configuration backups current and identifying devices that fall outside backup coverage. Capacity, cost and asset lifecycle work are also among the examples. These are descriptions of intended outcomes, while the goals validated for an early access customer depend on that customer’s connected environment.

The continuing measurement is what makes the goal more than a request for an answer. Avior is designed to establish a baseline, work within the configured limits, measure the environment again and report whether the target was achieved, improved, unchanged or degraded. A recommendation can be an outcome of that process even when the system has no authority to make the proposed change itself.

Capability and availability at the opening of access

The SolarWinds product explainer describes Avior as a separate cloud SaaS application designed for self-hosted and cloud deployments. Its initial integration focuses on SolarWinds Observability Self-Hosted and the network engineer role. That distinction between overall design and the initial supported connection governs what a customer can evaluate now:

Deployment model: A customer can retain its self-hosted observability deployment. Avior runs separately in the cloud; using the supported connection does not require a migration from the self-hosted product.
Initial connection: Platform Connect is required to connect SolarWinds Observability Self-Hosted to Avior. The system works through supported product connections rather than signing in directly to arbitrary machines.
Network goals: The initial goals are curated and validated against the customer’s environment. Alert correlation, incident investigation, configuration and compliance drift, and backup coverage illustrate the work being pursued; the examples are not a universal entitlement list.
Human handoff: A team can start with read-only investigation, recommendations or a dry run. Work stops for a person when risk, permissions, missing capability or uncertainty require judgment.
Customer entry: Early access is intended for eligible Advanced, Premier and Essentials customers with Platform Connect enabled, subject to customer program and entitlement decisions. Guided onboarding establishes the starting goal and its controls.
Commercial scope: Supported goals, integrations, licensing, pricing and entitlements can vary by release, deployment model and program. The launch information provides no fixed public Avior price.

The distinction matters most for hybrid estates. Support for self-hosted and cloud environments describes the application’s intended reach, while the connected product and validated goal define the opening evaluation. A team with several monitoring or workflow products should not assume that connecting one supported environment activates the same work across the rest of its estate.

Where autonomous work stops

Avior’s authority can be set per goal. Actions inherit the permissions of the connected SolarWinds account, and unknown or unclassified tools are held for approval. Higher-risk actions require explicit human approval. An IT team can therefore allow an agent to investigate or recommend a response while keeping a production configuration change behind a separate decision.

Visibility is part of that control. Avior is designed to show observations, decisions, actions and results, although activity and audit views depend on release capabilities. The announcement describes automated rollback support, while the product guidance makes clear that rollback or a compensating action depends on the workflow. For a change-bearing goal, the relevant boundary is the recovery behavior available for that particular action, not a general promise that every change can be reversed.

Data access also follows the connected user’s permissions. The announced safeguards include masking customer data and limiting agents to the tools needed for their assigned work. Those controls narrow what an agent can see and do, but the permitted scope still has to be set for the customer’s goal during onboarding.

The next concrete decision for a prospective customer is the goal, connection and level of authority established in its guided evaluation, alongside the program’s licensing terms. Those details determine whether Avior can move from gathering network evidence to taking an approved action in that customer’s environment.