Skip to content
All use cases
Developers

Be productive on day one, not week two

One CLI login sets up the local environment; the dashboard shows what is running.

Before Fenwave4 days waiting

“The README says Node 16 but the lockfile wants 20, and the docker-compose references a registry I cannot reach. Who owns this?”

What the wait costs

A new hire’s first week spent reverse-engineering setup, and a senior engineer’s week spent answering it.

With Fenwave20 minutes

In Fenwave

Tools›Local Setup›fenwave login

Capability

Fenwave Agent & DevApp

Onboarding time is a platform metric that hides in plain sight. The Fenwave Agent installs from the Local Setup page, authenticates with the same account as the web platform, and starts a local dashboard on localhost:3003 covering containers, images, volumes, registries, logs and terminals. The new hire sees the same view as the person helping them, which is most of what makes remote onboarding hard.

How it works

  1. 01Install the agent from Tools › Local Setup.
  2. 02Run `fenwave login` — same identity as the web platform.
  3. 03Run `fenwave service start`; the DevApp opens at localhost:3003.
  4. 04Containers, images, volumes, registries, logs and terminals in one dashboard.

Related use cases

See Fenwave on your own projects

Thirty minutes, on your repositories and your clusters. We will point out three requests your platform team would stop receiving as soon as next week.