So do/can users get a preview of the content before being required to make payment? Or is the idea that users are likely already familiar with the site/content to which they will pay? Sorry I only skimmed the article.
Did most of the companies have external facing jump servers? I'd hope at least companies have internal-only and even then with strict internal network access policies (+VPN etc) and ldap authorization etc. Can't imagine that any competent orgs would have externally-facing ssh or windows bastion hosts.
I'm interested in using these images on exe.dev. exe supports any oci images and stands it up as a microvm, in which it would be used non-ephemerally from that point. I'm assuming the images don't have any rc/services. How hard would it be to pull that back in after image deployment? (Also looks like I'd want to use the -dev images which include shell/apk, etc)
Just use Plexus [1]. The maintainer is not trying to be a hero or raise seed dollars or even really trying to promote it. He's just making an excellent, useful product. (Unaffiliated, just a happy user). It's not a full-on "LLMOps" platform (whatever that is), it's just a proxy that works very well and has some nice features.
Kinda sorta analogous to the cloud engineers who can standup complex monstrosities in AWS-land, but don’t know the first thing about how to troubleshoot say a connectivity or simple problem where they have to ssh to an ec2 box and do the needful
Up to 50 VMs with your shared resource pool for $20/mo, just all their unique features like http integrations and Shelley of course is just native, their exeuntu image has everything you need. Build with Shelley, no need to deploy it's already on the VM (tell Shelley to setup systemd to "productionize" it) with a my-vm.exe.xyz url with auto-https via exe's https proxy where you can keep it private to your exe login or make it public (no auth through the exe https proxy).
Pretty sure you could accomplish this in a large physical server or even a huge resource VM (that has KVM passthrough) with some sort of microvm technology? Then that would obviate the need for "multiple cloud instance per coding thread", it would just be a microvm on the large server.
Then again, I'm just the guy running his mouth, and you guys are the ones actually doing the work :)
BTW, looks very polished and thought-through, I may have to still give it a try!
I might use this if it supported any old cloud or VPS, and was at most $10/mo. The fact that you have decided that this platform should only live in your own custom cloud is unappealing to me.
Or, open source it and let us run it on our own VPS and keep your expensive cloud for those who want to pay. As it stands would never consider it.