# Services

Services support the work you create in Playbooks: supplying inputs, keeping editable results, storing application data, running background tasks, and checking what happened. Start with the capability you need, then check where it is available.

Chats, Agents, and Projects share conversational content capabilities. Projects also use application services during development; Sites operate independently configured production services. A service's availability does not transfer data, credentials, or permissions between those places.

## Choose where the work runs

| I want to… | Start here |
| --- | --- |
| Have an Operator use a website | [Browser sessions](/docs/services/browser) |
| Read a public page from my application | [Application Web Access](/docs/services/web-access) |
| Run commands and inspect a working preview | [Project sandboxes](/docs/services/sandboxes) |
| Host a static site or a backend at a visitor-facing address | [Release a first Site](/docs/sites/quickstart) and [production runtime](/docs/sites/runtime) |
| Give visitors an application login | [Application sign-in](/docs/services/identity) |
| Generate a response from my backend | [Application inference](/docs/services/inference) |
| Look up an address or display a map | [Maps and location](/docs/services/maps) |
| Generate an illustration for an application | [Media generation](/docs/services/media) |
| Call a reusable specialist from my application | [Agent access](/docs/agents/access) and [execution](/docs/agents/execution) |

## Inputs and execution

Bring material into a conversation, develop it into useful work, and decide how to retain or share the result.

- [**Browser** Inspect and interact with websites during authorized work.](/docs/services/browser)
- [**File system** Keep editable working files in Chats, Agents, and Projects.](/docs/services/file-system)
- [**Sandboxes** Run Project development commands and working previews.](/docs/services/sandboxes)
- [**Sources** Supply precise inputs to Chat, Agent, and Project conversations.](/docs/services/sources)

For example, attach a spreadsheet as a Source, develop a report in the File system, and retain an interactive calculator as an Artifact. Those are deliberate choices: editing the report does not change the original spreadsheet, and sharing the calculator does not expose its producing conversation.

For retained interactive experiences, see [Artifacts](/docs/artifacts/overview).

For lasting background across tasks, use configuration [Files](/docs/configuration/files).

## Data and automation

Build application behavior in a Project, then configure the production resources needed by its Site.

- [**Databases** Store structured records in the correct development or production environment.](/docs/services/databases)
- [**Jobs** Run application work outside an interactive request.](/docs/services/jobs)
- [**Storage** Keep application uploads and objects separate from working files.](/docs/services/storage)

A customer portal might keep account records in a database, uploaded documents in Storage, and prepare exports through Jobs. Releasing its code does not automatically copy development records or credentials into production.

## Visibility and quality

Use evidence from the appropriate environment to investigate problems and judge whether work is ready.

- [**Analytics** Understand measured traffic reaching a Site.](/docs/services/analytics)
- [**Logs** Investigate Project development and Site production execution.](/docs/services/logs)
- [**Monitoring** Review production exceptions in their Site release context.](/docs/services/monitoring)
- [**Security** Review Project application scan findings and their coverage.](/docs/services/security)
- [**Testing** Check application behavior and understand current testing limitations.](/docs/services/testing)

## Content, execution, and diagnostics by surface

A dash means the service is unavailable on that surface.

| Capability | Chats | Agents | Projects | Sites |
| --- | --- | --- | --- | --- |
| Analytics | — | — | — | Measure production traffic |
| Browser | Browse authorized websites | Browse authorized websites | Browse websites and inspect previews | — |
| Databases | — | — | Store development records | Store production records |
| File system | Edit files in the Chat | Edit files in the Agent’s working tree | Edit files in the Project’s working tree | — |
| Jobs | — | — | Develop background tasks | Run production tasks |
| Logs | — | — | Inspect development logs | Inspect production logs |
| Monitoring | — | — | — | Investigate production exceptions |
| Sandboxes | — | — | Run commands and working previews | — |
| Security | — | — | Scan application source | — |
| Sources | Attach conversation inputs | Attach conversation inputs | Attach conversation inputs | — |
| Storage | — | — | Store development uploads | Store production uploads |
| Testing | — | — | Check application behavior in development | Verify the live release with production authorization |

Each article explains the relevant scope and limitations. Supported provider setup, resource permissions, and funding still govern actual use.

## Related concepts

Use [Sharing](/docs/concepts/sharing) for collaboration and distribution, [Plans](/docs/operator/plans) for reviewed execution, and [Prompts](/docs/composer/prompts) for writing requests. External account setup belongs in [Configuration](/docs/configuration/overview). Production execution is covered by [Site Runtime](/docs/sites/runtime).