Port

My main use case for Port  is using it as a client where we have access to this internal development platform to build our landing zones and all the products that come with it.

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.

The best features Port offers include having a single source of truth where you can see how your infrastructure looks. It pulls real-time data from all these tools, and it is great for setting up these golden paths and how developers can work with the infrastructure. You can put guardrails and constraints in place.

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.

It is hard for me to say how Port can be improved because so far I have not found many things that I would have an issue with.

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.

I have been using Port for about two years.

Port is stable.

Port's scalability is great; it scales very well. So far we have not reached the limits, and I hope we do not.

I believe the customer support for Port is great.

I have not used any different commercial solution before Port; I have only worked with in-house developed IDPs.

I do not have any relevant metrics such as time saved or money saved to share regarding return on investment from using Port.

I do not have any experience with Port's pricing, setup cost, and licensing because it is not handled by my team.

I did not evaluate other options before choosing Port.

I do not want to rate the governance and security in Port's AI capabilities.

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.