Privacy and Security

Robusta was designed with security in mind. Our four guiding security principles are:

  1. Less is more: Don't send mountains of observability data when small subsets of the right data will do.

  2. Secure by default, configurable if necessary: Do the right thing for most companies by default. Make it easy for companies with stricter compliance needs to lock-down Robusta further or run it on-prem.

  3. Design for security: Secure systems are designed to be secure from day one. Discuss security when planning new features.

  4. Experience matters: Hire engineers who have built secure enterprise platforms before. Make security a core part of company culture.

Running Robusta in Airgapped Environments

Refer to Deploying Behind Proxies.

To run the Robusta UI on premise, speak to our team.

Handling Secrets in Robusta's Helm Values

Refer to Managing Secrets.

Limiting Robusta's Access in Your Cluster

To reduce the permissions that Robusta needs in your cluster:

  • On OpenShift you can deploy Robusta with a limited SCC - refer to OpenShift

To further limit Robusta's permissions, speak to our team for guidance.