Choosing a machine
Pick what is already around. Chat is cheap; what decides the size is the biggest Talk you run, and on a home line usually the upload speed, not the CPU.
The options
| Machine | Good for | Watch out for |
|---|---|---|
| A NAS (Synology, Unraid) | On all the time anyway, quiet, already has storage | The router: voice needs forwarded UDP ports, and the line needs a public IPv4 address |
| A small VPS | A public IPv4 address and no router to configure; fast upload | A few euros a month; pick a provider in your country that you trust |
| A Raspberry Pi 4 or 5 | Plenty for a crew, low power | A 64-bit system is required; put the database on an SSD or a good SD card |
| A spare PC with Linux | Any machine that runs Linux and Docker | Use a wired network; same router rules as a NAS |
Images are published for linux/amd64 and linux/arm64; Docker picks the right one. 32-bit ARM (linux/arm/v7) is not built.
What about the gaming PC?
Docker Desktop on Windows or macOS is fine for trying Mnema Talk on one computer, but it is not a tested hosting target. For your crew, use a Linux machine, a NAS or a VPS.
Can your home line host at all?
Only if it has its own public IPv4 address. Many providers share one address between many customers (CGNAT), or give you IPv6 plus a shared IPv4 (DS-Lite). Ports you forward on such a line never receive anything, so chat may work through a tunnel while every voice call from outside fails. Behind a router shows how to check in a minute. If the answer is no, a VPS is the way to go.
How big it has to be
What a server needs depends on the largest Talk you run, not on how many members have an account. 1,000 connected chat sessions used about 0.7 of a core and 100 MB in the benchmark. Every video stream the server forwards costs CPU, memory and upload bandwidth.
The rows come from the benchmark's sizing guide and describe one Talk at a time with 3 speakers, plus the screen share or cameras named:
| Talk | CPU to plan for | RAM | Server upload |
|---|---|---|---|
| About 10 members, voice only | 0.1 core | 1 GB (the default) | 1 Mbit/s |
| About 25 members, 1 screen share (1.5 Mbit/s) | 0.5 core | 1 GB | about 51 Mbit/s |
| About 50 members, 1 screen share and 4 cameras | 1.4 cores | 1 GB | about 180 Mbit/s |
| About 100 members, voice and 1 screen share | 1.8 cores | 1 GB | about 208 Mbit/s |
CPU is in cores of an Intel N100, the benchmark's test host. Shapes beyond the table, several Talks at once and long runs were not measured: run the benchmark on your own hardware for those.
Once it runs, Admin > Status > Capacity shows the live CPU, memory and outgoing traffic, and for each kind of Talk about how many people fit and what runs out first.