I agree with many of these points, here are some thoughts on how we deal them:

> Most enterprises are wary of handing over control to a vendor

Great point, we do have the Enterprise version, which is self-hosted.

> Do you find a lot of Lisp/Clojure devs out there for when you need to expand?

We won't hire engineers based on the language they know, but instead in general engineering skills, and they can learn Clojure here (already worked for the first one:)

> You still have to audit those things

Yes we do, but mostly to trigger alerts if anything happens there and to show that the accesses are either from Runops or the applications during audits. This is way lighter than relying on these as the source of truth for trails.

I'm curious about the Change Management features you think are missing. We do have review workflows and other CM-related features I didn't add here, this demo shows some of it: https://see.runops.io/videos/demo

That's great, I didn't know about the Enterprise version. I'll look closer at this and see if it fits our use cases. (fyi, the more docs we can read [esp. operational docs, but also technical], the more likely we are to push for adopting this in our enterprise)

Here's some of the things a typical IT CM process handles: How do you properly surface and acknowledge the risk & impact of a change? What are the order of operations & how do you track them? How do you validate an operation? Roll back? Are there governance structures in place (X team can run Y task in Z environment)? With multiple stakeholders, how do you get approval from everyone, or handle change overrides? How do you run 'almost' the same thing in different environments? Do you use multiple communication/coordination methods, like e-mail, MS Teams, Slack w/multiple workspaces/orgs, Zoom, Jira, ServiceNow, etc? Is there a "change plan" which is drafted, edited, published, approved, and executed, in coordination with multiple teams?

All that may be overkill for your tool, but it's some of the stuff I would need to build around it to use it in my enterprise. Otherwise I (the ops guy) would need to build & run all those steps and coordinate with others when it's time for them to perform their steps (release, validation, debugging, rollback, etc).

This is great, thanks for sharing! We handle most of these in Runops itself, but you can also use your existing CM tool and leverage only the UX and automations from Runops. We have APIs and webhooks that enables you to extend Runops, one company is doing this and integrating Runops to ServiceNow.