# Projects

A Project is a place to build a coherent application: its interface, routes, business logic, source, and development resources. You can describe an outcome conversationally, inspect working changes, and keep improving the source. A Project does not become a production Site just because its preview works.

## Development and production

The Project owns source and working previews. A [Site](/docs/sites/overview) owns a validated production release, visitor access, operation, data, and recovery. One Project can supply multiple independently configured Sites. Source edits do not update those Sites until an authorized release selects a specific revision and destination.

Use a [Chat](/docs/chats/overview) for research and deliverables that do not need an application backend. An [Agent](/docs/agents/overview) is a separately governed programmable specialist; a Project can implement agent behavior directly or integrate a supported provider. Start with the [Project quickstart](/docs/projects/quickstart).

## Example: build an intake portal

A portal that accepts requests, stores records, and lets authorized people change status belongs in a Project. The Project contains the source and development setup; its working preview lets you evaluate the workflow before release.

Begin with a small user journey in [Quickstart](/docs/projects/quickstart). Add [Databases](/docs/services/databases) or [Storage](/docs/services/storage) when the application needs them, and release to a [Site](/docs/sites/overview) when ready.

A [Workflow](/docs/workflows/steps) can assign a task to an existing Project in a fresh conversation.

## Next steps

- [**Configuration** Set development guidance and authorized resources.](/docs/projects/configuration)
- [**Development** Turn a requested change into a checked preview.](/docs/projects/development)
- [**Lifecycle** Manage collaboration, export, and retirement.](/docs/projects/lifecycle)
- [**Releases** Prepare a revision for a specific Site.](/docs/projects/releases)