API producers
Register ownership, submit OpenAPI contracts, resolve validation findings and promote approved versions through environments.
API lifecycle control
Turn API intent into governed, versioned and observable gateway delivery.
The product
DevPortal gives producers, consumers and platform teams a shared workflow without collapsing their responsibilities into one service.
Every request is admitted against ownership, policy and gateway capabilities before it can create infrastructure change.
Shared platform, clear responsibilities
DevPortal coordinates the API lifecycle without turning governance into a central bottleneck.
Register ownership, submit OpenAPI contracts, resolve validation findings and promote approved versions through environments.
Discover available APIs, register applications, request subscriptions and follow access decisions without opening infrastructure tickets.
Define policies, qualify gateway capabilities, supervise reconciliation and retain evidence for every production change.
Lifecycle
Each stage produces a durable result that can be inspected, approved and replayed.
OpenAPI contract, exposure target and policy intent.
Ownership, semantics, secret references and provider capabilities.
Policy gates and production decisions remain explicit.
Versioned manifests flow through GitLab and Argo CD.
Health, drift, events and rollback stay observable.
Product capabilities
Human workflows and automation use the same durable operations, policies and audit trail.
Validate OpenAPI structure, semantic rules, ownership metadata and organization-specific extensions before publication.
Prepare, approve, publish, promote and roll back versioned APIs with an explicit history of every decision.
Manage applications, managed identities, subscriptions, credentials and access requests within tenant boundaries.
Preview compatibility, provision or adopt instances, assign zones and decommission infrastructure deliberately.
Materialize desired state in GitLab, reconcile it with Argo CD and expose the resulting resources and revisions.
Inspect operation steps, events, health and drift in a human view, with JSON and YAML available when needed.
Composable architecture
The product and consumer control plane.
The gateway fleet control plane.
Independent by design. Portal API remains useful without gateway provisioning. Portal Operator can be introduced when the platform is ready to manage gateway instances.
Provider-aware delivery
Fits the platform you operate
DevPortal connects identity, source control, delivery and runtime concerns through explicit boundaries. Each integration remains observable and replaceable.
Operational outcomes
Restore a known successful API version without reconstructing intent.
Follow validation, merge requests, resources, reconciliation and events.
Use managed references while Keycloak enforces tenant-aware access.
Adopt progressively
Portal API
Use contract admission, publication, applications and subscriptions while existing platform processes continue to provision gateways.
Portal API + Portal Operator
Add instance provisioning, adoption, zone assignment and GitOps reconciliation without changing the producer or consumer experience.
Frequently asked
No. It governs API intent and delivery while Kong or Gloo Gateway remains responsible for runtime traffic.
Yes. Product governance, publication and consumer self-service remain available independently. Operator capabilities can be introduced later.
Compatibility is evaluated before infrastructure change. Unsupported semantics are rejected explicitly instead of being silently ignored.
Yes. Publications are versioned so operators can restore a known successful state with its associated evidence.
Contracts contain managed references rather than secret values. Access is constrained by Keycloak roles and tenant boundaries.
A controlled path to production