Templates for a Plug and Play Internal Developer Portal

Set up your internal developer portal in minutes, creating the perfect match with your developer self-service needs, use cases and data models. Once you connect the source, data will be auto-discovered and auto-populated into the portal. Afterwards, you can further customize actions, scorecards and software catalog blueprints.

Software catalog

Port will auto-discover software catalog assets according to blueprints: microservices, CI/CD, cloud resources and more

Self-service actions

Each template includes developer self-service actions from creating a service to day-2 operations and temporary environments

Scorecards

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.

Catalog

The template includes an API blueprint, which shows your API specifications through a swagger UI.

Actions

The template comes with pre-defined developer self-service actions, such as scaffolding a new component. You can always add more.

Scorecards

Built-in scorecards show code maturity, ownership and production readiness.

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.

Catalog

The template includes an API blueprint, which shows your API specifications through a swagger UI.

Actions

The template comes with pre-defined developer self-service actions, such as scaffolding a new component. You can always add more.

Scorecards

Built-in scorecards show code maturity, ownership and production readiness.

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.

Catalog

Create a single source of truth for both developers and machines, to help with automated workflows and easier troubleshooting.

Actions

Trigger an incident, change on-call, add a secret or deploy a service. As always, you can add anything you’d like.

Scorecards

Built-in scorecards include DORA metrics and service maturity. Or anything else, really.

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.

Catalog

This template allows you to create a redacted and whitelisted Kubernetes catalog for developers, allowing K8s insight with less cognitive load.

Actions

Self-service actions in this template include restarting a cluster or refreshing it, letting developers to roam free, with guardrails.

Scorecards

Pre-built scorecards are configuration checks, availability levels and production readiness. You can add more, as needed.

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!).

Catalog

Get a thorough understanding of how services utilize the cloud. Simplify resource management by providing the relevant metadata to developers.

Actions

Set developers free by allowing them to create new cloud resource, get temporary permissions or create ephemeral environments.

Scorecards

This template supports an operational maturity scorecard.

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.

Think templates make life easy? Wait till you see how easy it is to ingest data into Port, or to customize it.

I’m ready, let’s start