Applications built with ConfigHub. These are following the DevOps as Apps pattern described here.
- Event-driven Kubernetes configuration drift detection
- Uses ConfigHub Sets, Filters, and bulk operations
- Auto-corrects drift by updating existing units (not creating new "-fix" units)
- Real-time dashboard on :8080
- Claude AI integration for drift analysis
- Full ConfigHub deployment pattern with push-upgrade
- AI-powered cost optimization with Claude
- NEW: OpenCost integration for real cloud cost data (vs estimates)
- Web dashboard on :8081 with Claude API history viewer
- Metrics-server integration for real resource usage
- Uses Sets for grouping recommendations
- Push-upgrade for promoting optimizations across environments
- Pre-deployment cost analysis before units are applied
- Monitors all ConfigHub spaces for cost impact
- Trigger-based hooks (pre/post deployment)
- Web dashboard on :8083
- Self-deploys through ConfigHub
- Complements Cost Optimizer (monitor = pre-deployment, optimizer = post-deployment)
Each example has complete setup instructions in its own README:
# Example: Drift Detector
cd drift-detector
cat README.md # Full setup guide
# Or use the QUICKSTART.md for fast setup
cat QUICKSTART.md- ConfigHub account - Sign up
- ConfigHub CLI -
brew install confighubai/tap/cub - Kubernetes cluster - Kind, Minikube, or cloud provider
- Claude API key - Get one
- Go 1.21+ - For building from source
- DevOps as Apps Architecture - Full explanation of the pattern
- Canonical Patterns - ConfigHub best practices
- ConfigHub SDK - Reusable library used by all examples
All examples follow the same structure:
- Deploy via ConfigHub (not kubectl)
- Environment hierarchy: base → dev → staging → prod
- Event-driven with Kubernetes informers
- Claude AI integration
- Push-upgrade for promotions
- ConfigHub Sets and Filters for bulk operations
See each example's README for detailed architecture and deployment instructions.
Proprietary - ConfigHub, Inc.