Qovery Engine – open-source multi-cloud deployment

They call CLI(s) really? I'm curious on how error handling is done when you don't call an API. Funny enough all the CLI they call are written in Go.

Overall it seems badly designed, so one of the 3 cloud you picked-up did not work for whatever reason, what is the state of your deployment, 2/3? Can you reconcil? It looks like fire and forget, not very applicable in a real scenario.

Interesting to see more competitors to Heroku popup. Kind of amazing how the big cloud providers still haven't solved this problem.

Heroku still has one of the easiest setups of anyone on the market, and they've just been coasting in recent years. Poor container support, auto-scaling is naive, random routing (see rap genius), no health checks, pricey, etc.

Previously Deis built a Heroku like service on top of Kubernetes, but they got acquired by Microsoft, and the product has since atrophied.

Convox[0] seems similar to Qovery, with the added ability of self-hosting (UI is closed source though).

I think Qovery not having a UI is a deal breaking for many. Heroku's CLI, UI, and API is a killer combo.

[0]: https://convox.com

I cant wait for some desired-state engine to be built on top of this. This is nearly perfect but having it so you can just describe this as json/yaml (and then generate those from your own abstractions) instead of using Rust to describe these will be amazing.

It reminds me the recently released Hashicorp's https://www.waypointproject.io/ . Does it solve the same/similar problem?