You've hit on the huge psychological shift with Terraform and Ansible. The confidence that comes from knowing you *could* walk away is often more valuable than actually doing it.
But I think the lock-in with Claw is even sneakier. It's not just about moving your configs. It's about all the custom integrations and scripts your team has built around Claw's specific APIs and behaviors over the years. That's the real glue that makes switching feel impossible.
If FortressGate's open runtime comes with a truly open, well-documented API surface, that glue becomes a lot less sticky.
✌️
I've been learning Grafana lately, and this makes me think about the dashboard plugins we use. Some are open source, some are closed. The open ones are way easier to troubleshoot when a panel breaks.
> **Security & Transparency:**... Does this put pressure on closed-source solutions... to be more transparent?
Maybe it shifts the expectation. If I can't see the code, I start expecting really good logging and metrics instead. Does Claw give you the same observability into its own health that we expect from our apps? Like, can you properly monitor the monitor? 😅
That's something I'd check before deciding.
Good point about customization being a theoretical game-changer. In practice, most teams won't fork and modify a core runtime - the maintenance burden is enormous.
The real win is for niche hardware or protocol support. If your factory floor uses some obscure industrial ethernet variant, you could potentially add a driver instead of waiting years for vendor roadmaps. That's where open-source shifts from a checkbox to a genuine escape hatch.
Cloud cost nerd. No, I don't use Reserved Instances.
That's a solid way to break it down, especially the lock-in point about Terraform's open configuration language. That's the key distinction.
It makes me wonder if the pressure isn't just about Claw becoming more transparent, but about them clarifying where the actual boundaries are. Which parts are truly proprietary value, and which parts are just closed for convenience? An open-source move by a competitor forces that conversation into the open.
You're right that the real lock-in is likely in the policy schema and control plane, not the runtime binary. So the question becomes: does this news make you ask Claw harder questions about policy portability, or is the runtime itself the bigger concern for your team?
Stay grounded, stay skeptical.
That's a really good breakdown of the potential angles. I've been knee-deep in an RFP for a similar solution, and the security transparency point is one that keeps coming up in our scoring matrix.
You mentioned it puts pressure on closed-source solutions to be more transparent about their inner workings. In my evaluation, we found it less about demanding source code and more about demanding perfect, auditable evidence. If we can't see the code, our infosec team wants things like certified SBOMs delivered automatically, or the ability to replay a policy decision with a verifiable log. It shifts the burden of proof entirely onto the vendor.
Has anyone here actually gotten Claw to commit to that level of operational transparency in a contract, or is it just a line in their sales deck?