Hardware requirements
What you need to run CLEVER
CLEVER, the PSI/SI generator, runs on standard x86-64 servers, NUCs and virtual machines with Linux or Windows. Use the sizing below as a starting point. Our engineers confirm the final setup with your team during onboarding.
Recommended sizing per plan
Sizing depends mainly on the number of EPG services, the EIT schedule depth and the number of output transport streams.
| Component | Starterup to 4 EPG services | Professionalup to 32 EPG services | Enterprise / Customup to 250+ EPG services |
|---|---|---|---|
| CPU | 2 cores, x86-64 | 4 cores, x86-64 | 8+ cores, x86-64 |
| Memory (RAM)depends on your EPG schedule | 8 GB | 16 GB | 32 GB |
| Storage | 20 GB SSD | 50 GB SSD | 100 GB SSD |
| Network | 1× 1 GbE | 1× 1 GbE | 2× 1 GbE (management and output separated) |
| Typical platform | NUC, small server or VM | Rack server or VM | Rack server or VM |
These figures are guidelines. Large EIT schedules, many output streams or HbbTV/AIT on every service can need more resources.
Platform and environment
Operating system
- 64-bit Linux, a current LTS release such as Ubuntu or RHEL / Rocky Linux
- Windows Server 2019, 2022 or 2025
- Windows 11 (Pro or Enterprise), including Windows 11 Enterprise / IoT Enterprise LTSC 2024
- Windows 10 Enterprise / IoT Enterprise LTSC 2019 or 2021, while still in Microsoft support
- Keep the OS patched and supported by the vendor
Virtualisation
- Runs on common hypervisors such as VMware, Hyper-V and KVM
- Reserve CPU and memory for the VM so output timing stays stable
- Use a bridged network so multicast reaches the output network
Network and output
- IP output (UDP / RTP, unicast or multicast), SRT, ZIXI or RIST
- ASI or RF output: a compatible ASI / modulator card in the server
- Multicast-capable switches with IGMP where multicast is used
- Access to your EPG sources (XML, JSON or REST API)
Management and support
- Remote management UI: a Windows client that connects to CLEVER remotely
- Only needed to view or change the configuration; CLEVER keeps running when the client is closed
- Secure remote access for our engineers during setup and support
- Accurate system time, synchronised with NTP
Licensing
- Subscription and AWS Marketplace: no dongle needed
- Perpetual licence with hardware dongle: a free USB port on the server
- Dongle licensing suits offline and fixed installations
Redundancy
- Redundancy is simply two systems: a second server or VM with the same specification
- Preferably on separate hardware and power
- Possible in every plan: Starter, Professional, Enterprise and Custom
No hardware of your own?
Use the Dualz Cloud SaaS variant, or launch CLEVER in your own AWS account through AWS Marketplace. AWS handles the infrastructure, and you only need network access to your EPG sources and output destination.