Connect servers across machines and it’s US$30 per machine a month, from the second machine. Your first 30 days of multi-machine use are free.
Players, cores and developers are never counted. Development and production count the same way.
Run as many zlink servers as you like on one PC or VM, for development or a live game. No key needed.
Spread a service across machines. The first machine stays free. US$300 a year if you pay yearly.
SLA, source escrow, long-term support versions and priority fixes under a separate support agreement.
Contact| Setup | Connected machines | Per month |
|---|---|---|
| Developing on your PC, many servers in Docker | 1 | Free |
| A small game on one server | 1 | Free |
| Lobby and game servers on two machines | 2 | US$30 |
| An indie MMO on four servers | 4 | US$90 |
| A studio on twenty servers | 20 | US$570 |
A machine is one physical computer or VM. Everything on it, containers included, is one machine. We count the machines that the servers of one service run on at the same time. Kubernetes counts nodes; managed container services count running instances.
Not on one machine. To connect a second machine, register a key. Free keys come with a GitHub sign-in and are already inside projects you create with the Initializr.
Your servers keep running. Versions you received while subscribed stay licensed for your machines. New versions and extra machines need a subscription.
Only when a service runs on two or more machines, once a day: a random service ID, your account and key IDs, the machine count, the zlink version and the OS type. No game data, player data or code. One machine sends nothing.
No. A missing key or extra machines only produce a warning. The one thing zlink refuses is a second machine joining a service that has no key at all.