With automations like 1. Auto-deployment on every commit 2. New environment for every PR on a branch 3. Termination of inactive environments
we provide a unique ability to test PRs among peers, potential customers & users without shooting up your cloud costs.
We have web platform and IDE plugin and a CLI to easily fit into your development workflow.
Even your HN post title suffers from the same issue. I'm getting lost in your language of "ephemeral environments". I get what you mean, but it doesn't suggest what you would do with it until you describe it further.
Yes, they are ephemeral, but that isn't the benefit. "Show HN: Run every PR in it's own environment"
Also, EaaS (ease) has a nice ring to it, I feel like "environments as a service" could also have so many applications, that I wouldn't lead with it.
Could you imagine Stripe describing themselves as "Software as a service. A platform for 3rd party digital purchases". That's kinda what it does, but doesn't really give anybody something to tie it to.
"Modern development platform for fast-moving teams" - but that isn't the problem you solve. I'm part of a fast-moving team, we have a development environment, so what are you offering...
Perhaps there are things that I'm missing. I've never worked in such a large organization where we have independent dev-ops. But is this the pain point?
We have experienced the small bit of pain when reviewing a PR, and you have to stash your current work, open the branch, run the services, etc etc, but it has never been a big enough problem for us.
Perhaps in larger orgs, I don't know. But generally, you may be on to something, but please try to be clearer with what that something is.