Environment requirements
Minimum and recommended server parameters for deploying the on-premise version.
Terms used in this guide
- A reverse proxy accepts external requests and forwards them to MassAccess services.
- Transport Layer Security (TLS) encrypts connections to the public address.
- A health check confirms that a service is ready to handle requests.
- Enrollment binds an installed instance to the created license.
System requirements
| Component | Minimum | Recommended |
|---|---|---|
| OS | Linux kernel 5.x+ | Ubuntu 22.04 / Debian 12 |
| Docker Engine | 24.0+ | 27.0+ |
| Docker Compose | v2.24+ | v2.30+ |
| Installer | Bash, Python 3, curl | Bash, Python 3, curl |
| CPU | 4 cores | 8 cores |
| RAM | 8 GB | 16 GB |
| Disk | 50 GB SSD | 100 GB SSD |
| Internet | 100 Mbps | 1 Gbps |
Public ports
The platform publishes three ports. The API and web panel ports are exposed externally only through a reverse proxy; the service port is not exposed externally.
| Port | Purpose | Access |
|---|---|---|
| 10001 | API and webhook requests | Only for the reverse proxy (not exposed directly) |
| 10002 | Service checks | No public access required |
| 10011 | Web panel | Only for the reverse proxy (not exposed directly) |
Domain and TLS
To access the control panel and API over the internet, configure a public DNS domain pointing to the server's external IP and a valid TLS certificate on port 443 (reverse proxy). Incoming messenger traffic is delivered by the MassAccess platform and does not require a separate public domain or certificate from you.
Connectivity requirements
The product is not offline or air-gapped. Keep the documented outbound routes available for license heartbeat, signed usage metering, cloud billing, image delivery, and Telegram/MAX connectivity.