Skip to main content

Hybrid Deployments

Rookout's hybrid SaaS architecture empowers customers to keep application data within their premise by separating the control plane from the data plane.

Keeping the control plane connected to the Rookout cloud retains the benefits of SaaS: ease of use, ease of maintenance, live updates, etc. Keeping the data plane on-premise simplifies data governance concerns and is useful for a variety of security and compliance considerations.


Rookout hybrid architecture relies on two containers to process, store, and access application data:

  • The controller acts as a proxy, optimizing network traffic and offloading processing from the monitored applications.
  • The datastore is an in-memory cache making the data available for end users over a secure web endpoint.

Hybrid Architecture


When using the hybrid architecture, configure your agents to connect to the relevant controllers:

export JAVA_TOOL_OPTIONS="-javaagent:$(pwd)/rook.jar -DROOKOUT_TOKEN=[Your Rookout Token] -DROOKOUT_CONTROLLER_HOST="wss://your-controller-host"

If you forget to set the Rookout controller host you will be unable to set breakpoints. You'll see the following error: "Agent attempted connection to SaaS."


In the hybrid architecture processing and transmitting data to external targets is carried out by the controller.


Deploy using common infrastructure as code providers: