Directory DevOps & Platform EngineeringInternal Developer Platformskubefwd

kubefwd

About kubefwd

kubefwd port-forwards Kubernetes services, operating on a single service, a whole namespace, several namespaces, or several clusters at once. Each service it touches is assigned its own loopback address with the cluster hostname written to /etc/hosts. In-cluster connection strings resolve and work without modification. It watches Kubernetes events and reconnects automatically on pod churn. It can be operated through an interactive TUI, a REST API, or an MCP server for AI assistants. It is released under the Apache 2.0 license.

Products

kubefwd: Port-forwards Kubernetes services in bulk across namespaces and clusters.
MCP server: Allows MCP-capable AI assistants to connect, browse cluster services, and forward them.

Used for

Forwarding a whole namespace of services at once
Reconnecting forwarded services automatically after pod restarts
Streaming pod logs and live bandwidth data during use

From kubefwd's own website, read 2026-10-23. How we build listings.

How to evaluate Internal Developer Platforms

This is how the CIOPages Research Team evaluates this category. It is not an assessment of kubefwd. It comes from our Internal Developer Platforms (IDP) buyer guide.

25%

Software Catalog & Service Ownership

Accuracy of the catalog-of-record without manual upkeep (auto-discovery from Git/cloud/Kubernetes, real-time sync), the flexibility of the entity/data model (custom component types, relationships), dependency and API mapping, and how cleanly it answers “who owns this service?” during an incident

25%

Golden Paths & Self-Service Provisioning

Software templates / scaffolder for new-service creation, day-2 self-service actions (not just day-0), whether actions actually provision infrastructure or merely file a request, workflow/automation depth, and integration with an orchestration engine (Score, dynamic config) where real provisioning is the goal

15%

Scorecards, Standards & Governance

Maturity rubrics and scorecards (production-readiness, security, reliability), the ability to set and roll up global standards across teams, automated compliance checks, RBAC granularity, SSO/SAML, and audit logging on the portal itself

15%

Integration & Ecosystem

Breadth and quality of pre-built integrations (SCM, CI/CD, cloud, observability, incident, security), Backstage plugin compatibility where relevant, API-first / IaC support (Terraform, Pulumi) for managing the portal as code, and an in-IDE / MCP path so developers stay in flow

10%

Operating Model & Total Cost to Run

Build vs. buy vs. managed fit, realistic platform-engineer headcount to operate it, upgrade burden (code changes vs. version bumps), dependency-patch cadence, hosting model (self-managed, single-tenant SaaS, multi-tenant), and SOC 2 / compliance posture of the vendor

10%

Extensibility & Developer Experience

Customization ceiling vs. floor (no-code speed against framework flexibility), how opinionated the golden paths are and whether that fits your culture, UI/search quality, TechDocs and onboarding, and evidence of sustained developer adoption rather than mandated logins

Other Internal Developer Platforms Vendors

View all

Accenture

Accenture helps organizations rewrite the rules of growth, innovation and resilience through reinvention services.

Appian

Backstage (Spotify)

CloudFrame

CloudFrame helps enterprises transform COBOL mainframe applications into maintainable, cloud-ready Java code.

Coder

Cortex

CIOPages put this listing together from public sources. It’s information, not an endorsement. How we build listings. Work here? Claim this listing or .