Developers

Show your branch running, not describe it

Push a branch and get a running environment with its own URL, without asking anyone for one.

Before Fenwave2 days waiting

“Hey, could someone spin me up a test env for feature/checkout-v2? Need it for the review tomorrow 🙏”

What the wait costs

The review happens on a screenshot. The bug that only shows up under real routing is found in staging, a week later.

With Fenwave90 seconds

In Fenwave

Environments›Dev›feature/checkout-v2

Capability

Environment Manager

The branch is already the unit everyone reasons about — it is what the pull request is opened from and what the reviewer reads. Fenwave makes it the unit of deployment too. Push, and a namespace is provisioned with its own hostname; paste that hostname into the pull request and the reviewer clicks instead of imagining.

How it works

01Push a branch to a repository Fenwave watches.
02Fenwave provisions an isolated Kubernetes namespace and builds the branch into it.
03A unique URL is generated and shown on the environment card.
04The environment sleeps after two hours idle, so an unused preview costs nothing.
05When the branch merges, the namespace is deleted automatically.

Related use cases

QA & test engineers

Test a build that will still be there in an hour

Your own environment per branch, so nobody redeploys under you mid-campaign.

every sprinton demandEnvironment Manager

Product managersNo console needed

Click the feature before the sprint review

Every branch has a URL. Open it, try the flow, leave feedback while it is still cheap.

until stagingsame dayEnvironment Manager

DevOps & SRE

Stop paying for environments nobody opened this month

Idle previews sleep after two hours and delete themselves when the branch merges.

indefinitelyautomaticEnvironment Manager