HashiCorp Inc.

MongoDB built Atlas, its hosted service, after the self-hosted product got commoditized.

But Elastic, MongoDB, Redis, and HashiCorp all eventually relicensed away from open licenses because cloud providers were hosting their software and capturing managed service revenue without contributing back.

Each relicensing triggered a community fork.

Now, zoom into healthcare.

Wow.

So after Cambodia, you made a major pivot into engineering, moving through Amazon devices, HashiCorp, Smartsheet and Amazon S3.

So what drove that shift and what did working on S3 teach you about building teams and systems at scale? Yeah.

There was a lot in that question.

So if you're running a concurrent Terraform, you will corrupt that cache and have unexpected output.

And that is documented by HashiCorp as well.

The other is that it's only for providers and not for modules.

If you pull modules from a monorepo, for example, that could actually be a pretty big Git clone and be very slow.

logical

super logical yes cool so Mitchell Hashimoto, he is the founder of HashiCorp, and he's the creator of GhostTT, which is the terminal emulator.

Absolute genius guy, super focused on performance.

So a couple of weeks ago, he announced that they are working on something called SuperLogical, which is a terminal multiplexer.

You look at many of the big companies in the 2010 era innovated pretty significantly on their go-to-market strategies.

open source became incredible right with some huge businesses in ways that were entirely novel you look at like Confluent right like who would have thought you could go open source directly into the enterprise or HashiCorp which had six products at IPO only company I know of that had six companies at IPO the only one I know of was Atlassian so it was A breadth angle.

And so I think all the great companies, they find an innovation in an existing market.

There's a technical innovation, but I think more and more, maybe this is the change that I'm coming to, which is the go-to-market innovation is now significantly more important than it was.

If you're leaning too far into pure OSS, you may be forced to monetize earlier than you'd like.

You'll see this happen with companies such as HashiCorp in twenty twenty when they shifted from providing the free CLI to charging for the Terraform cloud offering.

They did so to capture value that enterprises derived from scaling and managing infrastructure at scale.

In the aftermath, HashiCorp had to balance community trust by ensuring the open source version stayed fully functional while also maintaining a revenue path through the cloud service.

A cautionary lesson is that monetization models should evolve as the product matures, not be imposed at inception.

That keeps your offering aligned with customer expectations and preserves openness where it matters most.

And Daniel's counter-argument is sharp.

Why not just use a cloud credential manager? AWS Secrets Manager, Azure Key Vault, HashiCorp Vault.

These already exist.

They already handle rotation, auditing, access control.

And this might happen because, for example, some of our customers actually have said, We love the experience of your local vault so much that we want to now use it as a cloud vault.

And obviously there are many great cloud vault offerings out there, not to mention AWS Secrets Manager, HashiCorp Vault, and like CyberArk, so many others.

But because of the ease of use of 1Password, actually many of our Fortune 1,500 customers have said, I use 1Password Connect, which is an API bridge that essentially presents your local vault as a remote vault in your cloud VPC.

And so when we do that, and there is then the need to decrypt your credentials potentially in the cloud, right? That is why we have built our own confidential computing platform on top of AWS Nitro, which means that as those blobs are being resolved, as those credentials are being decrypted, it's a zero-knowledge architecture.