FeaturePeek cofounder here! Glad to see others in this space :-) Yes, our use case is mostly geared towards frontends devs getting design and product feedback f

FeaturePeek cofounder here! Glad to see others in this space :-) Yes, our use case is mostly geared towards frontends devs getting design and product feedback from their team. Right now we only spin up frontends (both pure static and Docker-based architectures, which you can of course point to backend services you host), and run in the public cloud (so not tied to your existing infra). By default, environments are private, so only the people you whitelist can access them. On top of that, we overlay tools that let you comment w/ screenshots and screen recordings, and file tickets on third-party integrations. We also have other neat usability wins, like each repo getting its own subdomain (rather than each pull request) so that you don't have to re-login to your app for each environment that spins up.