Port
Self-service workflows have cut deployment from weeks to minutes and embed compliance by default
What is our primary use case?
Our main use case for Port is that we use its Service Catalog to list and display all the information for our applications. We also use Self-Service for our deployment work.
A recent workflow example is a serverless deployment. Our developers just need to push their code to GitHub, and then we use Port to deploy. The backend still uses Terraform, but we use GitHub Actions to provision, including Terraform plan and Terraform apply.
Something unique about our workflow is that Self-Service is pretty powerful, and we use it a lot. It saves us a lot of time compared to our current Sprint Agile way. It reduced our time from a couple of weeks to just 30 minutes, which is pretty awesome.
How has it helped my organization?
Port has positively impacted our organization through Self-Service. We changed our deployment wait time from a couple of weeks to less than 30 minutes, which is a lot of time saving and also cost saving. We also have all the security and compliance standards embedded into Self-Service, which saves us a lot of time in the future that we would otherwise spend refactoring or reviewing those standards.
What is most valuable?
In my experience, the best features Port offers are Self-Service and the new AI functions, which are pretty helpful. We set up skills inside Port, and our developers can use Port AI to ask for a service to deploy.
Our team is using the AI functions to make things easier for developers. They are similar to Port Self-Service, where we define a form, and developers need to fill in the form with the details about their application and then deploy. The similar function in AI lets users just ask AI, "Okay, I need to deploy an application," and the AI prompts users to provide more information about their service name, their environment to deploy, and also tagging strategy. All of this can be defined by AI functions.
A good strength of Port (port.io) is its pace of software development. Port releases new features very quickly, and it is kind of leading AI adoption for companies.
When it comes to Port's AI governance and security, I would say governance and security are already embedded, so that is good.
Because we already defined our AI Agent and our skills, the accuracy and reliability of Port's AI output is pretty accurate, I would say. If Port can teach customers how to use that, customers would be able to improve their accuracy.
What needs improvement?
For improvements to Port, I hope they can do better with customer onboarding. Instead of just giving customers access, the onboarding process is important for customers, especially new customers, because they are new to the product and have no idea where to start. They do not know the best practices for software development and deployment. Onboarding will help developers a lot to improve their efficiency and also help them adopt the tool and the platform.
Onboarding is the main improvement we would like to see in Port, and I think that is it. That is the main challenge we had before.
I chose 8 out of 10 because I think Port could improve its customer relationships by being closer to customers and helping customers be more successful.
For how long have I used the solution?
We started with Port two years ago, and we became their customer one year ago.
What was our ROI?
We do not have an exact number for our monthly time savings with Port, but we do have an estimation. For example, for 10 applications, we would save at least 100 hours for engineers.
What other advice do I have?
On a scale of 1 to 10, I rate Port overall an 8.
Port is a SaaS platform, so there is no need to deploy anything.
For others looking into using Port, I recommend trying it first. Port also has a Free subscription for users. If you have fewer than five users, you do not even need to purchase a license first. You can try it first.
A clear interface and useful integrations that make deployment and everyday platform work easier
Unified portal has standardized cloud landing zones and streamlined day two operations
What is our primary use case?
A specific example of how I use Port for building landing zones or products is that we can build easily any cloud landing zone in Azure, AWS, or GCP. We can do day two operations such as building networks, setting up permissions, and so on. We have full visibility in the portal as a software catalog.
What is most valuable?
Port sets up the golden path and guardrails for developers by allowing you to define a standardized way of doing common engineering tasks. You can ingest some security checks, implement standard workflows with approved cloud resources, and set up policies to constrain what can be used in which environment. Port also offers integrations with other systems such as GitHub and allows you to approve specific Terraform modules, for example. Approvals are also available.
Port has impacted my organization positively by helping establish a standard way of doing things without having to cater for each development team separately. As a team that develops infrastructure, it is positive because I do not have to follow many different processes for clouds, deployments, or other tasks. Instead, I have this single stop of a software catalog that tells me what is available. I can click through it, get my infrastructure provisioned, and deploy the products.
While I do not have any measurements, I can safely say that the time saved is enormous because you do not have to look at different parts in the organization and spend time finding who does what or where to get something provisioned. Instead, it is a single portal where you can do pretty much everything.
What needs improvement?
I would find it interesting to see some kind of migration plans for Port, including support for migrations that it could automate, such as moving from other systems or directly migrating cloud resources to Port.
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
I have not used Port's AI capabilities, so I cannot provide any thoughts on the accuracy and reliability of its output.
My advice to others looking into using Port is that you should go for it; it is a great product. I would rate this review a 9.
Great IDP
I like the tool, we're just scratching the surface.
Elegant self-service portal offering various features to make life easier
review from system engineer perspective
Easy to use and to integrate with AWS
Easy to integrate with AWS
User friendly
Portal for Modern Engineering Teams
What I love most is how easy it is to make Port work for our needs - you can add your own integrations if you need to, plus there are lots of ready-made ones from both Port and the community.
The interface is super easy to use, and you can set it up so different team members see exactly what they need without getting overwhelmed. It's really helped our team work better together.
Observability and Ownership: Monitor and understand the performance, health, and behavior of services to ensure reliability and availability.
Scorecard: Measure and track system performance to understand and prioritize areas for improvement.
Developer Experience and Self-Service: Improve developer productivity by providing efficient tools and resources for managing workflows and resources.