Skip to content
Fenwave
en
All use cases
Security & compliance

Run the whole platform inside your own perimeter

Self-host Fenwave via Helm when the data may not leave your cluster.

Before Fenwaveblocked waiting

“Legal will not approve a SaaS tool that can see repository names and deployment metadata. Is there an on-prem option?”

What the wait costs

A tool that would help is rejected at review, and the team keeps the spreadsheet it was meant to replace.

With Fenwave2-3 days

In Fenwave

helm install fenwave›your cluster

Capability

Platform Settings

Fenwave ships as a Helm chart you install on your own Kubernetes. Nothing needs to leave the cluster: the database, the platform and the credentials all stay inside your perimeter, and updates roll out on your schedule rather than ours. It is the same product as the hosted version — regulated industries do not get a reduced feature set as the price of compliance.

How it works

  1. 01Install the Helm chart into a namespace on your cluster.
  2. 02Point it at your PostgreSQL and your identity provider.
  3. 03Register your clusters and repositories; nothing egresses.
  4. 04Control when updates roll out.

Related use cases

Security & compliance

Answer "who can reach production data?" from one screen

Roles scoped to specific resources, with an audit trail that names people, not service accounts.

3 weeks5 minutesPlatform Settings
DevOps & SRE

Delete the ticket queue instead of working through it faster

Grant scoped, self-service access once and stop being the bottleneck for work that is only privileged.

every dayoncePlatform Settings
Security & compliance

Catch the committed secret this week, not at the breach

SAST, dependency, container and secret scanning one click from the component.

1 quarter4 minutesSecurity Scanner

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.