awesome-paas

Also see - https://github.com/debarshibasak/awesome-paas

Community compiled list of Heroku alternatives. https://github.com/debarshibasak/awesome-paas

We maintain list of PaaS platform out there in the wild - https://github.com/debarshibasak/awesome-paas

My 2 cents, having been in the space for a while and then pivoting out of it. All devops first engineers thinking this is a problem, building something that is more like PaaS but then soon you will realise now not only you have convince engineering managers but also engineers. The total addressable market is fairly small for this type of product, you can throw in compliance guard rails but when an org becomes big they will leave your platform. If you find a customer, you should charge 100 or more as your long value is fairly small. Do checkout the list of PaaS here [1] [1] https://github.com/debarshibasak/awesome-paas

I have been curating list of PaaS, kubernetes abstractions etc. in Awesome PaaS [1]. PS. This space is super competitive. One of the things I have noticed is that the life of an organisation using a platform like this is very short. For example, a startup might use this right away to become compliant and stuff, but once they mature and hire devops engineers, which they will when they hit PMF, they will plan a migration out of your platform. I am wondering how you are planning to counter this behavior. [1] https://github.com/debarshibasak/awesome-paas

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

I wish you luck on your journey with this. We were in the similar space as a YC S20 company - trying to create a Heroku-like experience on AWS. There's been plenty other attempts as well.[1] After working in this space for a couple years, I realized that unfortunately the market just doesn't exist. Small enough teams will typically hack their way through building an MVP and early versions. They don't need/want the complexity of kubernetes/terraform, most literally run their MVP on a couple of instances. On the other side, once you get big enough, you hire dedicated people to start solving these problems. The middle market in between the two is very small and you most likely will be beat by the services already built into AWS such as Amplify. [1] https://github.com/debarshibasak/awesome-paas

I have been very active in the PaaS in your cloud model in past. My analysis leads to the fact that no one has really pulled off heroku in your cloud kind product in recent time. There has been big exits like pivotal et al. Mind you it was before the kubernetes era. Post kubernetes era PaaS in your cloud has become very commoditized. As a PaaS-in-your-cloud (piyc) model as product you are not only competing with other product in the category list here [1] but also the internal platform teams in bigger orgs. Also, it is one of the competitive segment in devtool, devops space. Also having spent over 2 year in the space, I think heroku on AWS is an anti-thesis. I wanted heroku like experience I would start with heroku and not AWS. What you dont know yet is that it is a leaky abstraction as you start acquiring customers and very slow onboardi

The market is actually pretty small for super focussed with PaaS with a specialized business model. Trust me, been there, done that. You have to not only communicate why your PaaS is better than others out there in the market but Also de-mystify why they should adopt your pricing model too. 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 I do not think many orgs and serious startups would like. 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

Yes, miniflare [0] lets you run Workers locally, but I wouldn't treat it to production traffic. There's also Deno, which is very similar in technology to Workers [1]. Others are building "Workers" atop WebAssembly, and things are looking up on that front as well [2][3]. See also: https://github.com/debarshibasak/awesome-paas [0] https://github.com/cloudflare/miniflare [1] https://deno.land [2] https://github.com/suborbital/atmo [3] https://github.com/krustlet/krustlet