# Connect your platform

Declare your first source, with a read-only account and an address the collector can reach.

## The steps

1. On **Settings › Integration**, click the tile of your platform.
2. Choose the collector that will poll it, and give the source a name.
3. Enter the full address, with `https://` and the port if it is not 443.
4. Enter the read-only account prepared in [the first lesson](/en/connect/prepare). The secret is encrypted, and is never shown again.
5. Choose the **Collection frequency**. Every 4 hours is the recommended setting.
6. Click **Connect the source**.

## By platform

| Platform | Example address | Credential |
|---|---|---|
| VMware vSphere | `https://vcenter.example.local` | Username and password |
| Proxmox VE | `https://pve.example.local:8006` | API token: `user@realm!token=UUID` |
| Xen Orchestra | `https://xoa.example.local` | Authentication token |
| Nutanix Prism Central | `https://prism.example.local:9440` | Username and password |
| Microsoft Hyper-V | A cluster node, port 5986 | Username and password |
| OpenShift Virtualization, Superphenix | `https://api.example.local:6443` | Service account token |
| HPE VM Essentials | `https://vme.example.local` | VME Manager API token |

Other platforms join this list regularly: the Integration page shows those available today.

> Declare the highest entry point. A vCenter covers all its hosts, and Prism Central all its AHV clusters. Two sources on the same scope would count every machine twice.

## The certificate

**Verify the TLS certificate** stays ticked when your platform presents a recognized certificate. With an internal authority, install it on the collector machine, or untick verification for that source.

### The source stays waiting for its first collection

Click **Collect** on its card, then open its logs. The next lesson explains how to read them.

### I do not know which entry point to choose

Take the one that sees the widest and that you already administer: the vCenter rather than an ESXi host, Xen Orchestra rather than an XCP-ng host, Prism Central rather than a cluster.