VICTOR SOLUTIONS / MULTI-SITE
Your enterprise, across every site.
Operate distributed Victor infrastructure through one administrative view. Victor Enterprise brings together search, tasks and alarms across sites, while each site retains its own local management, permissions and operational independence.
Victor Enterprise · Community runs one site of any size01 / ONE TREE, EVERY SITE
Search and act across sites.#
Every joined site appears as a level in the inventory tree. Search across all of them, see tasks, alarms and events in one place, and run an action at the site that owns the object.
Actions are authorized and audited at the owning site, under that site’s own permissions. Losing one site does not take the others down.
- Pairwise joins with pinned mutual-TLS certificates
- Read or act scope per join
- victorctl site and an MCP sites toolset
02 / JOINING SITES
Invite, join, done.#
An administrator creates a one-time invite at one site and pastes it at the other. Both sites record each other, with the scope you chose.
victorctl site invite --scope act --expires 1h # prints a one-time invite
victorctl site join INVITE --scope act # at the other site
victorctl site ls
victorctl site search db-03 / WHAT CROSSES SITES
Clear about the boundary.#
| Service | Across sites |
|---|---|
| Inventory and search | Yes |
| Tasks, events and alarms | Yes |
| Actions on objects | Yes, routed to and audited at the owning site |
| Consoles, metrics, backups, migration | Not yet; open them at the owning site |
| Moving a VM between sites | Not in one step yet; back up at one site and restore at the other |
| Service accounts | Act only at their own site |
Federation has been tested with three simulated sites on one host, not yet across real WAN links.
FAQ
Multi-site questions.#
Is there a single point of failure?
No federation server exists. Each site runs its own Victor and database, and joins are between pairs of sites. A site that is unreachable shows as unreachable, with the reason, and the others keep working. #
Can Community manage two sites?
Community manages one site with no cap on hosts or clusters. Run two Community sites separately, or use Enterprise federation to see them together. #
How is this different from one big cluster?
Sites stay independent: their own control plane, database, permissions and failure domain. Federation adds a shared view and routed actions on top. #
NEXT STEP
Map your sites with us.
Tell us how many sites you run and how they connect. We will show federation in a guided demo.