Platform concepts

Concept	Meaning
Project	A top-level workspace that groups related services.
Service	An application unit connected to source code or a template. A project can contain multiple services.
Environment	A branch-specific deployment of a service, such as a production or development branch.
Resource	Compute or data infrastructure attached to an environment, such as a server, worker, database, queue, or cache.
Build	A recorded attempt to transform source and deployment configuration into deployable artifacts.
Deployment	The release of a successful build to the environment's runtime resources.
Agent	A temporary deployment worker that analyzes a new workload and detects the configuration Kuberns needs.
Runtime credits	The balance used to pay for running resources. The dashboard currently represents one runtime credit as one US dollar.

Projects, services, and environments

The main hierarchy is:

Project
└── Service
    ├── Environment: main
    └── Environment: development

An environment selects a repository branch and owns its deployment history, variables, domains, resources, and usage. Adding another branch creates another environment under the same service.

Builds and deployments

A build records source and configuration at a point in time. A deployment uses the resulting image and runtime configuration to update the environment.

Git push events, supported dashboard actions, template deployment, and agent completion can create or queue builds.

Resources are operated independently from the source service where appropriate. Their available lifecycle actions can include start, stop, restart, scaling, topology conversion, and termination. Trial and credit state can restrict these actions.