The most recent significant discussion of this topic (271 comments 7 months ago) with anecdotal recommendations of several of these:

https://news.ycombinator.com/item?id=41358020 Dokku: My favorite personal serverless platform

Which was nearly immediately preceded by a smaller (62 comments) Coolify discussion also on the front page:

https://news.ycombinator.com/item?id=41356239 Coolify’s rise to fame, and why it could be a big deal

Thanks for the links. I didn't know about SwiftWave.

I have a page with a comparison table of self-hosted PaaS on my site: https://dbohdan.com/self-hosted-paas. It only covers options that don't use Kubernetes. I have just added SwiftWave.

I’m building another one, based on Docker Swarm: https://lunni.dev/

My goal is to build an intuitive, snappy UI that helps you but doesn’t get in your way. Happy to answer any questions and would love to hear what you think :-)

Thanks for adding this.

The core problem of most of the PaaS is the dependency on Swarm (serious workload can't be run on swarm from my experience, disaster recovery too tough).

Working towards building an orchestrator.

We are currently investigating and planning something for scaling not based on swarm, so stay tuned, it may happen soon.

There is also piku, sort of a tiny dokku; https://github.com/piku/piku

This is true for most alternatives, but not for Coolify.

I am the second maintainer of Coolify and Andras and I maintain most of Core Coolify while we have 4 other maintainers helping with support and the docs and a few other maintainers who help with CLI and some other stuff.

Because businesses always support their software better than individuals?

He did not say "companies vs individuals", he said "single maintainer", which is obviously a high risk factor to consider IMHO.

I wonder why they all start their own projects instead of putting their heads together. They could achieve so much more and make a bit more money on the side, while each of them would have to spend less time on it. It would also attract risk-averse companies.

This is true for most alternatives, but not for Coolify. I am the second maintainer of Coolify and Andras and I maintain most of Core Coolify while we have 4 other maintainers helping with support and the docs and a few other maintainers who help with CLI and some other stuff.

The amount of random 1 man opensource projects holding up industries is shocking XD

It's worse for corporate private source projects. Often the docs are lacking and it's essentially a 0-man project.

Second this! I just got hired for a short-term project to extend a payment solution I once wrote when I was employed by that company.

I was amazed to find that a) nobody maintained the project after I left, there were only two minor fixes because their house was on fire, and b) I really took the time to write almost complete documentation on all the important topics, which helped me get back on track faster.

You are absolutely right, and I have experienced this most of the time. The problem is that it is an uphill battle to explain to most stakeholders why you are "wasting" so much time on non-customer facing documentation.

It is hard enough to convince even technical stakeholders (e.g. product owners) to write automated tests.

While at the time I mostly think it's bad, later on it forces them to pay me twice as much, so I guess it's not as bad as I always think in those moments :D

0 man + one accounts dept

Bus factor maybe? Which is mitigated by good community/contributors

What is DCR?

I’m wondering the same thing. Docker Container Registry maybe?

Makes sense.