Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

W'xOps

docs.wxops.cloud

  • Free plan
  • Windows
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
7.8 Club score Visit docs.wxops.cloud

What W'xOps is

W'xOps is a self-hosted internal developer portal for teams running Kubernetes. It runs as a portal container on a hub Kubernetes cluster and offers a searchable service catalog based on Backstage-compatible YAML stored in a gitops-infra repository, without a database or separate catalog server. Pinniped group membership and Kubernetes RBAC determine access across spoke clusters. Configuration changes avoid direct Kubernetes writes: users work through reviewed Gitea pull requests and ArgoCD synchronization. A scaffold wizard previews manifests, creates a service repository and deployment configuration, and opens a pull request. Lifecycle promotion is role-gated and PR-driven, with platform-team review for later stages. Darlane provides parallel debug deployments beside live workloads. W'xOps can write to Vault but cannot read secrets or delete secret paths; write actions are logged as structured JSON. It includes a CLI, API reference, software catalog, self-service workflows, and open-source code from version 0.6.x.

Who it suits

W'xOps suits Kubernetes-native teams that want self-hosted developer tooling and data kept inside their infrastructure. It is less suitable for teams without Kubernetes or those seeking a broad third-party plugin ecosystem.

Good to know, and what to watch

  • Self-hosted Kubernetes deployment
  • Catalog needs no database server
  • Role-gated GitOps changes
  • Structured JSON write-action logs
  • CLI and API included
  • Requires running Kubernetes
  • Limited third-party plugin ecosystem
  • Cannot read Vault secrets
  • Some catalog kinds are unsupported

The verdict

W'xOps combines a Kubernetes-focused portal, catalog, scaffolding, and GitOps controls. Its self-hosted, permission-based design fits infrastructure-conscious Kubernetes teams, while the deployment requirements and narrower ecosystem limit its audience.

What the maker publishes

Audit
The documentation says write actions are logged as structured JSON to stdout, including scaffolding, Vault writes, and promotions. source
Availability
The deployment guide says the portal image is in a private registry and access is granted case by case for enterprise deployments. source
Catalog limits
The catalog supports Component, API, Resource, System, Group, User, and Doc kinds; Location and Template kinds are not implemented. source
CLI and API
The documentation provides a wxops command-line interface and an API reference. source
Cluster security
The portal does not write to Kubernetes; configuration changes go through Gitea pull requests and ArgoCD sync. source
Debugging
Darlane provides on-demand parallel debug deployments alongside live workloads, with role gating and copyable kubectl and mirrord commands. source
Deployment
The guide describes deploying W'xOps as a portal container on a hub Kubernetes cluster. source
Deployment
W'xOps is described as a single Go binary with an embedded Next.js frontend and no database, cache, or message queue. source
Identity
W'xOps derives permissions from Pinniped group membership and uses Kubernetes RBAC to control what users can see on spoke clusters. source
Integrations
The deployment guide lists ArgoCD, Traefik, cert-manager, External Secrets Operator, Vault, Dex or another OIDC provider, Gitea, and Pinniped among deployment prerequisites or components. source
Integrations
The documented platform ecosystem includes Gitea, ArgoCD, Crossplane, Vault, Pinniped, and Kubernetes. source
Intended users
The maker says W'xOps is suited to teams already running Kubernetes, especially those that need data to stay inside their infrastructure. source
Lifecycle promotion
Lifecycle promotion is PR-driven and role-gated, with platform team review for later stages. source
Limits
The maker says W'xOps is Kubernetes-native and may not suit teams without Kubernetes; it also notes that it lacks a broad third-party plugin ecosystem. source
Maker and location
The documentation footer identifies the W'xOps Platform Team and says the project is made in Vietnam; it does not state a headquarters or founding date. source
Multi-cluster access
The portal uses Pinniped for shared identity across Kubernetes clusters and derives access from Kubernetes RBAC. source
Notable limitation
The maker says W'xOps may not fit teams that need a broad third-party plugin ecosystem or do not plan to run Kubernetes. source
Open source
The documentation states that from version 0.6.x W'xOps is open source and open for contributions. source
Product
W'xOps describes itself as an internal developer portal for Kubernetes-native teams. source
Scaffolding
The scaffold wizard creates a service repository and deployment configuration through a workflow that previews generated manifests and opens a pull request. source
Secret handling
The maker says the portal does not read secrets, to avoid making it a secret exfiltration path. source
Secrets
The portal can write to Vault but cannot read secrets back or delete secret paths. source
Security design
The maker says the portal does not write directly to Kubernetes; configuration changes go through reviewed Gitea pull requests and GitOps sync. source
Service catalog
The searchable catalog reads Backstage-compatible YAML from a gitops-infra repository and requires no database or catalog server. source

Checked against the maker's pages on 8 Oct 2026.