(By help I mean just help, not write an entire sloppy article.)
Fundamentally this sounds great, but isn't this rather painful with Postgres?
In my DB lectures in Uni I've been informally told to avoid managing logic from within Postgres, as the development and debugging experience for stored procedures is rather poor. I would add to this the painfully slow development cycles for third party language implementations such as plv8. In addition, platform support is next to none, because language extensions cannot load external code due to the trusted nature of the execution environment.
The way I understand it, the closer the better for the reasons stated, but that's just a factor and there are others that might make you not want to stay too close for certain logic.
I found the part that said "yes open source provides transparency but we have a roadmap" a bit weird.
It's their product, so if they don't want to open source it then they shouldn't. No need to write a silly article with almost as many emojis as words.
If you don't want to pay, you'd have to not use GitHub Actions at all, maybe by using their API to test new commits and PRs and mark them as failed or passed.