AVRIA Vault

Your AV projects,
organized.

Vault is the project workspace for AV teams. Every project has its own context, its own agent team, and its own history that persists across the lifetime of the work.

Vault · 14 active projects
Your workspace
BR Executive boardroom · Building 2 Updated 14 min ago HENRY · ELENA Active
CL Riverside Univ · Lecture Hall 204 Updated 2 hr ago HENRY Active
AU Memorial Center · 320-seat auditorium Updated yesterday HENRY · ELENA Draft bid
CR Federal Courthouse · Courtroom A Updated 3 days ago ELENA Bid pending
RT First Methodist · Sanctuary refit Closed 2 weeks ago HENRY Archived

A home for every project.

Vault is where your AV projects live. Each project is a self-contained workspace with its own scope, its own bill of materials, its own conversation history with the agents, and its own document trail.

You don't start over every time. You don't dig through email for the spec sheet you sent in March. You don't ask the new hire to relearn the room from scratch. Vault remembers.

  • Project scope · room type, capacity, brief, RFP attachments
  • Bill of materials · every version, every change, every reason
  • Conversation history · every brief-to-bid pass with the agents
  • Documents · spec sheets, drawings, RFPs, manufacturer cuts
  • Decisions · why this SKU, why this substitution, why this clause
Project context
Executive boardroom · Building 2
Room Executive boardroom · 24 seats · 28 × 18 ft
Brief Dual 85" displays, ceiling mics for VC, distributed ceiling audio. Budget ~$180k.
Status Bid draftedStandards-cited
Team Henry · Elena · 3 collaborators
History 14 conversations · 3 BoM revisions · 6 documents
Project team · Executive boardroom
5 seats
JB
Jeff Barnes
Senior AV Designer
Owner
MR
Maria Reyes
Project Manager
Edit
DT
Daniel Tan
Lead Technician
Edit
H
Henry
AV Designer · Avria agent
Agent
E
Elena
Bid Estimator · Avria agent
Agent

Your people and your agents, on the same project.

Each project has a seat list. Your designers, project managers, and technicians get scoped access. The agents (Henry, Elena, and the rest of the roster) join the project too. Same context, same history, same decisions.

The agents adapt to the project. Henry knows this is a 24-seat boardroom with brand-locks on displays. Elena knows the bid is under a no-substitutions clause. They don't forget when you close the laptop.

  • Role-based access · owner, edit, view, agent
  • Org-scoped · projects belong to your team, not to individuals
  • Activity log · who edited what, when, and why
  • Single-tenant boundary · your projects never bleed into another integrator's

Memory that survives the meeting.

When Henry decides on the Chief LTM1U tilt mount over the LSM1U static twin, he writes down why, and that reasoning stays attached to the BoM row forever. When Elena flags a brand-lock on row 4, the clause reference travels with the row through every substitution request that follows.

Decisions don't get lost. When you reopen a project six months later, you see not just the system you specified. You see why each spec is the way it is.

  • Decision trail · why each SKU, who chose it, what was rejected
  • BoM versioning · every revision saved, every reason captured
  • Citation history · standards cited on each row at the moment of decision
  • Substitution log · brand-lock holds + accepted swaps + clause references
BoM revision · v3
Row 4 · Display mount
Current Chief LTM1U · large-display tilt mount
Why Display center sits 17" above seated eye height at the front row. Tilt aligns the panel to the seated line of sight, keeping vertical viewing comfortable across the audience per ANSI/AVIXA V202.01.
Rejected Chief LSM1U (static) · projects the image plane perpendicular to floor, leaving the front-row viewer with a degraded off-axis vertical view
Author Henry · 14 days ago
Edits 3 revisions · all preserved

The agents read everything you put in.

Drop a 1,000-page bid spec, every drawing, the BoM, the schedule. Ask a question. The same six agents you already work with answer it, cited to the page.

"What bulk cable types are approved on this project?" Elena cites the cable types, the page number, and the exact section from the bid spec.

"What equipment is in conference room 4B?" The agents analyze the drawing flows, return the equipment list, and link to the drawing pages where each device appears.

The Vault chat is the same agent team. Henry, Elena, Sophia, Anthony, Teresa, David. Project-scoped versions of themselves, grounded in everything the project contains.

  • Bid spec Q&A · cite cable types, brand-lock clauses, substitution rules, bond requirements by page and section
  • Drawing Q&A · query equipment lists per room, signal-flow paths, mount locations, cable runs
  • BoM Q&A · "why is this DSP in the rack?" returns the decision-trail with the AVIXA citation and the rejected alternatives
  • Schedule Q&A · "what's the install date for Phase 2?" pulls from the project's milestone log
  • Cross-document reasoning · ask a question that spans the bid spec + the drawings + the BoM and the agents synthesize across all three
Vault chat · Building 2 boardroom
Ask anything
You What bulk cable types are approved on this project?
Elena Three approved per the bid spec: Cat6A plenum (West Penn 4246F or equivalent), 16/4 audio (West Penn 25226B), 14/4 speaker (West Penn 226B). Source: Bid Spec §27 05 26 · pp. 14–15
You What equipment is in conference room 4B?
Sophia Per flow drawing E-204: 2× Sony FW-85BZ40L on Chief LTM1U mounts, 2× Shure MXA920 ceiling arrays, QSC Q-SYS Core 110f, 6× QSC AC-C6T ceiling speakers, Netgear M4250-10G2XF-PoE+. Source: Drawing E-204 · sheet 3 of 8
Catalog update
Today · 2:02 PM
Update Shure MXA920 · firmware baseline updated to 2.6.4
Applies to 12 active projects across your Vault
Action Auto-flagged on each project's BoM with revision note. No silent changes. You confirm before any update lands.
Standards AVIXA A102.01Dante

Learn once, apply across every project.

When the catalog gets a new rule, when a SKU goes end-of-life, when a manufacturer ships a firmware update, Vault checks every active project and surfaces the change where it matters.

Nothing changes silently. You confirm before any update touches a live BoM. The catalog is shared infrastructure; your decisions are yours.

  • EOL detection · flagged before the install date
  • Firmware baselines · tracked per project, updated with consent
  • Standards updates · new AVIXA / NEC / ADA / FAR clauses propagate
  • Rule engine evolution · new engineering checks re-run on existing BoMs

Request early access.

Avria is coming soon. Join the early-access list to get a personal walkthrough of Vault and the agent team.

We'll only email you about Avria. No ads, no spam.

Book a demo at InfoComm 2026 · Las Vegas · June 15–19