Launch HN: Reploy (YC S20) – Instant fullstack staging environments for web apps
It&#x27;s interesting to see this, a couple of months ago I was discussing this idea with a co-worker, we agreed it would be very nice to have it, but costly to build&#x2F;maintain.<p>The conclusion I got was that, we could use deterministic urls (just you like you specify `<a href="https:&#x2F;&#x2F;{repo-id}-{commit}-{service}.reploy.io`" rel="nofollow">https:&#x2F;&#x2F;{repo-id}-{commit}-{service}.reploy.io`</a>), which can get linked automatically on every PR.<p>Every PR could trigger an environment to be created, dropping it after it&#x27;s unused for a given period of time, on every commit, you could get the environment built automatically when you get an user visiting the specific url. This way, you don&#x27;t waste too many resources, I wasn&#x27;t able to find how similar is this to what&#x27;s implemented on Reploy.<p>Something I&#x27;d love to see, is a way to get mobile apps built for these specific environments, it&#x27;s kind of simple for Android, but not so simple for iOS, so that if I&#x27;m trying a specific environment, I can run tests directly from the mobile apps prepared for it. Is there any plan to do this? or any trick to get a similar workflow?<p>What I dislike is the price per seat, as I don&#x27;t see a direct correlation between the number of Github users vs the number of environments, for small companies, it tends to increase the costs a lot, which has prevented me to integrate great tools, I&#x27;d prefer something more related to the number of active environments, so that you can choose the number that works for your team.<p>In any case, looks promising, and of course, wish you success.