This release is full of quality-of-life upgrades: enhanced docs, smarter automation, faster ways to build and manage your catalog, and improvements shaped through your feedback.
It’s all about giving you more control, less manual work, and features that make sense.
Here’s what’s new 👇
Big
New “Solutions” section in docs
We’ve introduced a new
Solutions
section in our documentation, kicking off with focused guidance for Resource Self-Service, Incident Management, and Engineering360.
These solutions explore real-world challenges, such as fragmented toolchains or slow incident response, and show how Port helps teams move faster while remaining secure and compliant.
Inside, you’ll find:
  • Actionable best practices
  • Real-life examples
  • Clear guidance to empower developers and streamline workflows
Explore Engineering360
Access a unified view of your engineering workflows—across tools, teams, and environments—with Engineering360.
Solutions
Screen capture of the new Port Solutions documentation. The image is in dark mode and shows the "Surveys" section of the Engineering360 solution, with a video of how to create a survey.
Explore the new docs, and don’t forget to send feedback! Your input shapes what we build next.
Medium
Generate calculation properties with AI
Speed up your schema setup with AI-powered calculation suggestions that do the heavy lifting for you.
Describe what you need, and Port will generate the calculation field for you. You can try things like:
  • “Calculate the pull request lead time”
  • “Combine these two fields”
  • “If the service language is Go, set it as backend; if it’s React, set as frontend.”
This feature is currently available to organizations with access to our AI tools.
Wondering how to get it? AI features will gradually roll out over the next few months. If you're interested in early access, let us know.
CleanShot 2025-08-06 at 12
An animated GIF of the Port UI in dark mode showing how to create a new calculation property, asking Port to "Calculate the PR lead time."
Use GET method for webhook backends
You can trigger webhooks using the GET HTTP method in Self-Service Actions and Automations. Select GET when configuring your webhook to connect with more external APIs seamlessly.
Query related entities by relation name
You can query related entities by specifying a relation name in your search queries. This allows you to find entities connected through a particular relation type efficiently. For example, when using the search API, you can filter by a specific relation using the following structure:
{ "relation": "relationId", "operator": "=", "value": "value"}
This returns entities that are related via the specified relation. Additionally, Port supports advanced relation path queries, allowing you to traverse specific chains of relationships by defining the path of relation identifiers to follow. This is useful for more complex queries where you want to find entities connected through a specific sequence of relations.
Create and delete entities in bulk
Port supports efficient bulk operations for both creating and deleting entities, allowing you to save time by handling multiple items in a single API call. These bulk operations are available via the API and are designed to streamline your workflow by reducing the need for repetitive single-entity calls.
Bulk
create
entities:
You can create up to 20 entities at once using the following API endpoint:
POST /v1/blueprints/:blueprint_identifier/entities/bulk
This endpoint allows you to create, overwrite, or update multiple entities in your software catalog. For more details, see the Create multiple entities API documentation and example usage in the docs.
Bulk
delete
entities:
To delete up to 100 entities in a single request, use:
DELETE /v1/blueprints/:blueprint_identifier/bulk/entities
Note that all entities must belong to the same blueprint. For more information, see the Delete multiple entities API documentation.
Group by array properties
Easily organize data by selecting array properties as group criteria. Start grouping your views for clearer insights and faster analysis.
For example, in the attached image, we can group by "Owning Teams," an array property. In this case, we will see a service that belongs to multiple owning teams under each relevant group.
arrayprops
A screen capture of the Port UI in light mode showing the service catalog grouped by "owning teams."
Service dependency support in DataDog integration
You can now add the “service dependency” kind to your DataDog integration to surface real-time service-to-service relationships detected by Datadog.
Now live for Ocean SaaS and the latest Ocean self-hosted version (upgrade required).
Prefilter Azure data by resource group tags
Quickly filter your Azure data sources using resource group tags for easier data management. Start by selecting the desired tags to narrow down your data view.
Quickly find new guides in docs
You can now filter documentation guides by “New” to see the latest additions from the past 60 days. Click the “New” button or combine with other filters.
Newguides
A screen capture shows Port documentation guides with a "New" button in the top right section.
Integration docs embedded in the installation screen
Integrations Installation screens now embed the setup documentation, reducing configuration issues and eliminating tab-switching for a smoother install experience. The embedded docs are currently available only for Jira, PagerDuty, and Argo CD, and they aren’t shown when the integration is installed via OAuth.
docsinstallscreen
A screen capture of the Port UI in light mode depicts setup documentation embedded in the new Jira data source installation screen.
Small
Automatically hide null properties
Port provides the ability to automatically hide properties with null values in the entity details widget on the Overview page. To control this behavior, use the "Show Null Values" toggle in the entity info widget. When this toggle is off, properties whose values are null will be dynamically hidden from view. The toggle is on by default, so all values (including nulls) are shown unless you disable it. This feature helps keep the UI clean and focused only on relevant data.
Nullprops
A screen capture of the Port UI in light mode depicts the toggle setting for showing empty values.
Faster, more reliable related entities widget
We improved the Related Entities widget so it loads each tab independently, making it faster and smoother to navigate large datasets.
View and search kubernetes exporter logs in UI
You can now view and search Kubernetes exporter logs directly in the Port UI, specifically in the Event Log tab. With the latest updates, the Kubernetes exporter sends structured JSON logs to Port, providing improved visibility and easier troubleshooting. To take advantage of these enhanced logs, you need to upgrade your integration to the latest version that supports this feature. This allows you to monitor exporter activity and diagnose issues more efficiently from within the Port platform
k8s
A screen capture of the Port Event Log showing Kubernetes exporter logs as structured JSON.
Define array enums in IaC
Defining array enums in Infrastructure as Code (IaC) for Port means you can specify a list of valid values (enums) for array-type properties directly in your IaC files, such as Terraform. This allows you to enforce consistency and validation for array fields—users can only select from the predefined set of values when populating these arrays.
This feature was previously only available via the UI and API, but is now supported in IaC, making it easier to manage and standardize your catalog configuration through code.
View informational-only self-service action fields
You can include informational-only (read-only) fields in your Port self-service action (SSA) forms by setting the field’s state to “disabled.” This makes the field visible to users for verification, but prevents them from editing its value. This is useful for displaying context such as entity data or user information without allowing changes.
info-only-ssa
Image description: A screen capture of the Port UI SSA form displaying "Disabled fields" where one field is editable and the other is read-only.
Access your user entity from the profile menu
Click your user icon in the top right corner to instantly view your own user entity details, making it easier to review personal information and settings.
Guides