There's a ton of data in software catalogs and a lot of options to self-serve. Reduce "too-much-information" cognitive load for developers, ensure compliance and security and set boundaries on self-service actions.
Autonomy means trust. Especially when allowing direct consumption of different resources. Set the right permissions on software catalog data to ensure developers see what they need, and to ensure self-service actions and their properties are open only when they should be.
Using Port’s RBAC you can define granular policies for self-service actions that go beyond allowing a developer to perform an action. You can set boundaries on how many development environments can be provisioned by a developer or team per week, or require that updating production pod counts require manual approval.
Port integrates with SSO and identity provider tools, so that it is aware of the organization’s structure - teams, groups and users - ensuring that each can see what it owns and less of what it doesn’t own (but should be aware of).
Port has an activity log that acts as an audit log that stores every event that occurred within the developer portal. It shows modifications made to software catalog data, who invoked which developer self-service action, status and more. It also shows any logs pertaining to how machines interacted with the data in the software catalog for workflow automations.
Configure and customize the portal itself through code, e.g. with Terraform. Simply update anything in the portal and know it's all in the repository. Democratize the portal by allowing engineering to contribute.
Use the API to model your software catalog, ingest data, invoke actions, query scorecards and more, or to get data from the portal into your CI/CD or automations.
Port plays well with your Git Provider, infrastructure, cloud provider, any SaaS or on-premise 3rd party service. Use Port's Open Source Ocean framework to easily build what you need.
.png)
.png)