Hello, and thanks for your comment! There are indeed a few other solutions to this problem. But we haven’t found any with all of the following characteristics:

Hello, and thanks for your comment! There are indeed a few other solutions to this problem. But we haven’t found any with all of the following characteristics: a) doesn’t require access to your private code b) works for any type of app c) doesn’t require buying into kubernetes if you don’t want to d) cheap to run A little digression here but the main trigger for creating this was seeing a post [1] on the Basecamp blog about their implementation of preview envs for their upcoming service: It seemed so convoluted and expensive that surely there was a way to do it with less moving parts (I totally understand that Basecamp may require a complex setup like that, but I’m pretty sure it should remain an outlier). Your comment about Netlify forgetting to remove the deployment link from the GitHub UI once it’s merged is also true, and from my testing Heroku also forgets to remove it. The GitHub deployment API documentation really needs some love, but still surprising since the removal is supported. Regarding domain name provisioning, you can see a few examples in the demos linked from the features page. Currently the pattern is IP-gh-REPO_ID-[pr|branch]-[PR_NUMBER|BRANCH_NAME].my.pullpreview.com. Something I forgot to mention on the features page is that custom domain names are also supported. Custom patterns could also be supported without any issue. [1] https://m.signalvnoise.com/seamless-branch-deploys-with-kubernetes/ https://m.signalvnoise.com/seamless-branch-deploys-with-kube...