Product

Five capabilities. One workspace.

Vectis is built around the customer account — the unit of work for every MSP. Each section below is one core capability, one concrete moment, and one real screenshot from a seeded 25-customer instance.

The customer hub Cross-tool rules Timeline Query builder Customer portal

One · Customer hub

Every customer, top to bottom, on one page.

A customer calls the tech who picked up at 9:14am. Old flow: open ConnectWise for the ticket history, NinjaOne for the alerts, Datto for last night’s backup, QuickBooks for the contract, and a tab for the M365 posture. Four tabs, three logins, a customer-id copy-paste between each. The Vectis flow: open the customer. Their tickets, devices, alerts, last-backup status, contract MRR, and M365 health render on one screen, with the action buttons inline. No tab-switching, no account-number reconciliation, no “hold on a second.”

Vectis customer hub landing surface for a seeded MSP customer: health badge, MRR, critical incidents, renewal countdown, connected source tags, and a tab strip linking to tickets, labor hours, devices & alerts, backups, communications, contracts, compliance, PSA invoices, billing system, profitability, users, documentation, notes, and timeline. — Customer hub — every connected tool on one page.

The hub is built around the customer account, not the data source. Tickets, alerts, devices, backups, contracts, invoices, M365 posture, communications, and an internal notes surface render as tabs on one page, each populated from whichever connectors that customer happens to be wired to. Replies, acknowledgements, and ticket creations are inline actions that write back to the source system through an audited connector — every action carries the operator, the target, and the payload into the append-only audit log.

Used withConnectWiseAutotaskHaloPSANinjaOneMicrosoft 365

Two · Cross-tool rules

If this in tool A, then that in tool B — with the audit trail.

3:11am. NinjaOne fires a critical disk alert on a file server. The rule asks: is there an open ConnectWise ticket for this customer in the last 24 hours that covers it? No. Open one on the right board, route to the after-hours tech, paste the alert payload as the first note, set the status to In Progress, and notify the customer in the portal — all within twelve seconds, all logged, all reversible. The morning tech sees a ticket queue, not an inbox of duplicated alerts.

Vectis rules index: a dry-run rule wiring NinjaOne incidents to ConnectWise tickets, with last-fired timestamp, 7-day activity rate, and an enabled toggle — the engine evaluating real triggers, not a demo gif. — Rule firing — NinjaOne alert to ConnectWise ticket, in real time.

Triggers come from any connected system — RMM alerts, PSA events, backup outcomes, contract milestones, vendor webhooks. Conditions span the unified data with AND/OR grouping and cross-system checks (e.g. “an alert exists with no matching ticket”). Actions write back to the right system: create or update a ticket, reply, change status, acknowledge or resolve an alert, notify the customer portal. Every new rule ships with a mandatory dry-run mode and per-integration rate limits; failures land in a dead-letter queue with one-click manual replay.

Used withConnectWiseNinjaOneDattoVeeamPax8

Three · Timeline

What happened, in order, across every tool.

A customer pings Tuesday morning: “something felt off with us on April 11 — can you reconstruct what happened?” The timeline filters to that date and merges every ticket reply, alert fire, backup run, invoice event, and internal note into one chronological stream. The reconstruction takes a minute. You answer with sources tagged on each entry — ConnectWise here, NinjaOne there, Datto for the backup — not a reading-the-vibes summary.

Customer timeline filtered to a single day, mixing ConnectWise ticket activity, NinjaOne alert events, Datto backup runs, and Microsoft 365 sign-ins in chronological order. — Timeline — every source merged on one day, one customer.

The timeline is the per-customer event feed, merged across every connected system into one chronological stream with source tags on every entry. Date filters scrub by day, week, or arbitrary range; source filters narrow to one tool when you need to. Internal Vectis-native notes interleave with vendor events, so the “we talked to their CIO at 4pm” line lives on the same surface as the ticket and the alert — not in a separate notes app no one opens.

Used withConnectWiseAutotaskNinjaOneDattoMicrosoft 365

Four · Query builder

Ask anything across the unified data.

A dispatcher needs the renewal-risk list before Wednesday’s standup. The ask: “which customers have a backup failure in the last seven days AND a contract renewing in the next thirty?” No single tool answers it. The Vectis query builder asks it in three clicks: pick customers, join backups + the contract rail, set the two filters, hit Run. Four customers, $14,820 of monthly contract value at risk, exported to Excel before the coffee’s done.

Vectis query builder with a point-and-click filter chain, the results table populated, and an Excel export button visible. — Query builder — ask anything across your stack, export to Excel.

The query builder is a point-and-click join interface over a frozen allowlist of schema tables: customers, tickets, conversations, contracts and line items, daily metrics, SLA snapshots, backup connectors, invoices, payments, credit memos. AND/OR filters with operators per column type; one-click Excel export; saved queries shared with your team and audit-logged on every execution. The allowlist means a misclick can’t reach an internal table; the query plan stays scoped to your tenant by construction.

Used withConnectWiseAutotaskDattoMicrosoft 365QuickBooks

Five · Customer portal

A surface your customers see, branded as your MSP.

An end-customer logs in to your subdomain — your colors, your logo, no Vectis chrome anywhere. They see their open tickets, their devices, their last backup status, their active contracts, their recent invoices, and the security posture you’ve chosen to expose. They submit a ticket inline; it routes to your PSA on the right board with the requester pinned. They see what their team uses, not what you can sell them.

Branded Vectis customer portal home view for a seeded customer with asset count, open tickets, and recent invoices. — Customer portal — branded per tenant, available as an add-on.

Pricing — portal add-on $99 / $199 / $299 per month on Starter / Growth / Scale, included on Enterprise. Priced per MSP, not per end-customer — per-end-customer pricing punishes adoption and we’d rather you turn it on for everyone.

The portal runs under a per-tenant subdomain with your logo and accent color baked into the email shell and the navigation chrome. Ticket submissions land in your PSA on the configured board; multi-site clients see the parent rollup with site-level drill-in; outbound notifications ride the unified email shell with CAN-SPAM scaffolding already wired. Every customer-facing action lands in the audit log alongside every operator action — one trail, two surfaces.

Used withConnectWiseAutotaskHaloPSAAteraQuickBooks

Six · Built to extend

Open protocols, not a walled garden.

Vectis exposes its tenant data over three surfaces a technical buyer expects to find on day one. The public REST API covers the same read and write actions the in-product UI calls, scoped by personal access token. An open Model Context Protocol endpoint lets any MCP-compliant client — Claude Desktop, Cursor, ChatGPT, your own — read and act against your tenant; Vectis itself never calls a model, the protocol is the product. Inbound webhook receivers accept signed payloads from any vendor that emits them, so Pax8 license deltas and ConnectWise ticket updates hit Vectis the moment they happen rather than on the next sync cycle.

REST / MCP / Webhooks — on every tier.

Compare

Evaluating another tool alongside Vectis?

Honest side-by-sides on the products MSPs most often shortlist next to Vectis.

vs Asio vs Kaseya IT Complete vs Rewst vs BrightGauge

Start your 30-day trial.

Connect your PSA and RMM at signup. Every customer with their full context on day one. No card required.

Start 30-day free trial See the integrations