Skip to content

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 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 for research and deliverables that do not need an application backend. An Agent is a separately governed programmable specialist; a Project can implement agent behavior directly or integrate a supported provider. Start with the Project 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. Add Databases or Storage when the application needs them, and release to a Site when ready.

A Workflow can assign a task to an existing Project in a fresh conversation.

Next steps