You store your markdown files locally and then copy them to your hosted blog.
> They start out great but as financial constraints creep in
Funny how you talk about financial constraints, and still refuse to pay for software.
Their stack is primarily comprised of other independent open source projects. The one component that isn't is their "realtime" server that serves updates from postgres' WAL over websockets, but that is open sourced[0] under Apache 2.0. From my understanding the primary part that has not been open sourced is their database browser / web UI. There are plenty of alternative management tools for postgres though. As you can export your database what else would you need to ensure your portability and independence?
Granted they make their docs fairly opaque for trying to self host. Presumably to encourage you to just use their hosted service. Hosting open sourced projects seems like a very ecosystem friendly way of monetizing.
(The dichotomy between "I must earn a gazillion dollars because I'm a senior dev" and "I will not pay money (that pays those salaries) for software" that's so prevalent on HN is mind boggling)
- development costs money
- workplaces cost money
- people want to eat
You can pay for Plex with money (Plex Pass). And while I sort of dislike them pushing their own content and monetization, it can be easily switched off in settings.
FYI, this is also open source: https://github.com/supabase/supabase/tree/master/studio
As long as they have something to keep them above poverty line: https://staltz.com/software-below-the-poverty-line.html (among other articles, the question of how free open source isn't sustainable is discussed often)