digger

atures of users that are willing to pay. We have slowly started figuring out the features that people would pay for and we are working hard to onboard our enterprise customers. But a question we repeatedly get asked is: how are you thinking about pricing? Why is it not transparent? The simple answer is that we are still figuring it out. The complex answer, is detailed in our current thesis below: We think that where Digger wins amongst its existing user base is that most “middle tier” features amongst competitors can be used for free either via self hosting the community edition or via using the free automation tier. Digger’s collaboration tier also presents a significant advantage vs competition in that it doesn’t charge “self hosting” tax, and allows users to self host the features available in the collaboration tier at no additional cost. Now coming to the governance tier, Digger allows users to consume the features in this tier via their preferred means, and also has a bunch of governance features such as SSO, Audit trails, log forwarding and private VCS support which are often hard enterprise requirements. We’d love the community’s feedback on this. Both regarding the feature split and on the actual pricing. We've also created a github issue regarding this: https://github.com/diggerhq/digger/issues/1589 [1]: https://handbook.opencoreventures.com/open-core-business-model/#764604b5c6db4107bb…

id purely out of technical considerations - it didn't seem to make any sense to duplicate the CI stack. But it looks like this whole idea behind Terraform Cloud of having an "infra-specific CI" was driven exclusively by commercial interest. You can charge per minute! You can charge even more per resource! Now it's catching up with Hashi; so they have to make such defensive moves. If the product made sense technically, if it was designed the way someone would design it with no commercial considerations whatsoever, they wouldn't have to make such moves.

t all, and it would be a real head scratcher to work out why Atlantis suddenly stopped working! (Loveholidays blog - https://tech.loveholidays.com/enforcing-best-practice-on-self-serve-infrastructure…) 4. “Atlantis does not have Drift Detection.” (Multiple users) 5. “The OPA support in atlantis is very basic.” (Multiple users) As CloudPosse themselves explain (https://cloudposse.com/faqs/why-do-you-recommend-spacelift/) - “Atlantis was the first project to define a GitOps workflow for Terraform, but it's been left in the dust compared to newer alternatives.” The problem though is that none of the newer alternatives are Open Source, and this is what we want to change. Would be super grateful for any thoughts/insights and pain points you have faced.