# Concepts

The core model behind Lizard: how your code is organized, how it's built, and how a release reaches production. Read these once and the rest of the docs will make sense.

For the model one level up — what a platform that runs your container for you is called, and how it differs from PaaS, FaaS and IaaS — read [container as a service](https://lizard.build/blog/container-as-a-service) on the blog.

## In this section

- [Architecture](https://lizard.build/docs/concepts/architecture) — the workspace → project → service hierarchy, managed addons, and cross-resource references.
- [Build Pipeline](https://lizard.build/docs/concepts/build-pipeline) — how source becomes a container image (synthesized Dockerfile, repo Dockerfile, or lizardpack auto-detect) and what triggers a rebuild.
- [Deployments](https://lizard.build/docs/concepts/deployments) — the build-and-release lifecycle, restarts vs. redeploys, and live config changes.