[erling]

Have you looked into Erlang/the BEAM VM? It provides many of these same benefits.

> This is cheaper than any other hosting solution in the cloud if you want the same level of stability and isolation.

Erlang provides total process isolation and can theoretically also run on only a single machine.

> It's even cheaper when you need something like a Redis cache. If my cache goes down and the container needs to be spun up again then it's not a big issue, so for cheap projects I can even save more cost by running some infra like a Redis instance as a container too. Nothing beats that.

In Erlang, each process keeps its own state without a single point of failure (ie a single Redis instance) and can be restarted on failure by the VM.

> Kubernetes takes care of itself. A container crashes? Kubes will bring it up.

Erlang VM takes care of itself. A process crashes? The VM will bring it up.

> Do I want to roll out a new version? Kubes will do a rolling update on its own.

Ditto for Erlang VM, with zero-time deployments with hot code reloading.

> I just click ok and everything happens automatically with zero downtime.

Erlang is famous for its fault tolerance and nine nines of downtime! And it’s been doing so for quite a bit longer than K8s.