Skip to main content

What is DevsPortal

DevsPortal is a complete, modular internal developer platform (IDP) for Kubernetes. It brings together the abstractions platform and application teams actually need — a Backstage-powered developer portal, development and architecture guardrails, application CI/CD, GitOps, and observability — in a single, cohesive product.

Instead of stitching together a dozen CNCF tools and writing the glue yourself, DevsPortal gives a platform team a production-ready foundation on day one. You can run it as-is, or tailor it to your organization's vision.

White-label by design​

DevsPortal is a white-label product: the same engine powers many customers, each with their own brand, domain, identity provider, and policies.

  • Fedshi is customer #1. Its instance runs at https://console.idp.fedshi.com and is used as the worked example throughout this documentation.
  • The deployed portal shows the customer's brand (logo, colors, sign-in label, social previews), not "DevsPortal". Re-branding for a new customer is a thin, repeatable step — see White-label model.

This means DevsPortal can be offered as an internal platform for one organization, or as a managed/branded platform for many.

What you get​

  • A developer portal — a Backstage-based console where developers discover, create, deploy, and observe their applications with self-service.
  • Golden-path abstractions — developers work with Projects, Components, and Environments, not raw Deployments, Services, and RBAC. Platform engineers define those golden paths once, as templates.
  • Application CI/CD — build from Git or deploy prebuilt images; promote releases across environments through declarative pipelines.
  • GitOps-native state — everything is a Kubernetes resource, so the platform's and applications' desired state can be versioned and reconciled.
  • Integrated observability — logs, metrics, and traces are automatically enriched with project/component/environment context and queryable from the portal.
  • Multi-tenancy & access control — namespaces and projects as boundaries, with fine-grained role-based authorization.

Built on Control Plane Operator​

note

DevsPortal is built on the Control Plane Operator engine, originally created by WSO2 as the successor to its Choreo SaaS platform and contributed to the CNCF community. We keep the engine's Kubernetes-native internals unchanged — you will see openchoreo.* API groups, namespaces, Helm charts, and the occ CLI. Those are implementation details; the product you brand, deploy, and present is DevsPortal. For deep engine API/CRD/CEL reference, this documentation links upstream rather than duplicating it.

Building on Control Plane Operator means DevsPortal inherits a battle-hardened, Kubernetes-native architecture and an active open-source ecosystem — while letting us deliver a branded, opinionated, ready-to-run product on top.

Where to go next​

  1. Why DevsPortal — the problem it solves and how it's different.
  2. How it works — the multi-plane architecture at a glance.
  3. Architecture — the deeper technical model.
  4. Concepts — the core abstractions developers and platform engineers work with.
  5. Onboarding path — a guided way to learn the whole platform, hands-on.