# Beszel: your own hub

Under Connections, category Monitoring, you store your own Beszel hub so servers can use it instead of MainPath-managed service.

> Source: https://www.mainpath.ai/en/docs/beszel-credentials/

**Beszel** lives under **Connections** in the **Monitoring** category. Without your own hub, servers use MainPath-operated Beszel service (recommended). With your own hub you enter the URL and credentials once for the organization and select it on the server. You can also run a hub as a [Docker App]({{< relref "hosted-apps" >}}) on one of your servers.

## What Beszel expects

The hub is a PocketBase instance. MainPath authenticates with email/password or an API key and needs the universal token plus the public SSH key agents use to register systems.

| Field | Content |
|---|---|
| **Hub URL** | Base URL of your Beszel hub, for example `https://beszel.example.com` |
| **Email** and **password** | Admin or API user of the hub |
| **API key** | Alternative to password login when the hub offers it |
| **Universal token** | Token agents use to create systems |
| **Public key** | Hub public key for agent registration |

## Select it on a server

When you create or edit a server (not a webspace), enable **Monitor server** and under **Beszel hub** choose either **Managed by MainPath (recommended)** or your own connection. The same picker is in the server details.

Triggered alerts are pulled from the Beszel API when possible and appear in the project export under monitoring.