Question 1

How do I get an invitation to ARIA?

Accepted Answer

Access is invite-only during this phase. Reach out through your Arista account team or a workspace admin who can issue you a seat. Existing admins can invite teammates from the workspace settings.

Question 2

Which vendors and platforms does ARIA support?

Accepted Answer

Output is optimized for Arista EOS and CloudVision, including EVPN-VXLAN, MLAG, MSS, and AVD-aligned data models. ARIA can also parse legacy Cisco (NX-OS, IOS) and Juniper Junos configurations to support brownfield migrations.

Question 3

What artifacts and formats does ARIA generate?

Accepted Answer

HLDs and LLDs as Markdown and PDF, EOS configuration snippets, AVD-style YAML variables, Jinja2 templates, Terraform and Ansible scaffolding, validation playbooks, and step-by-step MOPs with rollback triggers.

Question 4

How is my network and configuration data handled?

Accepted Answer

Session data is encrypted in transit and at rest, scoped per workspace, and never used to train shared models. Sensitive identifiers can be redacted before generation, and exported artifacts stay under your control.

Question 5

Can ARIA plug into our NetDevOps pipeline?

Accepted Answer

Yes. Generated artifacts are pipeline-ready — commit YAML vars and Jinja templates into Git, drive CloudVision Studios from the same intent, and run the produced validation playbooks against staging fabrics before cutover.

Question 6

How does pricing work?

Accepted Answer

Workspaces are issued under invite during the preview. Pricing for production usage is per-seat with an enterprise option for unlimited fabrics and SSO — talk to your account contact for current terms.