System Requirements
Accelero is distributed as a multi-container (Docker) application and runs on an on-premises server or in the cloud. This page describes the software platform and the sizing criteria.
Software platform
| Component | Technology |
|---|---|
| Orchestration | Docker / Docker Compose |
| Operating system | Linux |
| Web server | Nginx (TLS / HTTP2) |
| Application | PHP-FPM 8.1+ |
| Database | MySQL / MariaDB |
| Cache | Redis / Valkey |
| Device broker | Mosquitto (MQTT) |
All services are delivered in containers — there is no need to manually install these dependencies on the host.
Database
MySQL / MariaDB, accessed via PDO/mysqli. There is no support for other databases.
Network and connectivity
- HTTPS (443) for the operators' web interface.
- MQTT for communication with the field devices (controllers), with a credential and ACL per device.
- Connectivity between the server and the controllers/readers on the local network.
Browser
Interface compatible with up-to-date modern browsers (Chromium — Chrome/Edge —, Firefox, and Safari).
Server sizing
Accelero imposes no fixed limits on capacity; the volume of people, devices, and events an installation supports — and the performance — depend on the server sizing (CPU, memory, storage, and network).
The server is sized per deployment, according to the customer's scale; the Iongrade team advises on the sizing in the project. Even so, being a lightweight system, the core starts from modest minimum requirements:
| Resource | Minimum |
|---|---|
| Processor | Intel Celeron N3350 (or higher) |
| RAM | 4 GB |
For larger installations, the sizing grows with the load (number of people, devices, and event volume), with a server processor (e.g., Intel Xeon) and headroom in memory and storage.
How capacity relates to licensing and infrastructure in Capacities and Limits.
Next Steps
- Capacities and Limits - How Accelero scales
- On-premises Server - Local installation