Skip to content
Fenwave
en
Platform Settings

Grant the access, not the credentials

Roles, groups, clusters, repositories, cloud credentials and storage connections are configured in one place. Cloud keys are stored once by an administrator and never handed out; a person is granted a scoped role instead, which is what makes it safe to give a marketing manager a bucket.

Govern & connect
Cloud credentials in Fenwave Platform Settings: AWS, Google Cloud and Azure credentials, each scoped to environments and an owner group.

In this capability

  • Granular RBAC down to a single storage connection or environment
  • Cloud credentials for AWS, GCP and Azure stored once, never shared — static keys, workload identity or managed identity
  • Register clusters, repositories and environment types centrally
  • Groups mapped from your identity provider
  • Audit trail attributing every privileged action to a person

In Fenwave

Platform Settings›Users & permissions›Roles

Built on

  • OIDC
  • SAML
  • Backstage Permissions

Where teams use it

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

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
Security & compliance

Run the whole platform inside your own perimeter

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

blocked2-3 daysPlatform Settings

More in Govern & connect

All features

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.