[halotrope]

Last time I checked it there was a docker-compose file for local deployment but you had to translate that to a working production env on your own. Which would include setting up the database, setting up Kong on edge-gateway, figuring out secrets management, filehosting and updates. One could argue that this is normal hoops to jump through when deploying open source ofc. It just felt way more laborious than the communication suggested. One of the main features the "dashboard" was completely unavailable for self-hosted at the time. So you would not get quite the same experience compared to commercial (again this might be expected for OSS but is a little different from what might have been expected initially ). I just checked and it seems now there is e.g. a (unofficial) k8s deployment plan so it so things might have improved. In general it just felt like it was not the highest priority to get the self-hosted plan up to parity compared to the managed version.

I have no reason to believe that was anything other than the product not being quite ready for the aspirations of the team. There where some comments on on HN that called the Open-Source claims a marketing ploy. I strongly disagree with that notion and believe that the SB team is acting in good faith and that they will deploy some of that fresh capital to further strengthen the OSS story.

Time will tell :)

[pzduniak]

I've recently done the conversion, used Teleport to get access to the dashboard. It works pretty well and I like the fact that I can fork GoTrue / point routes at my own server-side components, rather than just Supabase.

I agree that a proper Helm chart (or a Kubernetes operator) would be ideal. Too bad it would probably also hurt their Cloud offerings.

[SOLAR_FIELDS]

I’ve used the community Helm chart and it’s nowhere near production ready. I had to spend several days configuring it to be usable in production. Which isn’t that big of a deal, but it doesn’t look actively maintained at the moment and could probably use a fork.