Some context here is that our launch is mainly to developers. Other users can't even sign up from the website or use the product without self-hosting. In any case, we'd still need to post a link to Github, somewhere.
If you're saying it's ok to post a Github link to a non-open source project, but just not as the main URL, I'd understand, but I still feel that in our specific case, the Github link is the least friction path to set up for self-hosting. I think a developer who goes to a marketing site and doesn't easily find way to setup/self-host would be more frustrated.
> I think a developer who goes to a marketing site and doesn't easily find way to setup/self-host would be more frustrated.
In that case the marketing site should probably be fixed.
"If it can be self-hosted, it has to be on GitHub" is a really weird claim, considering that tons of "self-hosted" open source projects aren't on GitHub. debian.org, for instance.
Also, I personally wouldn't call something that requires an external backend API (if I'm understanding this correctly?) "self-hosted". Partially self-hosted? Not sure. It's not exactly on prem either.
If you're saying it's ok to post a Github link to a non-open source project, but just not as the main URL, I'd understand, but I still feel that in our specific case, the Github link is the least friction path to set up for self-hosting. I think a developer who goes to a marketing site and doesn't easily find way to setup/self-host would be more frustrated.