(no title)
crudbug | 11 months ago
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.
password4321|11 months ago
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
networked|11 months ago
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|11 months ago
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|11 months ago
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.
frainfreeze|11 months ago
peaklabs-dev|11 months ago
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|11 months ago
o1o1o1|11 months ago
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.
cchance|11 months ago
edoceo|11 months ago
theanonymousone|11 months ago
selexin|11 months ago