# Build

Build turns a local source directory into an immutable container artifact. It snapshots your source, runs the build, and stores the resulting Open Container Initiative (OCI) image in Container Registry.

## Why use Build?

Running software starts with packaging its source and dependencies into something a runtime can execute. Build handles that step and gives you a recorded result that downstream tools can identify by its digest.

## What you can do

- Submit a snapshot of the current directory with the CLI.
- Inspect build status, follow logs, and cancel an unfinished build.
- List previous Builds and inspect their resulting Artifacts.
- Pass the published image to Run or another compatible OCI consumer.

## Core concepts

A **Build** records the source, execution status, logs, and result. An **Artifact** identifies the immutable OCI output. Its digest identifies the image content, so a deployment can refer to an exact result.

Build packages software. Runtime configuration, Secret bindings, and hostnames are configured separately in Run. This keeps application credentials out of the build output.

## Use Build

Read the [CLI reference](/docs/build/reference/cli) for commands or the [API reference](/docs/build/reference/api) for resources, request fields, and responses.

## Related services

- [Container Registry](/docs/scr)
- [Run](/docs/run)

---

Company: Socra — Multiply Your Judgment
Canonical URL: https://cloud.socra.com/docs/build