Introduction
Port announced today that its no-code internal developer portal now brings FinOps insights into the portal, allowing FinOps, DevOps and platform engineering teams to stay on top of cloud costs, rightsize spend and drive a more cost-conscious engineering culture without spending hours to get the basic reporting in place.
Today, most cloud resource cost reporting tools report data about cloud resources, such as S3, EC2 etc or kubernetes objects such as deployment, service, namespace, clusters and more. “The problem is that this type of reporting makes sense from the cloud resource provider point of view but is almost meaningless from the point of view of developers, teams and business owners, since it doesn’t tie into the microservice or system each of them are responsible for” said Yonatan Boguslavsky. Typically, to understand costs in a way that makes sense for developers and business teams, an extensive tagging effort is required within the cloud resource cost tracking tools. While this is feasible theoretically, it requires discipline and labor and is usually not done as it should be. “Internal developer portals and their broad software catalog can solve this problem” said Boguslavsky.
Internal developer portals lie at the center of the platform engineering revolution and support more than just developer self-service and abstraction. At their core lies a broad software catalog which contains a real time view of all software and infrastructure, including cloud resources. As such, the software catalog can show microservices, cloud resources and dependencies relating to teams, developers, services, systems and domains. Using integrations it takes minutes to add cloud cost data to Port’s software catalog, and all the data will be immediately mapped to developers, teams, microservices, systems and domains. Doing this in Port’s internal developer portal platform makes it easy to query the data and create reports on cloud cost per team, developer, service, system and domain.
“Software catalogs contain everything about costs, services, cloud resources, CI/CD and more. As such, they contain a real time snapshot of everything in the engineering environment, and are easily searchable” says Zohar Einy, CEO of Port. “Internal developer portals are about unifying information and reducing cognitive load. Developers track bugs or user counts on one central screen, sometimes even a large screen in a central place in the workplace. Why shouldn’t cost data be presented in a similar way?”, said Einy.
“This can be taken even further” said Einy. “You can create scorecards for cost to create a cost-conscious engineering culture and to rightsize costs without adding cognitive load to developers. You can also use workflow automation to identify issues and send alerts to the right people” Another option, adds Einy, is to get developers to add descriptions to services that capture their expected resource usage and cost.
{{cta_3}}
About Port
Port is a platform for building no-code, holistic, Internal Developer Portals. Port’s software catalog covers microservices, resources, custom assets and fits any data model, with in-context maturity scorecards. Its portals support any developer self-service action and workflow automation. You can read more at getport.io or see a live demo at demo.getport.io
Book a demo right now to check out Port's developer portal yourself
It's a Trap - Jenkins as Self service UI
How do GitOps affect developer experience?
It's a Trap - Jenkins as Self service UI. Click her to download the eBook
Learning from CyberArk - building an internal developer platform in-house
Example JSON block
Order Domain
Cart System
Products System
Cart Resource
Cart API
Core Kafka Library
Core Payment Library
Cart Service JSON
Products Service JSON
Component Blueprint
Resource Blueprint
API Blueprint
Domain Blueprint
System Blueprint
Microservices SDLC
Scaffold a new microservice
Deploy (canary or blue-green)
Feature flagging
Revert
Lock deployments
Add Secret
Force merge pull request (skip tests on crises)
Add environment variable to service
Add IaC to the service
Upgrade package version
Development environments
Spin up a developer environment for 5 days
ETL mock data to environment
Invite developer to the environment
Extend TTL by 3 days
Cloud resources
Provision a cloud resource
Modify a cloud resource
Get permissions to access cloud resource
SRE actions
Update pod count
Update auto-scaling group
Execute incident response runbook automation
Data Engineering
Add / Remove / Update Column to table
Run Airflow DAG
Duplicate table
Backoffice
Change customer configuration
Update customer software version
Upgrade - Downgrade plan tier
Create - Delete customer
Machine learning actions
Train model
Pre-process dataset
Deploy
A/B testing traffic route
Revert
Spin up remote Jupyter notebook
Engineering tools
Observability
Tasks management
CI/CD
On-Call management
Troubleshooting tools
DevSecOps
Runbooks
Infrastructure
Cloud Resources
K8S
Containers & Serverless
IaC
Databases
Environments
Regions
Software and more
Microservices
Docker Images
Docs
APIs
3rd parties
Runbooks
Cron jobs
Check out Port's pre-populated demo and see what it's all about.
No email required
Contact sales for a technical product walkthrough
Open a free Port account. No credit card required
Watch Port live coding videos - setting up an internal developer portal & platform
Check out Port's pre-populated demo and see what it's all about.
(no email required)