APEX, the AV operations platform for in-house teams and MSPs.

1. The eight-category problem

Modern AV operations live across at least eight distinct software categories: project management (Asana, Smartsheet), device monitoring (Crestron XiO, Cisco Control Hub, Logitech Sync), field dispatch (ServiceTitan, Excel), partner management (a spreadsheet of COI expiration dates), CMDB (the IT team's spreadsheet of MAC addresses and IP plans), compliance tracking (insurance, certifications, contractor licenses), service catalog and ticketing (ServiceNow, Jira, an inbox), and executive reporting (PowerBI rolled up once a quarter from all of the above).

Each tool is good at its own category. None of them know about the others. A partner's onsite visit lives in three systems with three IDs. A Cisco room reads healthy in Control Hub while its support contract expired last week, in a procurement spreadsheet the engineering team can't see. The friction scales with the tool count, and AV teams are usually carrying eight or more.

For AV operations specifically, one platform can serve all eight categories if it's built around the primitives they share: rooms, devices, partners, licenses, and the visits and discussions that move work through them. You can configure Asana or ServiceNow to approximate this, but the configuring is the cost. Every team rebuilds the same primitives their own way, and the data never connects across them.

2. Two ways APEX gets used

APEX supports two buyer modes equally. The data model handles both natively, so the platform doesn't care which one you are.

One integrator can run both modes at once: Mode A for their own office's AV (their own equipment, their own room health) and Mode B for the ten client tenants they service. The same lattice handles both, so the platform never has to tell them apart.

3. One platform, many clients, no data bleed

The payoff for this whole section: a partner serves a dozen clients from one login, and each client's data stays walled off from the rest. APEX is a single-deployment multi-tenant SaaS, not a per-customer container. Every row in every table carries a tenant_id column. Every query reads it from the JWT and filters through the requireTenant middleware. That filtering happens at the query layer, not the application layer, so a route that forgets to filter fails closed.

What sets AV operations apart from a generic multi-tenant SaaS is the partner lattice. Partners cross tenant boundaries with one stable identity, while their relationships (credentials, projects, licenses, visits) stay tenant-scoped. A partner organization has a UUID identity and one row in vendors per tenant it's in, each stamped with the same organization id. The partner sees all their clients in the client switcher; each client sees only its own slice.

The second wrinkle: one tenant can hold several partners with different scopes. A client might use one partner for new builds, a second for breakfix, and a third for event support. APEX models that as overlapping partner assignments per project, equipment item, and platform license. Each partner sees only its slice; the tenant admin sees who handles what. Once several partners run on the same client through APEX, the platform becomes the system of record they all coordinate through, and that shared workspace is what makes APEX stick.

4. What the partner side actually does

Most "partner portals" in AV are a CRM bolt-on: one page where a subcontractor logs in to update a status field on a job they're assigned. The APEX partner side is the integrator's primary workspace. They work in it all day.

The partner portal has seven top-level destinations, mirroring the company side:

• ·Home, cross-tenant overview. Time-aware greeting, attention cards (pending visit proposals, credentials needing attention, license renewals, upcoming visits), open tasks across every client, jump tiles to deep destinations.
• ·Projects, the active client's project list, scoped to what the partner is assigned to. Each project drills into a workspace with phased tasks, equipment BOM, onsite visits with full lifecycle, discussion thread, attachments, and a partner-private task list.
• ·Onsite, calendar + list of every visit across every project for the active client. Propose, reschedule, mark-on-site, mark-done with structured outcome and reschedule reason.
• ·Infrastructure, read-only fleet view powered by the Cisco Control Hub plugin (Microsoft Graph / MTR coming Q3 2026). Device health donut, per-location cards, workspace inventory, full device table. Scoped to the active client.
• ·Licenses, the platform licenses (Webex, Teams Rooms, Mersive, Logitech Sync, etc.) this partner manages on the client's behalf. Renewal calendar, seat counts, annual spend rollup.
• ·Credentials, partner's own compliance state (COIs, business licenses, manufacturer certs). Per-tenant for relationships with specific coverage requirements; global for org-level certs.
• ·Settings, account, team management, notification preferences.

A client switcher in the header swaps the active tenant. Switch to a non-home client and a thin amber band runs across the top of every page, "Working in Client B · Capital Mgmt (client context, not home)", so a tech can't lose track of which client they're in. Underneath, every API call stamps an X-Active-Tenant header, and the resolveVendorTenantContext middleware checks it against the partner's organization membership before any data flows.

5. Keeping the conversation in one place

The hardest part of AV operations isn't the technology. It's the back-and-forth between the client's team and the partner companies doing the work. Email and Teams chat scatter that across a thousand threads. APEX gives each work item (project, equipment item, room, onsite visit) one discussion thread, and both sides post into the same place.

Onsite visits have a structured lifecycle: partner proposes dates, client approves / counter-proposes / declines with a required reason, partner marks on-site, partner marks done with a structured outcome (done / partial / blocked) and an optional end-of-visit report (photos and video captured straight from the device camera). Every state change lands as a status row in the thread, which is the audit trail.

The client side runs in one of three modes:

• ·Partner-only: client never logs in. The partner uses APEX as their internal tool and emails the client PDF reports when they want a deliverable. Cheapest, lowest friction.
• ·Read-only client: client has a viewer login and sees the partner's work on their projects. Most common starting point.
• ·Co-managed: client has their own internal team in APEX working alongside the partner. Some projects partner-led, some client-led, all in one tenant.

6. Live data from the platforms you already run

APEX connects to the third-party platforms you already run through plugins, so room health and device inventory stay current without anyone re-typing them. Each plugin is a bounded module with explicit capabilities, per-tenant OAuth credentials, rate-limit awareness, and an audit log entry on every external call. The first shipped plugin is Cisco Control Hub. It syncs Webex device state on a rate-limited interval and auto-refreshes OAuth tokens. Microsoft Graph + Teams Rooms is next (Q3 2026), then Logitech Sync and Crestron XiO Cloud.

Plugins don't run free-form code. They expose a typed capability surface to the core: sync devices, sync rooms, push provisioning, fetch usage telemetry. Each tenant opts in per plugin, and the audit trail captures every call. Zapier and n8n trade safety for flexibility. APEX goes the other way and takes the typed boundaries, which fit AV's integration shape.

7. What's shipped today

What works in the product right now (May 2026):

8. What APEX is not

The boundaries, the things APEX doesn't try to be:

• ×Not ConnectWise / NinjaOne / Datto. Those are generic MSP platforms built for IT (laptop fleets, patching, RMM). APEX is AV-native, so it won't handle your printer contracts or endpoint protection.
• ×Not a general-purpose PM tool. The data model is for AV ops. SDLC, marketing campaigns, HR onboarding are all the wrong fit.
• ×Not a ServiceNow replacement at the enterprise level. The audit and service-catalog surface covers AV scope; it doesn't replace tenant-wide ITSM.
• ×Not a monitoring platform. Plugins surface manufacturer telemetry. APEX doesn't probe devices or run synthetic checks itself.
• ×Not a drawing or CAD tool. APEX will version Vectorworks files (on the roadmap) but won't render or edit them.
• ×Not a billing platform. License costs and visit time are tracked; invoicing flows through your existing AR system.

9. Where APEX is going

APEX is in early access: founder customers shape the build, early adopters get in early, and the Roadmap is public. Founding customers get early-access pricing, finalized at launch. The next blocks of work:

• Q3 2026Microsoft Graph + Teams Rooms plugin. MTR pairing state, calendar bookings, peripheral inventory.
• Q3 2026License renewal notifications. Email triggers at configured threshold days. Data is captured today; delivery is on the roadmap.
• Q3 2026Logitech Sync plugin. Rally Bar / Tap / Brio fleet management, firmware push, room-pairing state.
• Q4 2026BOM ↔ field reconciliation. Vectorworks part-number cross-check, asset tag scan from the visit drawer, drift flag before commissioning.
• Q1 2027Signal-path validation. EDID handshake telemetry, Dante subscription state, DSP preset sync verification, PoE budget calculator, AVB stream state.
• v1.0 (Apr 2027)As-built bundle generation. Redlined drawings + IP schedule + DSP configs + training videos packaged at closeout.

Read further: the How-To guides walk through specific workflows. The Technical Reference covers architecture, API, and deployment. The Roadmap page has shipping dates and founder voting status. Or start your 30 days free and click through what's shipped today.