Open source works, until compliance steps in
Reloader OSS is battle-tested and running in thousands of clusters. But when it's part of a regulated environment, the conversation shifts from "does it work?" to "can you prove it?"
These are the questions that OSS alone can't answer
Who It's For
Built for teams who run Kubernetes seriously
Platform Engineering
You need guaranteed compatibility on every Kubernetes upgrade, a stable image channel you can pin, and someone to call when an edge case surfaces at scale.
Security & Compliance
Your auditor wants verified image provenance, SBOMs, and a documented CVE response process. The OSS image alone doesn't give you that paper trail.
SREs at Scale
Reloader sits in the critical path for config and secret rotation. When something breaks during a cert rotation at 2am, you need a human on the other end, not a GitHub issue.
Everything you need for production at scale
Enterprise is a drop-in replacement, same codebase, hardened delivery pipeline.
Capability | OSS | Enterprise |
|---|---|---|
Full Reloader functionality | ✓ | ✓ |
Community support (GitHub Issues) | ✓ | ✓ |
CVE-scanned, signed container image | - | ✓ |
SBOM & artifact provenance | - | ✓ |
SLA-backed support with response times | - | ✓ |
Dedicated escalation channel | - | ✓ |
Security advisory notifications | - | ✓ |
Upgrade guidance & compatibility checks | - | ✓ |
Compliance-ready artifact chain (SOC 2 / ISO 27001) | - | ✓ |
Works with everything already in your stack
Reloader Enterprise is a drop-in component, not a new platform to adopt.
ArgoCD
Annotations strategy avoids triggering unwanted sync diffs during config reloads
Flux
Works alongside Flux reconciliation without introducing config drift
Kustomize
Annotation-based control works cleanly with Kustomize overlays and patches
How it works
Three steps. Zero migration effort.
Subscribe
Choose a support tier based on your cluster footprint and compliance requirements. No per-node pricing surprises.
Pull the certified image
Point your Helm values at the Enterprise registry. Same binary, hardened delivery chain. No manifest changes required.
Get support
Direct access to the Stakater engineering team. Not a ticket queue — a dedicated channel with people who wrote the code.
Common questions
No. It is the same codebase and the same binary. The difference is the image delivery pipeline — Enterprise images are built in a hardened environment, scanned for CVEs, signed with cosign, and shipped with a full SBOM.
Minimal changes only — you update the image registry reference to point to the Enterprise registry. All existing annotations and flags remain identical. Migration typically takes under 10 minutes.
The image and artifact chain supports SOC 2 Type II, ISO 27001, and FedRAMP-aligned environments. We provide the provenance documentation required by most enterprise security audits.
Via a dedicated Slack channel with the Stakater engineering team, with SLA-defined response times based on your tier. For critical production issues, we have an escalation path to the engineers who wrote the code.
Pricing is based on cluster footprint and support tier. There is no per-node or per-pod pricing. Contact sales@stakater.com for a quote based on your environment.
Yes — support-only tiers are available for teams that need the SLA and escalation path but have already addressed image verification through their own pipeline. Ask about this option in the sales conversation.
