Feature ideas

We take your ideas seriously! Read more on our prioritization process in our blog https://productmanagement.port.io/posts/managing-feature-ideas
Multi-integration ownership for deletion / reconciliation
Problem Today, automaticPort only allows automatic deletion during reconciliation by the integration that originally created an entity (the entity’s “owner”). If an entity was created by Port Internal or a legacy integration (e.g., the legacy GitHub app) and is later updated or maintained by a different integration (e.g., an Ocean-based LDAP/entitlements integration or GitHub Ocean), the maintaining integration cannot delete the entity when it stops reporting it. This results in: Orphaned entities that cannot be cleaned up automatically Customers being forced to delete and recreate large numbers of entities (users, GitHub entities, etc.) solely to transfer ownership Increased operational risk and complexity during migrations (e.g., legacy GitHub app → GitHub Ocean, or custom scripts → Ocean integrations) Requested solution Support multi-integration ownership for deletion, or provide a safe ownership transition mechanism. For example: Allow a configurable list of integrations to be authorized to delete an entity (or entities of a given blueprint/kind), even if they did not originally create it Provide a supported way to transfer or extend ownership from one integration/user-agent to another (e.g., from Port Internal or a legacy GitHub app to an Ocean integration) without requiring delete-and-recreate Benefits Safe, non-destructive migrations between integrations (legacy → Ocean) Cleaner catalogs with fewer orphaned entities Better alignment with real-world “source of truth” changes (e.g., moving user management to LDAP, or project ownership to GitHub/Snyk Ocean)
0
·
External Integrations
JFrog Integration
Integrating JFrog’s end-to-end software and AI supply chain security with Port’s Internal Developer Portal creates a single, authoritative control plane for visibility, governance, and remediation. Security signals such as SBOMs, vulnerabilities, malicious package detections, license and policy violations, secrets, SAST and IaC misconfigurations, and AI model risks are ingested from across the JFrog platform and modeled in Port as first-class entities. These signals are correlated to services, artifacts, packages, environments, deployments, and owners, with contextual enrichment such as CVE applicability, runtime exposure, business criticality, and ownership. This provides continuous, real-time insight into software and AI supply chain risk, backed by centralized audit trails, lineage, and compliance views. Through this integration, Port transforms raw security findings into actionable outcomes for both security and engineering teams. Developers gain a shift-left experience with clear ownership, service-level readiness indicators, and visibility into issues surfaced from IDEs, CLIs, and automated scanners, while Port actions enable guardrails and AI-driven remediation such as opening fix PRs and tracking SLAs. Security teams benefit from a unified posture view across services and environments, consistent policy enforcement, exception management, and end-to-end traceability from source code and models through artifacts and deployments. The result is a shared, developer-friendly security workflow that scales governance and remediation without slowing delivery.
0
·
External Integrations
Load More