Currently working on an open source Heroku / Fly.io / Render alternative: https://canine.sh
Its built on top of Kubernetes, based on learnings I've had from previous experiences scaling infrastructure.
If you look at the markup PaaS (Heroku, Fly, Render) applies to IaaS (AWS, Hetzner), it's on the order of 5-10x. But not having that, and trying to stitch together random AWS services is a huge PITA for a medium sized engineering team (we've tried).
On top of all that, theres a whole host of benefits to being on kubernetes, namely, that you can install any helm package with one click, which Canine also manages.
A good example is Sentry -- even though it has an open source offering, almost everyone pays for the cloud version because its too scary to self host. With Canine, its a one click, and you get a sentry.your-domain.com to use for whatever you need.
Recently got a sponsorship from the Portainer team to allow me to dedicate way more time to this project, so hugely grateful to them for that.
cool! how does this compare to dokploy? same niche or are there important differences?
I'd say the biggest difference is in the backend -- canine is built on top of kubernetes, which is what lets it leverage the rich ecosystem of tooling and packages. Kubernetes has a reputation for being difficult to use, and so Canine tries to be super opinionated, and follow a set of best practices.
I'd like to think at this point (about 2 years into development) we've gotten to a place where the end user doesn't even know they are using Kubernetes.