piku VS awesome-paas

I like it. I wrote Piku (https://github.com/piku/piku) with much the same interest in fixing some of my pains, so I get where you're coming from with this. Will drop it into one of my current projects to build ESP32 binaries :)

I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).

Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.

I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).

(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)

I automated that away a long time ago: https://github.com/piku/piku/blob/master/piku.py#L814

Piku https://github.com/piku/piku

So, stupid question: why couldn't I just use the 'baremetal' OS provided by Hetzner, install Postgres, Redis & node, create a separate db for each app, and run each app with https://github.com/piku/piku on a different port? For backups, I'll setup crontab to dump dbs locally and to S3.

piku?

Piku https://github.com/piku/piku

Hey there. Firstly, Congratulations on the progress. From the screenshot, I can tell you the UI/UX is great. I have been maintaining Awesome PaaS [1]. Overtime, I have started feeling this space has become commoditised. Because of containers, kubernetes etc. this has been an explosion in the number of tools in the space, however in your case, because of the django/python niche you might have something. In my opinion, very few early stage apps fit into PaaS model, most of the orgs have so much customization that it hard to fit them into your platform. I guess with Django as framework specialization this won't be a problem. Goodluck, with your endeavours.

[1] https://github.com/debarshibasak/awesome-paas

There's been a number of these projects out there. I think the biggest part developers misunderstand when building these is that your target audience either knows AWS enough to build all of this with Terraform / CDK, or they don't know enough about AWS to know which tool they need to use to get done and they use something like Elastic Beanstalk or Amplify. Unfortunately the market for something in the middle is almost non-existent.

You will literally be joining a market that's already over saturated with "Deploy your apps 100x faster/easier/better/safer/secure" platforms. Here's a running list of ones that exist: https://github.com/debarshibasak/awesome-paas

My argument is that most of the small business and startups struggle to make revenue from get go. Asking for revshare, when it is day-0/day-1 kind of situation can hit the startups, small business, individuals really hard.

To me the your model looks very close to a royalty structure. Which is bad on books if you have seen "Shark Tank". It can be a fun place to host apps for indie hackers.

Another argument is that, Major cloud providers give away a lot of credits for various services. It can go upto $100k. I would even argue that you don't need devops or specialized team from you are a small org, startup and your operations are small.

Anyways, Looks like a fun project would love to list you on my Awesome Paas[1] list.

[1] https://github.com/debarshibasak/awesome-paas