This page gives insights into our plans for the next few months and where we invest research in the long term. This way, you should be able to better decide on which version of Stormancer you could start projects, with a reasonable confidence as to when a specific feature will be released.

All features displayed here are expected to land with reasonable confidence. We will update this page whenever new data is available.


  • On track

  • Done

  • At risk

  • Delayed

11 Sept. 2015

Control how much CPU & working set resources an app can use on the servers using a web API.

Improved filtering API & Portal UX for logs. Includes category and level filtering, as well as text search.

In the portal, improve the UX of the monitoring tab to make it easier to follow application usage. (Default date intervals, for instance)

Finalize RPC support in the javascript client library:

  • Simplify the API to support binary raw data as well as object serialization
  • Add RPC cancellation
  • Add server peer role in the js client

Add the synchronized clock API in the C++ client

The management portal isn't currently bundled with the game server and must be deployed separatly. This situation complexify the installation of a Stormancer server as most administrators want to benefit from a management web application.

To solve this issue, we are currently adding the web based management portal to the game server in order to let users expose it on a configurable port.

Allow developers to change the scheduler object used by the client to handle network messages and the synchronized clock.

23 oct. 2015

Provides user authentication and user data persistence in Stormancer as an Open source plugin. The plugin is designed with extensibility in mind to add new authentication mechanisms on the long run.

Add RPC to C++ clients

Bug fixing

Run several instances of Stormancer in a single cluster synchronized using Apache Zookeeper to provide easy scale up.

Simple leaderboard plugin

Using Zookeeper for leader election and centralized configuration

Q4 2015

Bug fixing

Send messages to other scenes of the application on the server without having to worry about the node where the scene is running.

Includes support of Send as well as Rpc.

Improve the plugin installation process to let developers easily discover and install plugins in their application.

Let the developer configure a session timeout duration to allow a disconnected player to automatically reconnect to the game.

Open source matchmaking plugin that implements an efficient clustering algorithm to match players of similar skill.


The websocket transport already provides encryption using HTTPS. The Raknet UDP transport doesn't currently do it and it can be problematic when sending sensible data on the network for UDP enabled clients.

We propose an encryption scheme that uses HTTPS to securely exchange symmetric keys between the client and server, then uses these key to optionally encrypt data sent on the network.

Packet size is currently limited to a little less than 90k on Stormancer. Streaming enable the server and client to send binary data of arbitrary size over an arbitrary long period of time.

Run a Stormancer scene on several cluster nodes to create highly scalable worlds.

Allow developers to create replication policies for their scenes in order to provide fast recovery on node failure.

Enable peer to peer connections between players connected to the server, and passing of proxy objects between peers to transparently deal with connectivity, NAT and cross platform issues.