April was a consolidation month. The features that shipped in March moved into production, warm pools reached their first live customer, and Unity Matchmaker support landed with full documentation. Alongside that, a set of reliability and UX issues were resolved across the admin panel.
Here’s everything that landed.
Unity Matchmaker — now documented and supported
Studios using Unity Matchmaker can now find full documentation and working code for integrating with Gameye. The integration has always been technically possible, but the code and documentation are now available to use directly.
If you’re running Unity Matchmaker for session placement, you can route matched sessions to Gameye dedicated servers without building a custom bridge.
Warm pools: first live customer
Warm pools shipped in March. In April, they went live in production with the first customer. Under real load a set of issues surfaced — all resolved — and the feature is now running stably.
If you’ve been waiting for production validation before enabling warm pools, that validation has happened.
Container history: date/time picker
The container history page now has the same date/time picker introduced on the container details page and dashboard in March. At any meaningful session volume the history list becomes difficult to navigate without a time filter — this brings the history page in line with the rest of the panel.
Smaller changes
Dashboard card fixes. Peak sessions, peak CPU usage, and peak memory usage were displaying incorrect values in certain cases. The root cause has been resolved — the summary bar figures are now accurate.
Tags page fix. An issue affecting the tags page introduced in the March release has been resolved.
API token fixes. A set of edge cases in API token handling have been resolved.
Dropdown search. Dropdowns with large option sets now include a search field, making it faster to find the right value without scrolling.
Error messages. Several error messages across the panel have been rewritten to be clearer about what went wrong and what the next step should be.
What’s coming next
There is significantly more to talk about next month. The self-serve signup flow is in final development — studios will be able to onboard, connect their Docker Hub repository, and start sessions without any manual steps on our side. More details in the May update.
Questions about any of these changes? Reach out through the admin panel or ping us directly.