Skip to main content
An Environment is the unit of scope in RubixKube. One Kubernetes cluster, one AWS account, one GCP project, or a group of Linux VMs. A workspace can hold any mix, and every part of the product (Chat, Insights, RCAs, Actions) respects that scope. Environments are how you connect infrastructure once and then work against it forever. Add one, you get the full loop. Add another, they correlate automatically.

​
What counts as an environment

Kubernetes cluster

One EKS, GKE, AKS, KIND, or bare metal cluster. Everything inside the cluster (pods, deployments, nodes, services) belongs to the environment.

AWS account

One AWS account. EC2, RDS, Lambda, S3, ELB, CloudTrail, CloudWatch all flow into the environment’s graph.

GCP project

One GCP project. GCE, GKE, Cloud SQL, Cloud Run, Cloud Storage, Cloud Functions.

Linux VM (or group)

A host or a defined group of hosts. CPU, memory, disk, network, and per-process signals per host.

​
Multi-environment workspaces

A workspace is the top-level container. Inside it you can mix environments freely. A representative setup might look like:
  • One prod-eks Kubernetes environment.
  • One staging-gke Kubernetes environment.
  • One rds-backbone AWS account for shared data services.
  • One observability-vms group of Linux hosts running your own tooling.
All four feed the same Knowledge Graph. All four contribute to the same Memory Engine. A chat question like “what changed in payments in the last hour” spans them. An RCA that starts on a Kubernetes pod can pick up correlated signals from the AWS account automatically.

​
Environment properties

Every environment carries a small set of properties that shape how RubixKube works against it.
PropertyPurpose
NameHuman-readable label used across the product
TypeKubernetes, AWS, GCP, or VM
CriticalityLab, Dev, Staging, Prod. Influences default severity thresholds
Guardian policyWhich actions are approvable, by whom, with how many approvers
Notification rulesWhich channels receive which events from this environment
RetentionHow long signals, insights, and RCAs for this environment are kept
Redaction rulesPatterns that strip sensitive content before signals ship to the Cloud

​
How environments scale

1

One environment

You see the full shape of the product immediately. Topology, insights, chat, RCAs, actions.
2

Two to three environments

Cross-environment correlation starts paying off. Chat answers questions that span environments automatically.
3

Tens of environments

Enterprise workspaces segment through environment tags (team, region, criticality). Notifications, severity thresholds, and policies apply by tag.

​
Environment criticality, in practice

Criticality is more than a label. It changes defaults across the product.
Guardian policies can auto-approve low-risk Actions. Insights default to Low severity unless the signal is severe. Retention follows the free-tier minimum.
Guardian requires a single approver. Insights default to Medium. Notifications go to team channels, not on-call.
Guardian requires a single approver. Stricter thresholds. Notifications go to team channels with a lower volume threshold.
Guardian requires two approvers for non-trivial Actions. Insights default to High or Critical where merited. Notifications can escalate directly to on-call.
These defaults are starting points. Every environment’s policy can be tuned individually.

​
Common questions

Free tier allows one. Business allows up to three. Enterprise is unlimited. See Pricing.
Yes. Any pair of environments in the same workspace share the Knowledge Graph. Chat, RCAs, and Memory queries can span them without configuration.
Yes. Tag environments with arbitrary labels (team, region, criticality, owner). Notifications, dashboards, and chat filters can scope to any tag set.
The environment card shows degraded state. The Observer queues collected signals locally (bounded buffer) and catches up when connectivity returns. Cloud-side data and RCAs remain available; new ingestion pauses.
Yes. Deletion removes active ingestion. Historical signals, RCAs, and Memory entries stay retained per plan. You can reconnect the same environment later and the history links up automatically.

Observer Agent

The component installed per environment.

Environments in the console

How to manage, tag, and configure environments day to day.

Connect your environment

How to onboard a new environment.