Port vs SigNoz
Side-by-side trajectory, velocity, and editorial themes.
Port turns its AI catalog into an automation platform as Workflows hits open beta
Port is an internal developer portal that has spent 2026 turning its software catalog into an AI-and-automation platform. Recent months added an MCP gateway (external MCP servers into Port AI), BYO/OpenAI-compatible LLM endpoints, an Azure Anthropic provider, Skills and Memory for its AI assistant, and a public plugins repo. June's headline is Workflows reaching Open Beta — a visual, node-based builder for self-service automations.
Two arcs are converging: Port AI as an open, model-agnostic gateway (external MCP, any OpenAI-compatible endpoint, Azure-hosted Claude, Skills/Memory) and Workflows as a visual automation layer on top of the catalog. The steady monthly 'Big' feature and the plugins ecosystem signal Port positioning as the automation and agentic-operations hub for platform-engineering teams, not just a catalog of services.
Workflows likely moves from Open Beta toward GA with more triggers and actions, while Port AI keeps expanding its connector and model surface — the two being stitched into one agentic self-service experience.
SigNoz pairs an AI teammate with enterprise access control and wide cloud coverage
SigNoz, the open-source ClickHouse-backed observability platform, is advancing on three fronts at once. Noz, its AI teammate that answers plain-English questions across live telemetry, is now general to all cloud users. Cloud and integration coverage keeps widening — Azure services and six new onboarding sources including PlanetScale and Cloudflare Workers — while fine-grained, role-based access control entered beta for Cloud and Enterprise. Underneath, Query Builder v5, trace-detail rework, and a ClickHouse version bump continue.
The platform is maturing from a query tool into an investigation surface: an AI layer to drive analysis, RBAC and self-service API keys to make that safe in larger orgs, and out-of-the-box integrations to shorten onboarding. Notably, the access-control work is explicitly framed around feeding read-only keys to the SigNoz MCP Server for AI tooling, tying the enterprise and AI tracks together. Expect Noz and MCP access to keep converging with the permissions model.
Next likely moves: Noz gaining more write-style actions beyond suggestions, RBAC graduating from beta with role assignment delegated, and continued ClickHouse-version-gated features like JSON trace attributes.
See more alternatives to Port →
See more alternatives to SigNoz →