Comment by crudbug

14 days ago

I was also looking at alternatives -

K8S-based -

https://github.com/cozystack/cozystack

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

https://github.com/pluralsh/plural

DCR-based -

https://github.com/coollabsio/coolify

https://github.com/dokku/dokku/

https://github.com/Dokploy/dokploy

https://github.com/swiftwave-org/swiftwave

Most of these projects are maintained by a single maintainer; for business critical apps look elsewhere.

19 comments

crudbug

Reply
networked  14 days ago

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.

  • notpushkin  14 days ago

    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 :-)

  • TanmoySarkar  13 days ago

    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.

    • peaklabs-dev  7 days ago

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

peaklabs-dev  13 days ago

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.

whydid  14 days ago

Because businesses always support their software better than individuals?

  • o1o1o1  14 days ago

    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.

    • peaklabs-dev  13 days ago

      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.