31%
Faster API calls
The full game API call, at the median.1
Customer story
Ludo Saga moved to Plexivo Kubernetes. Players stayed signed in.
Ludo Saga, an online multiplayer Ludo game from India, moved from a single VPS to Plexivo Kubernetes in Mumbai on 26 October 2026. Here is how the move went, measured.
- Flutter app
- Elixir game server
- Aerospike database
The results
About 3 min
Downtime for the switch
One short, planned window. The restore itself took under a minute.
39,550
Game records, every count matched
Plus 5,191 session records. Every data set was counted and compared with the original.
Signed in
Sessions moved with the data
Reopening the app landed straight on Home, with wallet, settings and profile working.
Speed
Faster on every
measure.
The same game server, measured on both hosts. Network connect alone was 37% faster.1
- Plexivo Kubernetes
- Previous VPS host
- Lower is better
Full API call · median
Slow requests · 90th percentile
Realtime connection · websocket handshake
Network connect
Rehearsed first.
Then moved once.
Nothing on the day was done for the first time.
- 1
Rehearse
A full rehearsal restore on Plexivo Kubernetes with live data, before the real switch.
- 2
Measure
The move went ahead only once the rehearsal matched and latency was equal or better.
- 3
Switch
Traffic moved to Plexivo Kubernetes in one short, planned window.
- 4
Verify
Record counts compared with the original, set by set. The old server stayed ready as a rollback copy.
Where it runs
Running on
Plexivo Kubernetes.
The game server and its database are Kubernetes workloads in Mumbai, right-sized for today’s traffic.
Ludo Saga appOn players’ phones
Encrypted
Plexivo Kubernetes · Mumbai
Game serverElixir
Reads under 1 ms
DatabaseAerospike
A micro-VM for every pod.
Each pod runs in its own lightweight micro-VM, kept apart from every other workload.
Right-sized.
0.5 vCPU and 1.5 GB per service, matched to its traffic.
Grows with one update.
When more players arrive, more capacity is a single update away.
Security
Secure from the
first request.
Every protection was checked on the live game, not assumed.
Real player IPs. Forged ones ignored.
The game sees each player’s real IP address and ignores faked IP headers. Proved on the live game:
80requests, each with a forged IP→1player, still rate-limited
No ports opened to the internet.
Analytics reach Ludo Saga’s admin server over a locked-down encrypted tunnel that can open only two ports.
Byte-for-byte the same game.
The exact game image moved unchanged, every layer verified.
Its own certificate.
Players connect over TLS with Ludo Saga’s own certificate.
Backed up four times a day.
Automatic backups to a private bucket, each one verified by checksum.
Your game, app or API.
Moved with the same care.
Standard Kubernetes in Mumbai, with no nodes to manage. Planning a move? Talk to our team about yours.