An Internal Developer Portal for Kubernetes-native platform teams: one login for every cluster, a golden path from a form to a running service, and a safe place to debug — with Git as the only way anything changes.
Built for: Kubernetes · Gitea · Pinniped · ArgoCD · Crossplane · Vault
- Read-only by design. The portal never writes to a Kubernetes API, and its Vault client can only create or update a secret — there is no code path that reads or deletes one.
- Git is the only write path. Scaffolding, promotion, config edits and Darlane all end as commits
in
gitops-infra, reconciled by ArgoCD. Promotion to staging and production is always a reviewed pull request, and every change is a revertible commit. - Your identity, your permissions. One OIDC login through Pinniped Supervisor covers every cluster. The portal acts as you, with a short-lived credential, so you see exactly what Kubernetes RBAC allows — there is no second permission system to keep in sync.
- Stateless and small. No database: sessions are encrypted cookies and the catalog lives in Git. The whole portal ships as a single container image.
- A golden path, not a form to fill and forget. One wizard produces the repo, secrets, manifests, overlays, image automation and catalog entries together — and a service's lifecycle is derived from what is actually merged, not from a dropdown.
- Darlane: debug beside production. A parallel debug pod per environment that receives no traffic
by default, with your local code synced into it in real time by
wxops darlane sync.
| Area | What you get |
|---|---|
| Service catalog | Backstage-compatible entities (System, Component, API, Resource, Group, User, Doc) read from Git. Full-text search, a Ctrl+K command palette, dependency graphs, OpenAPI rendering, and RFC / ADR / runbook docs. → Catalog guide |
| Scaffolding | A wizard that commits XTenantApp, XTenantDatabase, ExternalSecrets, Kustomize base and overlays, an ArgoCD Image Updater CR and catalog entities to gitops-infra. Existing Gitea repos can be imported without re-scaffolding. → Golden-path flow |
| Lifecycle promotion | experimental → development → staging → production, driven from the Component page. Developers promote to dev; managers and platform-team promote to staging and production. Includes deprecation. → Promotion design |
| Darlane & CLI | Per-environment debug pods, plus the wxops CLI: login, catalog, debug, update, and darlane (sync, push, logs, restart, status, exec, port-forward). Usable in CI via WXOPS_TOKEN. → Darlane · CLI |
| Runtime visibility | ArgoCD sync/health and Crossplane status per environment, active alerts, and Grafana / Loki / Tempo links pre-scoped to the service. Plus CI runs, releases, container images and dependencies per entity. → Observability |
| Cluster views | Pods, deployments, services and quotas scoped by your group membership — no cluster-admin needed — and kubeconfig download. → Architecture |
flowchart LR
Dev(["Developer"]) -->|"scaffold · promote · edit"| Portal["W'xOps Portal"]
Portal -->|"PR / commit — the only write path"| Git["Gitea · gitops-infra"]
Git -->|"webhook"| Argo["ArgoCD + Crossplane"]
Argo -->|"reconcile"| Clusters["Hub and spoke clusters"]
Clusters -.->|"read-only, as the logged-in user"| Portal
The portal writes to Git and reads from your clusters with your credential. ArgoCD and Crossplane do the applying. See Architecture for the auth flow and hub-spoke topology, and the Codebase overview for how the code is laid out.
- Write to a cluster, or delete a Vault secret, or read one back.
- Show developers
gitops-infraPR links — they see status, not the platform's internal repo. - Offer delete actions to tenant developers (platform-team only).
- Replace the tools it links to: Gitea, ArgoCD, Grafana and Vault UI stay the source of truth for their own data.
These are properties of the code, not policy — see Security assurance for the evidence and how to check each claim yourself.
Run the portal locally against the bundled example catalog, with no identity provider:
cp backend/.env.example backend/.env
# In backend/.env, set:
# DEV_BYPASS_AUTH=true # skip OIDC; log in automatically as a dev user
# SESSION_SECRET=<output of: openssl rand -hex 32>
make dev-backend # Go API on :8080, serving the example catalog
make dev-frontend # Next.js on http://127.0.0.1:3000The full setup — Docker Compose, static cluster config, a real Gitea catalog — is in Local development.
The portal runs as a single image, installed with the Helm chart in charts/.
See the Deployment guide for the Pinniped, OIDC and RBAC
prerequisites and the Environment variables
reference.
Everything lives under docs/ — start with its index. Common entry points:
| Getting started | Introduction · Deployment · Environment variables |
| Concepts | Architecture · Platform engineering rationale |
| Using the portal | Catalog guide · Golden-path flow · Darlane · CLI · API reference |
| Security | Security assurance · Permissions |
| Contributing | CONTRIBUTING.md · Local development · Codebase overview · Release workflow |
| Direction | ROADMAP.md — planned work and architecture decisions |
APIs and generated manifests can change between minor releases — the changelog and release notes call those out.
Report a security issue through SECURITY.md, not a public issue.
Licensed under Apache-2.0; please read the Code of Conduct.