I'm from Gruntwork; we're the maintainers of Terragrunt.
We get this question a lot because Terragrunt did in fact start as a feature shim for Terraform. But that was a long time ago and Terragrunt has evolved into a first-class "orchestration" tool for Terraform or OpenTofu.
We're on a mission to transform the way DevOps is done. The status quo for creating and managing infrastructure is still a terrible experience for most organizations, and we'd like to change that by creating a next-generation DevOps platform.
Gruntwork is globally recognized both for our open source tools (Terragrunt, Terratest, Cloud Nuke) and our thought leadership (blog.gruntwork.io, books). Now we're looking for the following Grunts:
- Senior Product Marketing Manager. Lead all marketing at Gruntwork, mostly product marketing and some demand generation.
- Senior DevOps Solutions Engineer. Lead customer success at Gruntwork. Activate our customers, and help support them.
- Senior Sales Engineer. Be the technical advisor to prospective customers as they evaluate Gruntwork.
We're on a mission to transform the way DevOps is done. The status quo for creating and managing infrastructure is still a terrible experience for most organizations, and we'd like to change that by creating a next-generation DevOps platform.
Gruntwork is globally recognized both for our open source tools (Terragrunt, Terratest, Cloud Nuke) and our thought leadership (blog.gruntwork.io, books).
Now we're looking for staff-level product engineers to help us build out our vision.
Our stack includes Go, Python, Bash, NextJS/Node, Terraform/OpenTofu, and new tools as needed. You'll work directly with the CEO/co-founder, Head of Product, and Head of Product Design to build a great product.
OpenTF core member here. If you're comfortable opting into an ecosystem where most of the key products are offered and supported by a single vendor (in this case, Hashicorp), then yes, there are no licensing issues to worry about and basically nothing needs to change for now.
But our philosophy at OpenTF is that users would rather participate in an open ecosystem where multiple vendors compete for their business. If you're not happy with one vendor, you can easily switch to another; competition works to make all vendors better.
When we look back at this comment a year from now, I'll wonder how your company will feel about the responsiveness and new features they're getting from Terraform Cloud when the primary incentive to stay is not because you think it's the best product available, but because switching costs are so painful.
OpenTF core member from Gruntwork here. All great products require focus, and right now our sole focus for OpenTF is creating the best possible truly open source and community-driven successor to legacy Terraform.
I'd personally love to see an open source path forward on other products that Hashicorp re-licensed like Packer, but those will need to be a separate project and initiative.
OpenTF core member here. To build on this comment, we've tried to intentionally focus on positively meeting our needs, not on negatively villifying another company for trying to meet their needs. You can see a good example of this in https://github.com/opentffoundation/manifesto/issues/165#iss....
We do not fault HashiCorp for trying to build a thriving business and we respect their amazing achievements and contributions. However, on this one issue of the Terraform license, we do not agree with their position and believe strongly in the need for a truly open source, community-driven Terraform.
Your main pitch is on open source standardized contracts and that definitely resonates, but as a current Ironclad user where they’re our single-most expensive SaaS subscription, your contract lifecycle management system built for startups is what resonates for me.
Do you plan on offering migration services from Ironclad? That would amount to importing our workflows and repository.
We package DevOps and AWS best practices to make them available for easy use by DevOps teams. Ultimately, we enable our customers to launch and manage production-grade cloud infrastructure in days, not months, all backed by IaC the customer controls.
Tech stack: Go, Typescript, React/Next, Bash, Python, AWS, K8s, Terraform. We’re a small team (~20 people), but our clients include Toyota, Adobe, TicketMaster, Verizon, and lots of startups.
We are profitable, self-funded (no investors, no debt), pay salaries, equity, and bonuses according to transparent formulas, and are very focused on building a company we're proud of. We are 100% remote, with 2/3 of our team in the USA and 1/3 in Europe. We have company-wide in-person meetups every few months. We welcome applicants from all backgrounds.
We're looking for a principal product manager to serve as the lead on 3 key Gruntwork products:
- Gruntwork Library
- Gruntwork Pipelines
- Gruntwork Reference Architecture
Gruntwork | Software Engineers (Principal, Staff) | 100% Remote/US time zones | Full-time | https://gruntwork.io/careers
We aim to improve humanity's most important invention: Software. Our product packages DevOps and AWS best practices and makes them available for easy use by devs. Ultimately, we enable teams to launch and manage production-grade cloud infrastructure in days, not months, all backed by IaC the customer controls.
Tech stack: Go, Typescript, React/Next, Bash, Python, AWS, K8s, Terraform. We’re a small team (~20 people), but our clients include Toyota, Adobe, TicketMaster, Verizon, and lots of startups.
We are profitable, self-funded (no investors, no debt), pay salaries, equity, and bonuses according to transparent formulas, and are very focused on building a company we're proud of. We are 100% remote, with 2/3 of our team in the USA and 1/3 in Europe. We have company-wide in-person meetups every few months. We welcome applicants from all backgrounds.
We're looking for principal-level engineers to help us execute on an ambitious set of next-generation products.
Gruntwork | Software Engineers (Principal, Staff) | 100% Remote/US time zones | Full-time | https://gruntwork.io/
We aim to improve humanity's most important invention: Software. Our product packages DevOps and AWS best practices and makes them available for easy use by devs. Ultimately, we enable teams to launch and manage production-grade cloud infrastructure in days, not months, all backed by IaC the customer controls.
Tech stack: Go, Typescript, React/Next, Bash, Python, AWS, K8s, Terraform. We’re a small team (~20 people), but our clients include Toyota, Adobe, TicketMaster, Verizon, and lots of startups.
We are profitable, self-funded (no investors, no debt), pay salaries, equity, and bonuses according to transparent formulas, and are very focused on building a company we're proud of. We are 100% remote, with 2/3 of our team in the USA and 1/3 in Europe. We have company-wide in-person meetups every few months. We welcome applicants from all backgrounds.
We're looking for principal-level engineers to help us execute on an ambitious set of next-generation products.
Gruntwork | Software Engineers (Senior, Principal, Staff) | 100% Remote/US time zones | Full-time | https://gruntwork.io/
At Gruntwork, we aim to improve humanity's most important invention: Software. Our product enables software teams to launch and maintain production-grade cloud infrastructure in days, not months.
We create the building blocks that devs and DevOps engineers can use to make launching in the cloud 10x better / faster / easier. We think of our work as creating a new paradigm for how DevOps can be done, one that leverages the insight that many companies re-invent the foundations that software engineers need to build and launch their apps. We work with AWS, K8s, Terraform, Go, Typescript, and React, and introduce new tech as needed. We’re a small team (~20 people), but our clients include Toyota, Adobe, TicketMaster, Verizon, and lots of startups.
We are profitable, self-funded (no investors, no debt), pay salaries, equity, and bonuses according to transparent formulas, and are very focused on building a company we're proud of. We are 100% remote, with 2/3 of our team in the USA and 1/3 in Europe. We have company-wide in-person meetups every few months. We welcome applicants from all backgrounds.
Our measure of a successful Grunt is (1) think like an owner, (2) make impact, (3) communicate effectively, (4) be a good person. If this sounds like you, we're hiring!
(This is my second feature request on this thread; apologies for any noise.)
Stripe Billing helpfully allows you to set the original subscription start date to a past date, but only at subscription creation time. If we could modify the subscription start date, then Stripe could be authoritative for when 100% of our subscriptions actually started.
We use Stripe Billing and it's gone very well overall, but the biggest miss for us is that Stripe conflates "contract term" with "billing frequency." We sign up customers for annual contracts but bill them monthly, but Stripe Billing only understands the "bill monthly" part of that.
Are there any plans for first-class contract term support coming?
I really appreciate these suggestions. We're a fully bootstrapped ~20 person, $5M+ ARR company in the DevOps space. We're growing quickly and often wonder what an extra $1.5 - $3M could mean for us, but don't want the overhead associated with a traditional investor, nor to invest the time in raising. We get emails from 3 - 4 VCs per week, but never any alternative funding options like the ones you listed. CalmFund in particular could be worth exploring. I wish this space ("Tech Mittelstands"?) were better established.
At Gruntwork, we aim to improve humanity's most important invention: Software. Our product enables software teams to launch and maintain production-grade cloud infrastructure in days, not months.
We create the building blocks that devs and DevOps engineers can use to make launching in the cloud 10x better / faster / easier. We think of our work as creating a new paradigm for how DevOps can be done, one that leverages the insight that so many companies re-invent so much of the foundations that software engineers need to build and launch their apps. We work with AWS, K8s, Terraform, Go, Typescript, and React, and introduce new tech as needed. We’re a small team (~15 people), but our clients include Toyota, Adobe, TicketMaster, Verizon, and lots of startups.
We are profitable, self-funded (no investors, no debt), pay salaries, equity, and bonuses according to transparent formulas, and are very focused on building a company we're proud of. We are 100% remote, with 2/3 of our team in the USA and 1/3 in Europe. We have company-wide in-person meetups every few months. We welcome applicants from all backgrounds.
Our measure of a successful Grunt is (1) think like an owner, (2) make impact, (3) communicate effectively, (4) be a good person. If this sounds like you, we're hiring!
- Senior Software Engineer
- Senior Software Engineer (Contract, Part-time)
- Director of Engineering
- VP of Engineering
Naive but genuine question: What are the major advantages of switching to an ARM processor? From Apple’s keynote, I gathered that there’s the benefit of instant-on, and allowing iPhone/iPad apps to just work in MacOS, but are there some other fundamental advantages to be had with ARM for Mac? What difference does it make for both power users and real consumers at the end of the day?
What you're missing is that there's overhead in writing CSS-in-JS. You have to switch context from HTML to JS, you have to keep track of the "link" between your CSS-in-JS and your React component, you have to deal with cascading styles, and hopefully you're able to keep all styles across all components consistent.
Tailwind cuts through all of that and says:
- Just declare the styles you want directly in the HTML
- If you're repeating styles, use @apply
- Limit the number of styles available to your project to enforce a de facto design system
We get this question a lot because Terragrunt did in fact start as a feature shim for Terraform. But that was a long time ago and Terragrunt has evolved into a first-class "orchestration" tool for Terraform or OpenTofu.
We wrote a blog post addressing exactly your concern that you might find helpful: https://blog.gruntwork.io/terragrunt-opentofu-better-togethe....