Port will auto-discover software catalog assets according to blueprints: microservices, CI/CD, cloud resources and more
Each template includes developer self-service actions from creating a service to day-2 operations and temporary environments
Drive engineering quality standards by setting scorecards to reflect requirements and quality
An internal developer portal using Git providers
This template creates a classic microservice catalog providing visibility into the software development lifecycle. Git data will populate Port blueprints, creating software catalog entities that will show developers the information they need, in-context, with the right abstractions, permissions and more.
A GitOps based internal developer portal
This template generates a backstage-style C4 software catalog. The strength of this approach is that it goes beyond microservices and catalogs underlying cloud resources, deployments and related dependencies. A nice addition here can be a running service blueprint.
A CI/CD based internal developer portal
This method uses CI/CD data to create the portal. It unifies CI/CD data that is spread across multiple systems and repositories, so you can see all build and deployment configurations, artifacts, version numbers, environment variables, dependencies and more.
An internal developer portal for Kubernetes
This template uses our Kubernetes exporter or ArgoCD. The resulting portal takes the different Kubernetes resources (deployments, pods, namespaces etc) and maps them into blueprints for a kubernetes catalog, creating Kubernetes entities. You can then configure Kubernetes abstractions for developers, to reduce cognitive load.
An internal developer portal for cloud resources
The template uses Port’s cloud exporters to build a developer portal. Adding cloud resource data into the software catalog enriches catalog data immensely and provides developer autonomy. In the case of AWS you can add data about Lambda functions, S3 buckets, SQS queues, ECS services and anything in the AWS cloud control API (500 resources!).
You can and should change your mind
We don’t expect your choice of template to be static - you can play with templates and improve them, introducing any type of blueprint you need and creating a super-opinionated software catalog and internal developer portal that exactly fits the way your engineering organization works.