All developer needs, across the entire SLDC

A fully-fledged internal developer covers everything from planning to post-production ops. It’s an end-to-end developer experience; one place to cover all needs when developers aren’t coding.

Plan: let developers unlock their day

Everything begins with a plan. To plan, developers need to see PRs to review, incidents to manage, new team members to onboard, and whether they are on-call. Having it all in one place can make prioritizing and planning easier, leaving a lot of time to code.

Common user stories

  • Pull request reviews

  • All relevant Jira tickets

  • Future on-call shifts

  • Manager initiatives
    (e.g. need to update helm charts, tag S3 buckets etc)

  • Security issues by priority

Develop: give context, get developer autonomy

When developing, developers need to get quick context, on dependencies, APIs and more. They also need to be able to test quickly, access a development environment and force merge code, using golden paths and with the right guardrails in place.

Common user stories

  • Find API documentation

  • Add IaC to service

  • Scaffold new service

  • Deploy a development environment

  • Manage secrets

Ship: make it happen, easily

Using a portal, developers can ship features without needing extensive knowledge and familiarity of tools. Cover all shipment needs with self-service that frees developers and ensures your quality and cost standards are always met.

Common user stories

  • Build

  • Promote

  • Deploy

  • Toggle feature flags

  • Manage Canary

  • Run Migrations

Production operations: monitor & maintain

Developers are needed for incident management, maintenance and on-call. Let them view data across infrastructure and dev tools to understand why issues happen, monitor services and make changes.

Common user stories

  • Rollback

  • Restart service

  • Understand health of services

  • Notify service owner on incident

  • Get temp permissions to DB/Resource

  • Find outages root causes

  • Understand & troubleshoot outages

Start with the most pressing needs, build more later

Portals should support a broad range of use cases and user stories. Start with a smaller subset of developer routines, and add more as you go, driving functionality and adoption. Choose Port for its support of any future use case you’ll need, allowing you to deliver a compelling user experience.

The portal touches every step of the journey

Developer productivity begins with developer experience. Provide developers with what they need in the way that’s simplest for them to use. Using a portal, developers:

  • Don’t need to context switch as they can use one tab for all tools (except for git or their CDE)

  • Know what the golden paths are

  • Are served infrastructure and K8s data in a way that’s abstracted and personalized to them

  • Don’t need to know tools and technologies that aren’t core to their work

  • Can self-serve most actions with a golden path with no need to tap into tribal knowledge or send a ticket to devops

Portal as code

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.

API-first

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 API

Integrations

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.

Read more

Starting with Port is simple, fast and free.

Let’s start