Capacities and Limits
The Accelero core is designed to scale. It imposes no fixed (hard-coded) limits on the number of entities — controllers, people, areas, identifiers, events, etc. There is no, for example, "maximum number of controllers" cap embedded in the system.
In practice, the capacity of an installation is determined by two factors:
- Licensing — the license defines the commercial ceilings per entity.
- Infrastructure — the server sizing determines the volume the installation supports with good performance.
Core scalability
The architecture is multi-container (application, database, cache, and MQTT broker), which allows scaling according to load — vertically (more CPU/RAM/storage) and, at the infrastructure layer, by distributing the services.
Since there are no fixed caps in the code, the growth of an installation (more people, more devices, more events) is a matter of license and server capacity, not an artificial limit of the product.
Details of the architecture and technology base in Security and Architecture.
Limits by licensing
The only quantitative limits in Accelero come from the license. It carries ceilings per entity (operators, controllers, identifiers, categories, time ranges, devices per manufacturer, etc.) and the capacity of active people is defined by the contracted commercial package.
When a ceiling is reached, the system prevents new records of that type until space is freed or the license is expanded.
The full list of limits and the package structure are in Licensing and Modules.
Limits by infrastructure
The volume of people, devices, and events an installation supports — and the performance (response time, release latency, event throughput) — depend on the server sizing: CPU, memory, storage, and network.
There is no single "maximum capacity" figure: it is sized per deployment, according to the customer's scale.
Requirements and sizing guidelines in System Requirements.
Next Steps
- Licensing and Modules - Ceilings and commercial packages
- System Requirements - Hardware sizing