Why would it automatically fail just because others have ship their products first? It's always good when new ideas are tried and bring something new to the tab

Why would it automatically fail just because others have ship their products first? It's always good when new ideas are tried and bring something new to the table. Never say never. > I doubt the savings justify additional development complexity. As a cloud provider, your goal is to make your services as easy to adopt as possible. I have been following the news on Unikraft development for a few years now (since 2019 I think) and now fortunately am a beta tester on kraftcloud. I have seen their website and documentation transform from something that only linux kernel wizards would use to what it is now. So definitely they put some work on making sure unikraft is easy to adopt. As the current state of kraftcloud, some apps can already be deployed by copy-pasting the config file (that usually consists of 4 or so lines), install the CLI and hit the deploy button. If you want to enable the scale-to-zero you only need to put -0 at the end of the deploy command. If your use cases not covered in their documentation asking their support or joining the discord is a good start if you don't want to deal directly with the "complexity" (which from my experience mainly consist of copy-pasting some .so files into the root folder).