bentoctl VS klotho

Elastic License 2: https://github.com/bentoml/bentoctl/blob/v0.3.1/LICENSE.md which also applies to their Yatai kubernetes thing, but strangely not (yet?) to the similarly named repo which is Apache-2: https://github.com/bentoml/BentoML/blob/main/LICENSE

Another project in this space is Klotho. I think it's the only one with broad language support so you can write in Go or Python or JavaScript or Java or C#.

https://klo.dev/

I'm one of the creators of Winglang that is featured there as one of the future 4th gen. tool, along with Eventual, Ampt and Klotho.

Hi everyone, we’ve been working on an adaptive architecture engine as part of the open-source Klotho (github), and are now adding an intelligence layer on top of it we call InfraCopilot that features:

Something like this for example: https://klo.dev/

disclaimer: I'm one of the founders

We're building klotho[0] for many of the reasons mentioned here. (happy to answer questions). We transform plain code to cloud native code. The majority of the complexity is moved into the Klotho compiler, and what devs handle is the simplest bundle that's easy to deploy and operate on public clouds using standard tools.

[0] https://github.com/KlothoPlatform/klotho

When I was putting together the pitchdeck for our startup I wanted to search for pitchdeck slides to learn from - but I was looking for specific sections or types of startups for slide decks. To find that one relevant slide, I had to open tens of decks and scroll through them. So I decided to make a tool that would allow me to search inside the decks more easily: SearchTheDeck.com

AWS is heavily invested in its serverless offerings. Every year during re:Invent, they introduce more and more integrations to the already vast toolkit. They know the value serverless brings, specifically for small-to-medium-sized companies. There definitely is a tipping point, where serverless becomes more expensive to run than a more traditional serverful setup, but for most companies, it's at the scale of large enterprises; we're talking a couple of thousand requests per second scale. Tooling is still not perfect but improving every year. Great frameworks, like the serverless framework, chalice and others make it super easy to get up and running with this stack. No need to configure infrastructure details (though I'd always suggest learning the ropes), you can just run a deploy command and you're done. Just to put this into context, even the builders of the Adaptive Architecture (new wave of infrastructure management, e.g. Klotho and Winglang) are prioritizing serverless services on the roadmaps.