kubero VS otomi-core

For deploying your apps you could use something like Kubero (https://github.com/kubero-dev/kubero)

Repository: https://github.com/kubero-dev/kubero

Are you running Kubero in the background? Zeabur seems to have the same feature set, and Add-ons.

However, because I want to offer an MTA as an add-on for Kubero, my Heroku alternative, I have decided to create one with Haraka. Haraka is a well-known MTA and is used by Craigslist. This MTA is very flexible and can be extended with plugins. It is also highly performant and can run on minimal resources. Another important criterion is that it has been well maintained and developed for a long time.

I'm the maintainer of Kubero, which is pretty similar but requires a Kubernetes cluster, which might be a show-stopper in your case. But apart from that, Kubero would be able to fulfill your requirements:

Probably kubero

I'm self-hosting Heroku with Kubero.

An example of a self-hosted Kubernetes-based PaaS is Otomi. Install Otomi on your Kubernetes cluster, compose your platform (by activating the required capabilities) and build, deploy and expose apps in just a couple of minutes. Heroku, but Kubernetes native and running on your own cluster.

This video shows some of the new features of Otomi version 0.19.0 that will be released in Week 11 2023. Follow us on GitHub and be the first to try it out: https://github.com/redkubes/otomi-core

Otomi

Kubernetes is 'only' a multi-node cluster kernel. Some call it the Linux of the cloud.

And because K8s is only a kernel, there are now over 2000+ (open source) projects, all adding some extra functionality to it. Be it for observability, security, or networking. But all of these projects don't really collaborate and end-users don't ask for maturity of individual projects, they want sets/stacks of projects that integrate well.

Now every company has created some Stack with applications and configurations for Kubernetes, all trying to reinvent the wheel and spending an often shocking $ in doing so.

So here is my take:

- Let's create a new category in the Cloud Native Computing Foundation (CNCF) landscape and call it Integrated Stacks for K8s

- To be accepted, a stack needs to provide an open integration framework for other projects to add/integrate their apps

- Just like aLinux distro, each stack is ideal for some specific use case(s)

- A stack can be installed in one run, contains integrated apps that work out-of-the-box, has a (web) UI that acts as a desktop environment to provide easy and secure access to all features. Call it a new user experience for Kubernetes

Wouldn't it be great to have a list of all Kubernetes stacks available that everyone can use (and contribute to)? Just like (in the Linux analogy) you can choose between Linux Mint, Fedora, or Ubuntu.

We already created the first: https://github.com/redkubes/otomi-core