Humly Control Panel (HCP) is the server behind your Humly devices. It manages Humly Room Displays and Humly Booking Devices. It also connects them to your booking system, such as Microsoft 365, Google Workspace or Exchange Server.
You can use HCP in Humly Cloud or run it on your own server. This article shows how the parts connect in each setup, and what your network must allow.
In this article
- Two ways to run Humly Control Panel
- Humly Cloud
- On-premises
- Humly Cloud IP ranges
- Optional features and integrations
- Supported booking systems
- Get started
Two ways to run Humly Control Panel
| Humly Cloud | On-premises | |
|---|---|---|
| Server | Run and updated by Humly | Your own Windows or Linux server |
| Your HCP address | Your cloud ID, for example 12345.humly.cloud | Your server's host name or IP address, for example hcp.example.com |
| Port for devices and browsers | TCP 443 | TCP 3002 by default. You can use TCP 443 or another port. |
| TLS certificate | Managed by Humly | Self-signed at install. Replace it with your own. |
Devices always connect out to HCP. HCP never connects in to a device. In the diagrams below, each arrow starts where the connection starts. Allow traffic in that direction.
Humly Room Displays can use an HTTP proxy for outbound traffic. So can an on-premises HCP server.
Allow WebSocket traffic
Humly devices use a long-lived WebSocket connection to HCP, and they have no fallback. A proxy or TLS-inspecting firewall that blocks the WebSocket upgrade stops them from connecting. Read WebSocket Connectivity Requirement for Humly Control Panel before you roll out devices.
Humly Cloud
Humly runs HCP for you. Everything in your network connects out over the internet.
What your network must allow
Allow all of Humly Cloud, by host name or by IP range. This gives your network access to your HCP, licenses and updates.
| From | To | Port | Used for |
|---|---|---|---|
| Humly devices | *.humly.cloud or Humly Cloud IP ranges | TCP 443 | HTTPS and WebSocket to HCP |
| Humly devices | Firmware endpoint: humly.online and *.humly.online, or Humly Cloud IP ranges | TCP 443 | New device firmware |
| Humly devices | NTP server | UDP 123 | Device time. The default is 0.pool.ntp.org. Change it in Global Settings. |
| Web browsers | *.humly.cloud or Humly Cloud IP ranges | TCP 443 | Control Panel, Reservations, Visitor and Floor Plan |
| Humly Print Service | *.humly.cloud or Humly Cloud IP ranges | TCP 443 | Only if you use it. You install it in your own network. It connects out to your HCP in Humly Cloud. |
| REST API clients | *.humly.cloud or Humly Cloud IP ranges | TCP 443 | Only if you use the API. |
Systems in your own network
Humly Cloud needs no inbound ports, with one exception. If you run one of these systems on site, HCP must be able to reach it. It must be reachable from the internet. Allow the connection from the Humly Cloud IP ranges only.
| System | Port | When you need it |
|---|---|---|
| Exchange Server | TCP 443 | Only if your booking system is Exchange Server. |
| LDAP or Active Directory | TCP 636 (LDAPS) or TCP 389 | Only if you import users from LDAP. Use LDAPS. |
| SMTP server | Your SMTP port | Only if you send email through your own SMTP server. |
On-premises
HCP runs on your own server. Devices and browsers stay inside your network. The server connects out to your booking system and to Humly Cloud. A few optional features also connect in to the server.
What your network must allow
TCP 3002 is the default HTTPS port. You can change it to TCP 443 or any other port. If you do, use your port wherever this table says TCP 3002.
| From | To | Port | Used for |
|---|---|---|---|
| Humly devices | HCP server | TCP 3002 | HTTPS and WebSocket to HCP |
| Web browsers | HCP server | TCP 3002 | Control Panel, Reservations, Visitor and Floor Plan |
| Humly Print Service | HCP server | TCP 3002 | Only if you use it. Install it on a separate server in your network. |
| REST API clients | HCP server | TCP 3002 | Only if you use the API. |
| HCP server | Booking system | TCP 443 | Calendar data. See Supported booking systems for host names. |
| HCP server | *.humly.cloud or Humly Cloud IP ranges | TCP 443 | Licenses, software updates and monthly statistics. Also email and SMS sent through Humly. No internet access? See below. |
| HCP server and Humly devices | Firmware endpoint: humly.online and *.humly.online, or Humly Cloud IP ranges | TCP 443 | New device firmware |
| HCP server | NTP server | UDP 123 | Server time, through the operating system's time service |
| Humly devices | NTP server | UDP 123 | Device time. The default is 0.pool.ntp.org. Change it in Global Settings. |
| HCP server | LDAP or Active Directory | TCP 636 (LDAPS) or TCP 389 | Only if you import users from LDAP. Use LDAPS. |
| HCP server | SMTP server | Your SMTP port | Only if you send email through your own SMTP server. |
HCP can also answer SNMP monitoring queries on UDP 161. SNMP is off by default.
Servers without internet access
HCP also runs on an isolated network, without access to Humly Cloud. Humly sends your licenses as files, and you add them in the Control Panel. You can also upload device firmware by hand.
Server requirements
| Operating system | Windows Server 2019 or later, 64-bit. Ubuntu Server 20.04, 22.04 or 24.04 LTS, 64-bit. |
| Minimum hardware | 4 CPU cores, 8 GB RAM and 40 GB storage. The CPU must support AVX, which MongoDB requires. |
| IP address | A static IP address. Devices connect to this address or its DNS name. |
| Internet during install | Linux needs internet access to download packages. Windows has an offline installer. |
| Humly Print Service | Install it on a different server. |
Installation guides: Windows and Linux.
Humly Cloud IP ranges
Humly Cloud has no single static IP address. Allow it in your firewall in one of two ways.
By host name, if your firewall supports wildcards:
*.humly.cloudfor your HCP, licenses and updates.humly.onlineand*.humly.onlinefor firmware.
By IP range, which covers all of the above. Addresses inside a range can change, so allow each whole range.
| IP range |
|---|
5.45.176.208/28 |
5.45.176.224/28 |
5.45.179.112/28 |
185.45.115.0/28 |
Use the IP ranges to let Humly Cloud reach a system in your own network. Host names do not work for this direction.
Optional features and integrations
Humly Cloud: Humly manages these connections on the cloud side. You have nothing to allow.
On-premises: if you use a feature below, allow its connection. "Your HTTPS port" means TCP 3002, or the port you chose instead.
| Feature | On-premises: what to allow | Notes |
|---|---|---|
| Microsoft Graph webhooks | Microsoft Graph to your HTTPS port, on the /api/v1/webhooks/ paths | Microsoft 365 only. Booking changes arrive right away. Your server needs a public HTTPS address. Without it, HCP syncs on its regular sync intervals. Microsoft lists its source addresses. |
| License checks from Humly Cloud | Humly Cloud IP ranges to your HTTPS port | Lets Humly Cloud check your licenses. HCP keeps working without it. |
| Floor Plan | Web browsers to *.smplrspace.com on TCP 443 | Loads the 3D map from Smplrspace. |
| Single sign-on | Web browsers and HCP to your identity provider on TCP 443 | Microsoft Entra ID, Google or AD FS. |
| Outlook add-in | Outlook to your HTTPS port | Uses the same address as your web browsers. |
| Signage mode | Humly Room Display to your signage URL | The device opens the page directly. |
| Disruptive Technologies sensors | HCP to api.disruptive-technologies.com and identity.disruptive-technologies.com on TCP 443.Their cloud to your HTTPS port. | Your server needs a public HTTPS address. Cloud connectors have their own firewall rules. |
| Haltian sensors | Haltian's cloud to your HTTPS port, on the /api/v1/ paths | Your server needs a public HTTPS address. HCP makes no connection to Haltian. |
| Xyte | HCP to *.xyte.io on TCP 443, and to Xyte's MQTT address | Xyte sets the MQTT address when a device registers. |
A few connections start inside your own network, even with Humly Cloud. You need a rule for these only if your network restricts what browsers and devices can reach:
- Web browsers to
*.smplrspace.comfor Floor Plan. - Humly Room Displays to your signage URL for signage mode.
- Teams clients to
teams.humly.comfor Microsoft Teams. This address is outside the Humly Cloud IP ranges.
The Microsoft Teams integration is available with Humly Cloud and Microsoft 365 only.
Supported booking systems
HCP connects to one booking system. It uses HTTPS on TCP 443.
| Booking system | HCP connects to |
|---|---|
| Microsoft 365 | graph.microsoft.com and login.microsoftonline.com. Government clouds use other host names. |
| Exchange Server SE, 2019 and 2016 | Your Exchange Web Services address. Use HTTPS. TCP 80 is possible only if your server is set up for HTTP. |
| Google Workspace | www.googleapis.com and oauth2.googleapis.com |
| Nexudus | spaces.nexudus.com |
| Appspace | api.cloud.appspace.com |
| TOPdesk | <your-subdomain>.topdesk.net |
| Humly Standalone | No external booking system. Bookings stay in HCP. |
Get started
To start your installation, go to Step 1: Booking System Preparation.
Questions about your network setup? Contact support@humly.com.