# Organizations & projects > How organizations and projects relate on snoozestack. [HTML version](https://snoozestack.com/docs/organizations-projects-sources/) · [Docs index](https://snoozestack.com/llms.txt) ### Organization The account, billing, and admin boundary. Your admin login belongs to exactly one organization; that organization owns every project you create. Org-wide settings (its name, admin accounts) are edited from the console. ### Project A complete, isolated app backend: one [runtime](https://snoozestack.com/docs/runtime.md) with its own database, storage, queues, schedules, signals, sites, and users, served at `https://.snzzz.com` — a domain of its own, separate from snoozestack.com, so nothing a project serves shares an origin, a cookie scope or a site boundary with the console. What the project *is* lives in your repo — the committed `snoozestack/` folder — and the hosted side runs what you publish. An organization holds up to the number of projects its plan allows — one on Free, three on Starter, ten on Pro (see [pricing](https://snoozestack.com/pricing/)). One project per app is the common case, and nothing is shared between them — not data, not users, not sign-in providers. The allowance counts *running* projects: an owner can stop a project (its API and sites answer “paused”, nothing is deleted) to free a slot, and when an organization is over its allowance after a downgrade the newest projects are paused until there is room again. **Diagram:** Organization · Project: my-app · one runtime · its own data · Project: admin-tool · one runtime · its own data · Project: mobile-app · one runtime · its own data ### Namespaces Within a project, state is namespaced: `dev` is your machine, `default` is live, and each person's preview (`snoozestack preview`) gets its own. Each namespace holds genuinely separate data, storage, queues, and secret overrides — so exercising a preview never touches live rows, and a device registered in development can never receive a live push. ### Creating a project ```bash title="terminal" snoozestack projects create my-app snoozestack link --project my-app # records it in snoozestack/project.toml ``` See [Using the console](https://snoozestack.com/docs/portal-tour.md) for where each of these lives in the console.