kkgupta

3 ms·

1. 1.▲
   by kkgupta 2mo ago

   The operational challenges that you highlighted with BYOC makes sense and they need to be addressed. - On upgrades, agree that “vendor managed” shouldn’t mean “the vendor can push arbitrary code whenever it wants” especially with the supply
2. 2.▲
   by kkgupta 2mo ago

   One nuance on the air-gapped / shrinkwrap end of the spectrum that I was thinking about afterward is that there is a difference between “no connection back to the vendor” and “just ship binaries and scripts.” One can also imagine shipp
3. 3.▲
   Ask HN: How are you operating OSS AI infrastructure?

   3 points by kkgupta 2mo ago|0 comments
4. 4.▲
   BYOC Anywhere: The Spectrum of Bring Your Own Cloud Deployments(omnistrate.com)

   80 points by kkgupta 2mo ago|16 comments
5. 5.▲
   AI Is Breaking the SaaS Deployment Model: 10 Commandments for BYOC(byocanywhere.org)

   11 points by kkgupta 2mo ago|0 comments
6. 6.▲
   How are you operating AI infrastructure in production?

   6 points by kkgupta 2mo ago|0 comments
7. 7.▲
   Control Plane: Operating System of Software Distribution(blog.omnistrate.com)

   6 points by kkgupta 1y ago|0 comments
8. 8.▲
   Developer platform to build your Software Distribution(blog.omnistrate.com)

   14 points by kkgupta 1y ago|0 comments