> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/concepts.md).

# Concepts

Pipekit introduces a handful of terms on top of Argo Workflows. This section defines each one and points into the task-oriented documentation under [Using Pipekit](/using-pipekit.md) for the day-to-day surface.

If you're new to Pipekit, start with [Workflow vs Pipe vs Run](/concepts/workflow-vs-pipe-vs-run.md). It disambiguates the three terms readers most often confuse.

## Core terms

* [Pipe](/concepts/pipe.md): A logical container for one Argo `Workflow` definition and the history of every run of it.
* [Run](/concepts/run.md): A single execution of a Pipe.
* [Workflow vs Pipe vs Run](/concepts/workflow-vs-pipe-vs-run.md): Disambiguating Argo's `Workflow`, Pipekit's `Pipe`, and Pipekit's `Run`.
* [Cluster](/concepts/cluster.md): A Kubernetes cluster registered with Pipekit.
* [Organization](/concepts/organization.md): Pipekit's top-level tenant.
* [Pipekit Agent](/concepts/pipekit-agent.md): The in-cluster component that brokers commands and status between Pipekit and Argo.
* [Templates](/concepts/templates.md): Reusable `WorkflowTemplate` and `ClusterWorkflowTemplate` definitions Pipekit manages across clusters.
* [Cron & Externally Triggered](/concepts/cron-and-externally-triggered.md): Execution models that bypass direct submission.
* [Access Control](/concepts/access-control.md): Workspaces, roles, and IdP group bindings.
* [Pipekit Cloud vs Self-Hosted](/concepts/cloud-vs-self-hosted.md): Deployment models, side by side.