Daytona

Cloud sandboxes for AI agents, containers by default with VM and GPU options.

Provider: default
Kind: Worker
Category: Compute
Official docs: https://www.daytona.io/docs/en/limits/

Properties · 3 set by this component

property	type	values	required	kind default	this component
accelerator	enum	none \| gpu \| asic	no	none	inherited
concurrency	integer	—	no	—	inherited
fanoutStrategy · advanced	enum	none \| push \| pull \| hybrid	no	none	inherited
fanoutThreshold · advanced	integer	—	no	—	inherited
idempotent	boolean	—	no	false	▸ false
instances	integer	—	no	—	inherited
isolation · component property	enum	container \| vm	no	container	inherited
managed	boolean	—	no	false	▸ true
memoryGb · component property	integer	—	no	1	inherited
rateControl · advanced	enum	none \| fixed \| aimd	no	none	inherited
schedule	string	—	no	—	inherited
tier · component property	enum	tier-1 \| tier-2 \| tier-3 \| tier-4	no	tier-1	inherited
trigger	enum	queue \| stream \| schedule \| batch \| manual	yes	—	▸ manual
vcpus · component property	integer	—	no	1	inherited

Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Push fan-out without a celebrity thresholdwarning

push-fanout-without-celebrity-path

Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.

— all of these hold:
— the node's `fanoutStrategy` is "push"
— the node's `fanoutThreshold` has no value
— the design contains a node of kind graph-database

Shared worker pool across queueswarning

shared-worker-pool-across-queues

One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.

— all of these hold:
— the node has more than 1 incoming edge from a queue
— the design requirement `isolation.perQueue` is true

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "daytona", component: "daytona" }

Other Worker products · 82

SchedulerXalibaba-schedulerxalibabacloudworker Amazon AppFlowaws-appflowawsworker AWS B2B Data Interchangeaws-b2b-data-interchangeawsworker AWS Batchaws-batchawsworker AWS Glue DataBrewaws-databrewawsworker AWS DataSyncaws-datasyncawsworker AWS Deadline Cloudaws-deadline-cloudawsworker AWS Entity Resolutionaws-entity-resolutionawsworker Amazon EventBridge Scheduleraws-eventbridge-schedulerawsworker AWS Fault Injection Serviceaws-fisawsworker AWS Glue crawleraws-glue-crawlerawsworker AWS Glue for Ray jobaws-glue-ray-jobawsworker AWS Application Migration Serviceaws-mgnawsworker Amazon MSK Connectaws-msk-connectawsworker Amazon SageMaker AI Training Jobaws-sagemaker-training-jobawsworker AWS Systems Manageraws-systems-managerawsworker AWS Thinkbox Deadline 10aws-thinkbox-deadlineawsworker AWS Glue jobglue-jobawsworker Azure Automationazure-automationazureworker Azure Batchazure-batchazureworker Azure Chaos Studioazure-chaos-studioazureworker Azure Data Factoryazure-data-factoryazureworker Azure Data Shareazure-data-shareazureworker Azure Database Migration Serviceazure-database-migration-serviceazureworker Microsoft Entra Connect Syncazure-entra-connect-syncazureworker Microsoft Graph Data Connectazure-graph-data-connectazureworker Azure Storage Moverazure-storage-moverazureworker Azure Update Managerazure-update-managerazureworker Browser Runcloudflare-browser-runcloudflareworker Cloudflare Snippetscloudflare-snippetscloudflareworker Cloudflare Zarazcloudflare-zarazcloudflareworker Airbyteairbyteworker Airflow DAGairflow-dagworker Chaos Meshchaos-meshworker Chunkrchunkrworker Container workercontainer-workerworker Cron jobcron-jobworker E2Be2bworker Embulkembulkworker Fan-out daemonfanout-daemonworker

and 42 more → Worker page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Daytona: composable cloud sandboxes for AI agents, containers by default with VM, GPU and macOS options.
3# Per "Limits", Tier 1 organizations get a 10 vCPU pool and 10,000 API requests a minute, rising with verified spend to Tier 4;
4# per "Sandboxes" a sandbox defaults to 1 vCPU, 1 GB of memory and 3 GiB of disk, with auto-stop and auto-archive intervals.
5schemaVersion: "1"
6type: "component"
7id: "daytona"
8kind: "worker"
9provider: "default"
10docs: "https://www.daytona.io/docs/en/limits/"
11defaults:
12  managed: true
13  trigger: "manual"
14  idempotent: false
15properties:
16  tier:
17    type: "enum"
18    values: ["tier-1", "tier-2", "tier-3", "tier-4"]
19    default: "tier-1"
20  isolation:
21    type: "enum"
22    values: ["container", "vm"]
23    default: "container"
24  vcpus:
25    type: "integer"
26    default: 1
27  memoryGb:
28    type: "integer"
29    default: 1

The same page as markdown, for an agent: /catalogue/components/daytona.md