Platform Engineering
A Terraform-first Approach to Internal Developer Portals
Mar 14, 2023
No-code role-based access control
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.
Control who sees what and who does what
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.
The policies you need for self-service actions
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.
Single sign-on and ownership-led permissions
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).
Audit log
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.
Makes any dev
happier. We're
serious about that.
Whether you're a full stack developer or a DevOps engineer, context switches are all over. We're here to 1000x the developer experience.
Eliminate clutter
around infrastructure. Deliver faster.
Save thousands of hours spent on understanding, communicating and managing DevOps assets. Transform time consuming tasks into a one-click op.
A culture of quality
and compliance
Use scorecards, golden paths and set the standards for compliance and software quality. Drive change through standards setting, not enforcement.
