HandyCafe Docs
owner it-admin

System Requirements

Before installing HandyCafe in your internet cafe, gaming center, or esports arena, verify that your hardware and network meet the following requirements.

Server PC Requirements

The server is your management station. This is the PC where you run HandyCafe Server to monitor and control the entire cafe.

Component Minimum Recommended
Operating System Windows 10+ (64-bit), macOS 12 Monterey+, or Linux (64-bit) Windows 10/11 (64-bit), macOS 12+, or Linux (64-bit)
Processor Dual-core 2.0 GHz Quad-core 2.5 GHz+
RAM 4 GB 8 GB+
Disk Space 500 MB (application) 2 GB+ (with recordings and screenshots)
Display 1280 x 720 1920 x 1080+
Network 100 Mbps Ethernet Gigabit Ethernet

Note: If you use remote desktop with session recording, allocate additional disk space for MP4 recordings (approximately 50-200 MB per hour of recording depending on quality).

Linux note: HandyCafe is built with Tauri v2 which uses WebKit2GTK on Linux. You must install the libwebkit2gtk-4.1 runtime package before running the application. Supported distributions include Ubuntu 22.04+, Fedora 38+ and other distributions shipping an equivalent version of WebKit2GTK.

Client PC Requirements

Each customer-facing PC runs HandyCafe Client, which connects to the server over the local network.

Component Minimum Recommended
Operating System Windows 10+ (64-bit), macOS 12 Monterey+, or Linux (64-bit) Windows 10/11 (64-bit), macOS 12+, or Linux (64-bit)
Processor Dual-core 1.5 GHz Quad-core 2.0 GHz+
RAM 2 GB 4 GB+
Disk Space 200 MB 500 MB+
Network 100 Mbps Ethernet Gigabit Ethernet

Note: These are requirements for the HandyCafe Client software only. Your PCs will need additional resources for the games and applications your customers use.

Network Requirements

All PCs (server and clients) must be on the same local network (LAN).

Required Ports

Port Protocol Direction Purpose
5001 TCP Server: inbound, Client: outbound Command and response communication
5002 TCP Bidirectional File transfers
5003 TCP Server: inbound, Client: outbound Remote management control channel
5004 UDP Bidirectional Screen streaming (remote desktop)

Important: These are the default ports. You can change them in Network Settings. If you change the ports on the server, update the client configuration to match.

Firewall Configuration

  • Windows Firewall: HandyCafe attempts to add firewall rules automatically during installation. If automatic configuration fails, manually add inbound rules for the ports listed above.
  • macOS Firewall: Open System Settings > Network > Firewall and allow incoming connections for HandyCafe. Alternatively, add the ports listed above to your firewall allow list.
  • Linux (iptables / ufw): If you use ufw, run sudo ufw allow 5001:5004/tcp and sudo ufw allow 5004/udp. For raw iptables, add equivalent INPUT ACCEPT rules for TCP ports 5001-5003 and UDP port 5004.
  • Third-party firewalls: Add exceptions for the HandyCafe server binary on the server PC and the HandyCafe client binary on client PCs.
  • Router/Switch: No special configuration needed for LAN-only operation. If you have VLANs, ensure the server and all clients are on the same VLAN or that routing allows the required ports.

Client Discovery

HandyCafe uses mDNS (multicast DNS) for automatic client discovery on the local network. This requires:

  • All PCs on the same subnet
  • Multicast traffic not blocked by switches or routers
  • If mDNS does not work (e.g., across subnets), clients can connect by entering the server's IP address manually

Bandwidth Considerations

Feature Approximate Bandwidth
Normal operation (per client) < 1 Kbps
Remote desktop streaming 350 - 25,000 Kbps (configurable)
File sync transfer Limited by network speed
Screenshot capture ~100 KB per screenshot

For a typical cafe with 20-50 PCs, a standard 100 Mbps LAN is sufficient. Gigabit Ethernet is recommended if you frequently use remote desktop for multiple PCs simultaneously.

Console Requirements

If you manage gaming consoles (PlayStation, Xbox, etc.), the consoles must be on the same network as the server. Each console is identified by its MAC address and registered manually in Console Settings.