Backup integration
Per-customer Keepit backup health on the same hub as PSA, RMM, and billing — no Keepit tab swap.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives.
Read-only today
This adapter pulls data into Vectis but doesn’t write back into Keepit. Rules can still react to the synced data — for example, a Pax8 subscription change can open a ConnectWise ticket or a HaloPSA action. The write-back lands in the PSA, not in Keepit.
How it correlates
Vectis is about Keepit joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
A connector hasn't reported a successful backup inside the freshness window (default 48h). The alerts engine fires the backup-stale trigger; the rule of your choice opens a PSA ticket or pings a Slack channel.
Recovery, security, and compliance events from the Keepit audit log land on the same customer timeline as PSA tickets and RMM alerts. When an event falls inside an open ticket's window for that customer, it attaches to the ticket so the dispatcher sees the full sequence.
Setup snapshot
Mint a dedicated API user + token in Keepit (Users → Edit User → Security → Add API token), grab the regional subdomain from your Keepit URL, and paste both into Vectis. The optional sub-account GUID restricts sync to a single Keepit account; leave it blank to sync every account the token can see. Vectis tests the connection by calling /users before saving. The first sync pulls connectors + latest status; the audit log drains on a 14-day rolling window.
Full setup guideavailable after signup
14-day free trial. Connect Keepit at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.