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.
A fully-fledged internal developer portal covers everything from planning to post-production ops. It’s an end-to-end developer experience; one place to provide developers with everything but coding.
Everything begins with a plan. Having it all in one place can make prioritizing and planning easier, leaving a lot of time to code.
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
Developers need quick context, on dependencies, APIs and more. They also need to test quickly, get a development environment and force merge code, all using golden paths and with the right guardrails in place.
Find API documentation
Add IaC to service
Scaffold new service
Deploy a development environment
Manage secrets
Let developers ship features even when they don't have extensive K8s knowledge or familiarity with all tools. Create self-service actions that free developers and ensure quality and cost standards are always met.
Build
Promote
Deploy
Toggle feature flags
Manage Canary
Run Migrations
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.
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
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. Port supports future needs, so you can deliver compelling user experiences in the future too.
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
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.