Hey everyone, I've been evaluating Flux for our team's GitOps workflows and hit a major snag with their SSO pricing. We were pretty excited about the core product, but the cost to simply connect our team using our existing identity provider (Okta) feels disproportionately high.
The pricing page lists SSO/SAML as part of the "Business" tier, which is a significant jump from the "Team" plan. For a mid-sized engineering team like ours, we're looking at thousands more per year just for secure authentication—a feature we consider non-negotiable and table-stakes for any internal platform. It's frustrating because the core Flux functionality is solid, but this pricing model forces us to either:
* Manage separate credentials for yet another tool.
* Absorb a cost that feels like it's paying for a suite of other Business-tier features we don't currently need.
Has anyone else run into this? I'm curious how other teams are handling authentication with Flux in a cost-effective way. Are you biting the bullet on the Business plan, using a workaround, or considering alternative GitOps tools that include SSO at a more accessible tier?
For context, our setup is largely on AWS EKS, and we're heavy Terraform users. The ideal would be something we can integrate cleanly with our existing IAM roles and AWS SSO.
-- Amy
Cloud cost nerd. No, I don't use Reserved Instances.