Feature ideas

Currently, the message sender only supports slack. Some organizations use Microsoft teams, which means they cannot create notifications for their teams.

As a Port admin, I need to enforce a code freeze across the organization so that no one, including other Port admins, can edit integrations, blueprints, workflows, or dashboards while the freeze is active. Today I can only ask people not to make changes, and nothing in Port prevents them. I’d like a single toggle or scheduled freeze window that makes these configuration objects read-only for everyone, with an audit trail of who attempted changes during the freeze. Workflow runs should remain allowed by default, with an option to block them as well. This would let us enforce our organization’s code freeze policy directly in Port.

Some data models include blueprints such as CI/CD jobs or deployments. These blueprints usually get filled with high number of entities, but the entities in these blueprints become stale and lose relevancy very quickly. With this feature, users will be able to configure custom retention for specific blueprints, giving them the option to automatically delete old entities once the number of entities for the blueprint passes X entities, or if an entity was updated more than 1 week/month/year ago

Teams need to see security vulnerability data alongside the services and infrastructure they own in Port. We’d like a Qualys integration that syncs hosts, assets, and vulnerability findings into the catalog and links them to the relevant services and owners. This would let teams check their risk posture from the same place they manage their software, and build scorecards around open critical vulnerabilities or patch SLAs. Ideally the integration would also support scheduled syncs and keep findings up to date as Qualys scans run.

Currently, Port's audit log does not capture the source IP address of individual API calls. The request is to expose the source IP address for each API request in the audit log

Add option to specifically resync a predefined list of resources & do a scheduled resync only for a selected list of resources

Clicking "get more results" in a grouped table drills down into the group and reloads the table, so the user loses the view and position they were working in. The extra results should load inline in the current table instead of in a new view. Every reload interrupts the user's work, which makes it hard to navigate and compare data across groups in large tables.

Unlike Ocean integrations, the Port Agent doesn't expose Prometheus metrics, so teams running it self-hosted for actions, workflows and automations can't see its backlog, failures or whether it's stuck, and have nothing to autoscale on. Expose a /metrics endpoint with counters for processed, failed and skipped events ( port_agent_events_total{source,outcome} ), webhook results including HTTP failures, timeouts and connection errors ( port_agent_webhook_requests_total{status_class,outcome} ), authentication, connectivity and polling failures ( port_agent_consume_errors_total{source,reason} ), and Port API calls for claiming, acknowledging, reporting status and sending run logs ( port_agent_port_api_requests_total{operation,outcome} ). Add histograms for webhook latency with p95/p99 ( port_agent_webhook_request_duration_seconds ) and time from event creation to processing start ( port_agent_event_age_seconds{source} ), plus gauges for the last successful poll, including empty results ( port_agent_last_successful_consume_timestamp_seconds{source} ), and Kafka backlog in Kafka mode ( port_agent_kafka_consumer_lag{topic,partition} ). Without these, self-hosted agents end up over-provisioned or silently falling behind.

The audit log API ( GET /v1/audit-log ) can't filter results by the user or identity that performed an action. Anyone who needs the activity of a single user or service account has to pull every event in the org and filter them on their own side. Adding a filter by user ID and by user email or client ID, covering both human users and service accounts will help a lot with that.

The workflow builder is hard for non-technical users. Add a simpler workflow form trigger that uses the self-service action UI for building forms.