Prodvana has six core concepts that the platform is built upon. These six concepts are exposed as gRPC and REST APIs to allow for easy integration into existing workflows and tooling.

This is organized from the point of view of a developer starting of the application or product that they are managing.


The application scope is a collection of Services and Capabilities that are dependent on one another in a way that fulfills a business's need. The application defines the context and management policies for its constituent pieces based on its business requirements. Within an application, there are release channels where services live and pipelines operate (see below).


Pipelines define your change management process. They are dynamically built by understanding the environment and constraints that are configured for your application. They can be run sequentially or in parallel. Pipelines can be initiated by a user or by events. Pipelines are used as building blocks to converge an application to a certain state in production.


Services are the underlying components of an application. Most applications will have multiple services that communicate with each other and other systems.


Capabilities are 3rd party systems that your application relies on. Capabilities are provided by outside vendors or other teams within your organization.


Integrations are 3rd party systems that you wish to use in the control flows for managing your application. Examples of these are monitoring and observability systems, docker registries, ticketing systems, etc.


Runtimes are where services you create are run. Examples are Kubernetes clusters, serverless systems, or other job-running frameworks. Runtimes are linked to your Prodvana account and are managed by you. Runtimes support extensions that increase their functionality and usefulness to the platform. Example extensions include cost, service meshes, and security scanning.