Daytona

Sandboxes for agents and code runs, controlled from an app: create, start, stop and delete them. A sandbox's preview URLs and its toolbox stay outside the Gateway. Self-hosted Gateways only, since one key is the whole Daytona organization's.

API keyCopy Anchor Link

1. Sign in at app.daytona.io, in a Daytona organization kept for this Gateway: any key reaches every running sandbox in its organization.
2. Open Keys and select Create Key. Give it a name and an expiry, and pick only the permissions the apps need: write:sandboxes and delete:sandboxes to create and remove sandboxes, and the snapshot or volume ones if an app manages those. Reading sandboxes, snapshots and regions is always allowed. Leave manage:api_keys, manage:secrets, manage:billing and the region and runner permissions off.
3. Copy the key and keep it somewhere safe: Daytona shows only a masked value afterwards.

Add it to your Gateway. It asks for the key:

everyapp provider add daytona

Use it in an appCopy Anchor Link

In the app's everyapp.config.ts:

capabilities: {
  daytona: { access: "read", why: "What the app does with it." },
},

The app calls Daytona's API with integrationFetch(), and the Gateway adds the key. Use "write" if the app changes things. More in API providers.

Check it worked: everyapp provider show daytona shows the key as set.

Something wrong or missing? Open an issue.