Self-Service Developer Portal
In Development
The Self-Service Developer Portal is currently in development. This documentation describes the planned architecture and capabilities. Features described here are subject to change before release.
Purpose: For platform engineers and application teams, explains what the self-service developer portal provides and how it enables teams to provision resources without waiting for platform team intervention.
What the Portal Provides
The openCenter Developer Portal gives application teams a curated, governed interface to:
- Browse available services — databases, caches, message queues, and middleware from an approved catalog
- Provision resources on demand — request a PostgreSQL instance, Kafka topic, or Redis cache via UI or API
- Manage team resources — view quotas, monitor usage, rotate credentials, and scale services
- Scaffold new applications — instantiate golden-path templates with pre-configured CI/CD, observability, and security
How It Works
Developer Request → Portal API → Git Commit (CRD manifest) → FluxCD Reconciliation → Running Service
Every portal action translates to a Git commit in the team's GitOps repository. There is no imperative provisioning — the portal is a UX layer over the existing GitOps workflow.
Key Design Principles
- GitOps-backed: Every action produces an auditable Git commit
- Policy-enforced: Kyverno validates all portal-generated resources
- RBAC-integrated: Portal permissions mirror Keycloak group mappings
- Self-service with guardrails: Teams operate freely within defined boundaries
Related Pages
- Portal Architecture — technical design and integration points
- Service Marketplace — available services catalog
- Onboarding — team self-enrollment workflow
- Templates — application golden paths
- Governance — quotas, policies, and approval gates