I've been self-hosting my projects in VPS / bare metal for years now, using tools like portainer, easypanel, coolify, etc but there was still a lot of work to setup and maintain those. So, out of my own need, I decided to build Grua.
The PaaS is meant to feel like you're using off-shelf products from a big cloud provider (buckets, streams, database, etc) in the sense that it's easy to setup and to use without having to manage servers / containers / scripts.
For example, my biggest pain point was deploying postgres with Point-in-Time Recovery which now, in Grua, it's pretty much a one-click deployment.
There's still a lot to improve there, so feedback is much appreciated. If you wanna try it out, you can use this license:
8e418259-fd13-46cf-bee7-c3a2b63e0227
Grua is free, but it's not open-source (at least not yet).
Why k3s? I run k3s for years now, and it’s great, but sometimes I just want to setup a simple paas that is a single binary in a single server that can potentially scale to multiple servers. But k3s seems like overkill because then I just use k3s, not the paas.
So this is definitely something I’d like to use, if it didn’t have the k8s overhead.
A single binary PaaS that can scale to more than one machine would have to do pretty much what k3s does, so for me it was a no brained decision to get started with k3s.
Also, I want to make it easy to eject Grua from the cluster. For example, if a customer grows beyond Grua, they can eject it to manage the cluster themselves.
I do like your idea tho. I think it has potential for a product of its own, targeting a more skilled audience.
Thanks for the feedback. And if you decide to test Grua out, lemme know what you think
I've been self-hosting my projects in VPS / bare metal for years now, using tools like portainer, easypanel, coolify, etc but there was still a lot of work to setup and maintain those. So, out of my own need, I decided to build Grua.
The PaaS is meant to feel like you're using off-shelf products from a big cloud provider (buckets, streams, database, etc) in the sense that it's easy to setup and to use without having to manage servers / containers / scripts.
For example, my biggest pain point was deploying postgres with Point-in-Time Recovery which now, in Grua, it's pretty much a one-click deployment.
There's still a lot to improve there, so feedback is much appreciated. If you wanna try it out, you can use this license:
8e418259-fd13-46cf-bee7-c3a2b63e0227
Grua is free, but it's not open-source (at least not yet).
Why k3s? I run k3s for years now, and it’s great, but sometimes I just want to setup a simple paas that is a single binary in a single server that can potentially scale to multiple servers. But k3s seems like overkill because then I just use k3s, not the paas.
So this is definitely something I’d like to use, if it didn’t have the k8s overhead.
A single binary PaaS that can scale to more than one machine would have to do pretty much what k3s does, so for me it was a no brained decision to get started with k3s.
Also, I want to make it easy to eject Grua from the cluster. For example, if a customer grows beyond Grua, they can eject it to manage the cluster themselves.
I do like your idea tho. I think it has potential for a product of its own, targeting a more skilled audience.
Thanks for the feedback. And if you decide to test Grua out, lemme know what you think