We are Fenleap.
We built Fenwave because we kept watching good engineers spend their week on requests.
What we kept seeing
Fenleap builds and runs delivery infrastructure for French retail and MedTech teams. In every engagement the same pattern showed up: a small platform team, and a queue of requests that were not technically hard. Grant a bucket. Restart a pod. Spin up an environment. Send someone a file. Each one took a few minutes to perform and a few days to reach.
The bet we made
The bottleneck was never skill — it was that the only way to do those things was to hold a credential, and credentials cannot safely be handed around. So we built the platform the other way up: store the credential once, and grant people a narrow, named, audited role instead. Everything else in Fenwave follows from that decision.
Why it reaches beyond engineering
Once access is a permission rather than a skill, there is no principled reason to stop at developers. A marketing manager uploading to a bucket, an analyst fetching an export, a support agent checking whether a release went out — all the same mechanism, all narrower grants than the shared credential they replace. That is the part of Fenwave we are least willing to compromise on.
Where we are going
Fenwave is built on Backstage and Kubernetes, deliberately: we would rather be opinionated on top of things your team can already reason about than invent a new abstraction you have to trust. It ships as a hosted platform and as a Helm chart, with the same feature set in both, because compliance should not cost capability.
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.