# The basics > How your app is organized in Ployz, and how a change reaches your servers. For agents: [llms.txt](https://ployz.dev/llms.txt) indexes the Ployz docs as Markdown. Picture boxes inside boxes: your organization holds your servers and projects, each project has environments, and each environment runs services on your servers. Everything you change is a draft until you deploy it. ```mermaid flowchart TD org["Organization"] --> servers["Servers"] & project["Project: my-app"] project --> prod["Environment: production"] & preview["Environment: a pull request's preview"] prod --> web["Service: web"] & pg["Service: postgres, with a volume"] ``` ## How your app is organized **Organization.** Ployz creates one for you when you first sign in. It holds your servers, your projects and your billing. See [Organizations and billing](https://ployz.dev/docs/account/organizations). **Servers.** Linux servers you own or rent, with Ployz on them. Together they're your own small cloud: they share a private network, and Ployz spreads your services over them. See [Add a server](https://ployz.dev/docs/servers/add-a-server). **Project.** One app and everything it needs to run, like a web app, its worker and its database. **Environment.** One complete copy of a project, with its own services, variables, volumes and addresses. Every project starts with `production`. Branch it into `staging` to change things without touching production, and turn on preview environments to get a copy for every pull request. See [Environments and branches](https://ployz.dev/docs/environments/environments). **Service.** One thing that runs: a web app, a worker or a database. It runs your GitHub repository, which Ployz builds, or a Docker image, as one or more replicas. [Service settings](https://ployz.dev/docs/services/settings) lists what you can set on one. **Volume.** A disk attached to one server, where a service keeps files across deploys and restarts, like a database's data. The service that uses it runs on that server. See [Volumes](https://ployz.dev/docs/services/volumes). An environment opens on its canvas. Each service is a card, with its volume underneath. ![A canvas with a GitHub service, a Docker image and PostgreSQL with its volume, all Online](https://raw.githubusercontent.com/getployz/ployz/main/docs/user/images/canvas-with-database.png) ## How a change ships Settings save as you change them, and config files when you click **Save**. Both turn pink, like a draft. Your servers keep running what they ran until you click **Deploy**; then Ployz makes them match. A few settings, like **Auto-deploy**, say "Takes effect at once" and skip the draft. The bottom bar collects your staged changes and counts them, like **1 change**. **Details** lets you review or discard each one, and **Deploy** ships them all. Each deploy becomes a deployment, with its own page and logs. See [Deployments](https://ployz.dev/docs/deploy/deployments). ![The bottom bar with one staged change](https://raw.githubusercontent.com/getployz/ployz/main/docs/user/images/bottom-bar-changes.png) A Git push deploys too, like **Deploy**: the services it builds get your latest commit, and every saved change goes along. To send staged changes with the next push, click **Save only** in **Details**, or Alt-click **Deploy**; changes you only staged stay behind. See [Deploy on push](https://ployz.dev/docs/deploy/github#deploy-on-push).