# Ray and Daytona

> Which sandboxes and snapshots exist, and what they are costing.

Source: https://heyray.io/integrations/daytona

Ray is an AI teammate that works in your team chat, on Slack today. Connect Daytona and it can do the Daytona part of a request without anyone leaving the conversation: read what it needs, draft the change, and leave it for you. 13 reads run without asking. Writing to Daytona is not switched on yet.

## What Ray reads in Daytona

Reading changes nothing, so Ray never stops to ask whether it may look something up.

- Sandboxes, snapshots, and volumes
- Organization usage and available regions
- Sandbox health and build logs

## What Ray writes

Ray reads Daytona and answers from it in the thread. Writing to Daytona is not switched on yet, so there is nothing to approve.

## Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

- Create, archive, or delete a sandbox
- Run a command inside a sandbox
- Delete files or a git branch
- Touch API keys and organization roles

## Ask it like this

- "@Ray how many sandboxes are running, and what are we spending?"
- "@Ray which sandboxes have been running longest?"
- "@Ray why did that snapshot build fail?"
- "@Ray what regions can we run in?"

## Connecting Daytona

Every person on the team connects their own Daytona account on Daytona's own login screen, so Ray can only reach what that person can already reach, and the history in Daytona shows who actually asked. Passwords never pass through Ray. Disconnecting Daytona or uninstalling Ray revokes the connection.

## More

- This page for people: https://heyray.io/integrations/daytona
- Every integration: https://heyray.io/integrations.md
- Install Ray: https://heyray.io/install.md
- Pricing: https://heyray.io/pricing.md