Helm Charts for Stigg Sidecar and Persistent Cache Service - Stigg

We’re excited to share that we’ve released official Helm charts for deploying the Stigg Sidecar, Persistent Cache, and Redis together in your Kubernetes cluster.

🆕 What’s New
You can now deploy the full Stigg runtime stack using Helm, including:

Stigg Sidecar - running alongside your app or as a standalone service for low latency, resilient entitlement checks
Persistent Cache Service - for streaming entitlement updates into your Redis storage
Redis - for local storage when persistent cache is enabled
An end-to-end example app - showing how all components work together

The repository includes everything you need to get started, from a complete example chart to Kubernetes manifests, TLS setup guidance, and production-oriented configurations.

💡 Why It Matters
These charts give you:

A repeatable and production-ready way to deploy Stigg components on Kubernetes
Built-in support for API key management, autoscaling, resource limits, and secure Redis communication
Example manifests and templates that make it simple to integrate Stigg into existing workloads

Whether you deploy on EKS, GKE, AKS, or local tools like minikube or kind, the charts help you bring Stigg into your infrastructure with minimal friction.

📦 How to Get Started

Clone the stigg-helm-charts repo
Follow the instructions in README.md for either the Helm or the Kubectl + Kustomize deployments.