Unified CloudOps platform for SRE, FinOps, and Kubernetes operations. It tackles fragmented tooling by providing AI-driven insights and automation for observability, cost optimization, incident response, and runbook execution across Kubernetes and major clouds (AWS, Azure, GCP). The platform streamlines cloud-native environment management for operators.

How It Works

This Kubernetes-native monorepo ingests signals like K8s events, metrics, traces, and cloud scans. It uses LLM-powered agentic planners for incident triage, root-cause analysis, and remediation. Key features include FinOps for resource optimization, ChatOps via Slack/Teams for interactive workflows, and Temporal-orchestrated runbook automation.

Quick Start & Requirements

Local development requires Docker, Go 1.26+, and Node 25+. Clone the repo, run docker compose up -d, configure .env (generate NUDGEBEE_ENCRYPTION_KEY with openssl rand -hex 32), start the Go backend (make run), and the Node.js frontend (npm install && npm run dev). Kubernetes deployment uses Helm (oci://ghcr.io/nudgebee/charts/nudgebee), requiring the encryption key via --set. Access the dashboard at http://localhost:3000 post-installation. Production details are in deploy/kubernetes/README.md.

Highlighted Details

• Unified AI-SRE, AI-FinOps, AI-K8sOps platform.
• Agentic Automation Builder.
• LLM-powered incident triage, root-cause analysis, and remediation.
• Observability ingestion (K8s, cloud).
• FinOps for resource optimization and right-sizing.
• ChatOps (Slack/Teams) for SRE workflows.
• Codified runbook automation.
• Ticketing system sync (Jira, ServiceNow, PagerDuty, Zenduty).

Maintenance & Community

Community engagement occurs via Discord for discussions and coordination. Contributions are guided by CONTRIBUTING.md, with GitHub issues tagged for discoverability. All contributions are licensed under Apache 2.0.

Licensing & Compatibility

Licensed under the permissive Apache License 2.0, allowing commercial use, modification, and distribution without copyleft restrictions.

Limitations & Caveats

The dashboard requires initial integration setup (cloud accounts/K8s clusters) to populate data. Local development specifies Go 1.26+ and Node 25+. Production deployment necessitates consulting separate documentation for advanced configurations.