> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Scale Computing HyperCore

> Let Neo agents read and work a client's HyperCore cluster: each VM's vCPU, memory and snapshot schedule, reboots, snapshots and clones

Scale Computing HyperCore (SC//HyperCore) runs a client's virtual machines on a cluster of nodes, usually at the client's own site. Connect a client's cluster, and Neo agents can read and work its VMs from a ticket, a schedule or a chat.

## What Neo can do with HyperCore

* Read every VM with its vCPU, memory, disks, NICs, power state and the snapshot schedule assigned to it, and list which VMs each schedule protects
* Reboot, start, shut down or live-migrate a VM, and read that it reached the new state
* Take a snapshot before a change, assign or change a snapshot schedule, and clone a VM or a snapshot
* Add vCPU or memory, add or grow a disk, and insert an ISO, with the VM shut down and started again when the change needs it
* Read nodes, drives, cluster health alerts (conditions), replication, and the result of every change HyperCore runs as a task

## One connection per client

A HyperCore cluster holds one client's VMs, so you connect HyperCore once for each client, under that client's company in your PSA. On a ticket, the agent calls the cluster of the ticket's company. A scheduled agent or a chat names the client in each call.

A cluster that hosts several clients' VMs, such as one in your own data center, is connected under the company whose tickets should reach it, usually your own. Every call on it reaches all of its VMs, and Neo cannot tell which client owns a VM there. So an agent that works that company's tickets can change any VM on the cluster: give it the **Read Only** preset, or turn on approval for every area you leave Read/Write, so a technician checks each change.

See [Scale Computing HyperCore API](https://docs.neoagent.io/agents/tools/networking/scale-hypercore-api.md) for the permission groups.

## Next steps

> [card] [Connect Scale Computing HyperCore](https://docs.neoagent.io/integrations/scale-hypercore/connecting-to-neo.md)
>
> Give Neo a HyperCore user and save it with the address of a node of the client's cluster.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.