Feature ideas

If I have two port instances for my organization (i,e - dev port, and prod port), I should be able to replicate data across the two instances so that I can use live data for testing changes in a lower environment instead of having to use production for the live data.

Please add the ability to generate a time-series trend line chart based directly on the historical count of entities matching a custom filter. We would like to be able to: Select an entity type (e.g., Service Entity). Apply a custom filter (e.g., entities with a specific property indicating they are onboarded). Plot the total count of those filtered entities over time. This feature would allow us to easily track system adoption rates without having to build and maintain dedicated aggregation properties on parent entities just for reporting purposes.

When a dashboard or catalog uses the “My Teams” filter, users who are not part of any team currently see all entities because the filter resolves to an empty set and removes restrictions; instead, the filter should return zero results (or follow a defined fallback) for users with no team membership, ensuring they don’t see everything by default, regardless of their role.

Integrating an Audit Log API into a Model Context Protocol (MCP) server so that Audit logs can be reviewed with MCP and Agents

The Integration Event Logs page is difficult to use when there are many logs. It currently uses infinite scroll, so logs only load while scrolling. This makes troubleshooting hard and makes it easy to lose the selection when trying to copy multiple log lines. In addition: The in-page search does not jump to the matching log entry There is no option to download logs There is no date/time range filter in the UI Users have to rely on the API for proper filtering Requested improvements Add pagination (or allow pagination instead of infinite scroll) Add a Download logs button to export filtered logs Add a date/time range filter in the UI Improve the in-page search so it navigates to matching log entries These changes would make the logs page much easier to use for troubleshooting, especially when working with large integrations that generate a high volume of logs.

Hi Port Product team, We are requesting support for OIDC client authentication mode private_key_jwt (RFC 7523) for Entra ID SSO configurations. At BNC, this is a blocker to implementing our approved SSO architecture because shared secret modes do not meet our target security posture for enterprise SaaS integrations. We are explicitly asking for a no-shared-secret model based on signed client assertions and certificate/public-key registration. This is high-impact for both Port and regulated enterprise customers: For Port: stronger enterprise IAM posture, fewer procurement/security objections, and reduced support friction around secret lifecycle incidents. For customers: lower credential risk, easier compliance, and faster secure rollout. Requested outcomes: Support private_key_jwt for Entra ID OIDC clients. Provide certificate rotation support with overlap window and non-breaking cutover. Publish clear setup and troubleshooting guidance. We are available to run a controlled enterprise pilot for this capability. Thank you, BNC DevPortal Architecture Team

The PATCH https://api.port.io/v1/teams/:name endpoint currently requires the team name rather than the identifier. Since names can change, this makes it harder to reliably update team entities without first performing an extra step to retrieve the current name. While there is a workaround using the entity patch endpoint, supporting the team identifier directly in this endpoint would simplify usage and cover more use cases.

The GitHub Ocean integration currently fetches team data via GitHub's GraphQL API but does not include parentTeam or childTeams fields. We'd like these fields to be added to the integration's team query so that team hierarchy relationships (parent/child) can be mapped into Port, for example, via a self-referencing relation on the githubTeam blueprint.

When filtering a catalog table by a relation, the entity selection dropdown is currently only available for the has any of operator. Since multiple operators are supported when filtering by a relation, the dropdown should be available across all of them for consistency.

Add a configuration option to allow live event (webhook) handlers in Ocean integrations to process mapping kinds sequentially (mirroring the behavior of the periodic sync) in order to ensure consistent entity and relation building for users with cross-blueprint dependencies. Live event behavior and periodic sync behavior should be configurable to match, giving users confidence that their data is consistently built regardless of the ingestion path.