Digger - Open source infrastructure as code management tool

Hello Product hunt - Today we are (re)launching Digger. We have had quite a journey over the last 9 months since the first line of code of the open source IaC management tool was written back in March, and the feedback from PH from our beta launch in May has helped a ton in shaping our roadmap. Let me explain briefly what Digger is - Digger is an orchestrator that helps run Infrastructure code such as Terraform and OpenTofu in GitHub Actions. It does so via helping enable concurrent runs, role based access controls and detection of drift, which are all extremely important for something as critical as production infrastructure. Most tools that help in CI/CD for infrastructure as code do so by duplicating CI functionality, which then requires users to duplicate compute - workers, jobs, etc. The central idea of Digger is that Infrastructure as Code can operate within your own CI systems, like GitHub Actions. This approach means you “use your own compute”, while Digger handles the orchestration aspects, including pull request automation, locking mechanisms, role-based access control, drift detection, remediation, and audit trails. This method cuts additional compute costs significantly and ensures private workers are a standard feature (as compared to being on paid tiers). More importantly, it still allows access to enterprise-grade features like role-based access controls and drift detection through the Digger orchestrator. Do check it out and share your thoughts. We are super hungry for feedback. Feel free to: Book a demo - https://bit.ly/diggerpro Join our Slack - https://bit.ly/diggercommunity For a no pressure walkthrough of the product.

It looks awesome. Congrats Digger team on the launch! 👏

Congratulations to the team on the launch—best of luck! Excited to see how Digger's innovative compute reuse transforms the IaC landscape. 🙌💫

One of the makers here - super excited to launch Digger Pro today! Digger is built upon one simple idea: you shouldn't need 2 ci/cd platforms in your stack. One should be enough! Existing platforms, like Terraform Cloud for example, effectively duplicated it - they run terraform on their servers, with jobs, logs, steps, etc. Digger takes a different approach: it triggers jobs in Github Actions instead, avoiding the duplications. This is: ✅ More secure - because secrets never leave an already high-trust environment of your CI ✅ Much cheaper - you don't need additional compute for private runners With the launch of Digger Pro, we are introducing: 💥 Dashboard - a convenient UI to manage policies and projects across teams 💥 Concurrency - Digger can now intelligently schedule jobs in parallel to speed up plans / applies 💥 OPA policies - check plans and user actions with powerful Open Policy Agent using Rego language 💥 RBAC - granular control who can do what, seamlessly integrated with GitHub teams

Hey there! Your product, Digger, sounds like a fantastic tool for managing Infrastructure as Code. I'm really excited to see it in action when you launch. As someone who is also about to launch their own product, I would love to hear any advice you have for a successful launch. Additionally, once my product is live, I would greatly appreciate your feedback. If you're interested, feel free to click on the "Notify" button to get notified when it's ready. Thank you in advance for your support!

It looks excellent, @nadigerutpal, and congratulations on the launch!!

Big congrats on the launch, best of luck today ♥️🦄

Code management has always been a nightmare for my team 🚀 Congratulations on the successful launch! What's the pricing plan?

Great team and product! Kudos to everyone involved in the launch 🎉🎉

Looks cool. Have only over tried duplicate CI’s for terraform. Would love to try it out