Cloud Providers
What each cloud provider Daintree can create hosts on needs and does: the credentials it asks for, who pays, the sizes and images it offers, what a stop keeps and still bills, how a machine stops by itself, how its host key is trusted, what delete removes, and providers that plugins contribute.
Each provider Daintree can create cloud machines on describes itself the same way: what it asks for, what a stop keeps and still bills, how a machine stops by itself, and how its ssh host key is trusted. Daintree words every dialog from that description, so the start and stop confirmations always match the provider. This page lists what each one says and does.
At a Glance
| Provider | You connect with | A stop keeps | While stopped | Stops by itself | Host key |
|---|---|---|---|---|---|
| Boat | An API key | Files in its home folder, for at least 14 days | Not billed | Lifetime, pushed back while in use; idle stop | From Boat's API |
| Agent 37 | An API key | Files and installed programs | Disk billed | Sleeps when idle | Agent 37's tunnel vouches for it |
| AWS | An access key, its secret and a region | Files on its disk | Disk billed | Idle stop | Read from the instance, or you confirm it once |
| Google Cloud | A service account key file | Files on its boot disk | Disk billed | Optional fixed lifetime; idle stop | From Google Cloud's API |
| DigitalOcean | A personal access token | Files on its disk | Billed in full | No | You confirm it once |
For the machines Daintree creates, memory and running processes are lost on a stop, Daintree asks for the provider's normal saving stop rather than a forced power-off, and deleting a machine deletes the disk created with it. For a machine you added, extra disks or saved snapshots, the provider's own rules apply. Every created machine carries two labels, daintree=1 and daintree-binding, which is how Daintree finds a machine whose create didn't answer.
Boat
On-demand Ubuntu machines that stop when idle and resume with their disk.
- Connect: an API key from Boat's dashboard. It must be able to read machines in at least one wallet. Who pays is Personal or an organization the key can read.
- Create: a size of Small (2 vCPU, 4 GB), Default (4 vCPU, 8 GB), Large (8 vCPU, 16 GB) or Extra large (16 vCPU, 32 GB), priced from your account's own rate. No region or image to choose. Daintree adds its SSH key after the machine exists, and Boat reports the machine's host key, which Daintree pins.
- Stop: Boat saves the disk first and refuses to discard work. Files in the home folder are kept;
/tmp, caches and memory aren't. A stopped machine isn't billed, and its saved disk is kept for at least 14 days; after that Boat may delete it, and the host then reads Saved disk expired and can't be started. - Lifetime: 2 hours by default, from 1 hour to 24 hours or Never, counted from each start and pushed back while a window here shows the host or its agents are working.
- Idle stop: Daintree asks Boat for a key scoped to reading, updating and stopping that one machine, for 30 days, and gives it to the host, which keeps it in memory only. The host uses it to extend the lifetime while it sees work and to stop the machine once its idle time ends. A connected computer replaces the key when it is lost or close to expiring, and removing the host revokes it, retrying if Boat can't be reached.
- Delete: permanent.
Agent 37
Persistent Linux machines that sleep when idle and keep their disk.
- Connect: an API key. A key belongs to one workspace, so who pays is always Workspace. A key with an IP allowlist works only from addresses on it.
- Before you connect to a machine: install Agent 37's
agent37command on this computer. Agent 37 machines are reached only through its tunnel (agent37 tunnelas ssh'sProxyCommand), signed in however that command signs in; Daintree passes it no credentials. The tunnel vouches for the machine, so there is no host key to pin or confirm. - Create: Small (2 vCPU, 4 GB memory, 12 GB disk), Medium (4, 8, 16), Large (4, 16, 24) or Extra large (4, 32, 32), from Agent 37's base Linux template. Daintree registers its SSH key with the workspace as Daintree first. Agent 37 has no way to recognize a repeated create, so a create whose answer was lost is only ever looked for, never sent again.
- Stop and sleep: a stop keeps files and installed programs, and loses running processes and memory. Sleep keeps memory too. Either way, Agent 37 bills only the disk.
- Idle: Agent 37 puts the machine to sleep once it has been idle; a new machine is created with 30 minutes, and one you added keeps its own setting, which may be off, until you pick an Idle after time on the host's details page, which sets Agent 37's timer to match. With sleep on, while this computer is connected, the connection itself keeps Agent 37's timer from running, so the host's idle time decides and Daintree puts the machine to sleep when it ends. With nothing connected, the host keeps the machine awake while it sees work through a link Daintree gives it, valid for 7 days. If that link has expired or couldn't be made, Agent 37's timer can put the machine to sleep even while work is running; the details page says which applies.
- Start: starts a stopped machine or wakes a sleeping one.
- Delete: permanent.
AWS
EC2 instances in your own AWS account. They run until stopped; a stopped instance keeps its disk.
- Connect: Access key ID (from an IAM user's security credentials, starting
AKIA, orASIAfor temporary keys), Secret access key, Session token (only for temporary keys) and Region, where the keys are checked and machines are created unless you choose another. China, GovCloud and isolated regions aren't supported. Who pays is the AWS account the keys belong to. - Permissions: checking the keys tests each EC2 action Daintree needs and names any that are missing:
DescribeRegions,DescribeInstances,DescribeImages,DescribeVpcs,DescribeSubnets,DescribeSecurityGroups,CreateSecurityGroup,AuthorizeSecurityGroupIngress,RunInstances,CreateTags,StartInstances,StopInstancesandTerminateInstances. Two more are optional: withoutGetConsoleOutputyou confirm each host key yourself, and withoutDescribeInstanceAttributea machine can't stop itself when idle. - Create: a region, an image (Ubuntu 24.04 LTS by default, or Ubuntu 22.04 LTS, Canonical's newest build for the type's architecture) and a type from the t3, m7i (Intel, x86-64), t4g and m7g (Graviton, Arm64) families. The instance gets a 32 GiB gp3 disk that is deleted with it, a public address in the region's default VPC, and the SSH key through its first-boot configuration. Prices aren't reported.
- Network: Daintree creates, or reuses, a security group named
daintree-sshin that VPC, makes sure it allows ssh (TCP port 22) from any IPv4 address, and puts each instance in it. ssh still needs the account's key. If you narrow that rule in the AWS console, the next instance Daintree creates in the VPC opens it again for every instance in the group. Daintree never changes a group of that name it didn't create; it refuses to use one. - Host key: on the first connect, Daintree trusts the key the machine presents when it matches the one in the instance's console output, refuses one that doesn't, and asks you to confirm the fingerprint when there is none to read (or the keys can't read console output). After that it holds the machine to the key it trusted, and a changed key needs your review.
- Stop: a normal EC2 stop that lets the OS shut down. The disk is kept and billed.
- Idle stop: the machine powers itself off from inside once its idle time ends, after checking its own identity with the instance metadata service. EC2 treats that as a normal stop. It can't do this if its root disk isn't EBS, if it is a spot instance or in an Auto Scaling group, if Daintree doesn't know its instance type, or if its shutdown behavior isn't stop; such a machine is left running. If the only problem is that the login Daintree uses can't run
sudowithout a password, Daintree stops it through the API from this computer instead, while connected. The details page says which applies. - Delete: terminates the instance. Only instances tagged by Daintree are listed.
Google Cloud
Compute Engine VMs in your own Google Cloud project. A stopped VM keeps its disk, which Google bills while it's kept.
- Connect: a Service account key, the JSON key file for a service account that can manage Compute Engine VMs, and optionally a Project (blank for the key's own project). Who pays is that project. The Compute Engine API must be enabled in the project.
- Create: a zone, an image (Ubuntu 24.04 LTS by default, Ubuntu 22.04 LTS or Debian 12), a subnet, and an e2-standard-2, e2-standard-4 or e2-standard-8 machine type. The VM gets a 30 GB balanced persistent boot disk that is deleted with it and an external address. Its metadata carries the SSH key for a
daintreeuser, turns OS Login off so that key works, and turns guest attributes on so the VM can publish its host key. Prices aren't reported. - Host key: Google Cloud reports it, and Daintree pins it.
- Lifetime: optional, Never by default. A limit is Google Cloud's own maximum run time, counted from each start; it can't be moved while the VM runs, so it stops then even if agents are still working. Choose a new limit while the VM is fully stopped (not suspended), and Daintree applies it the next time it starts the VM.
- Stop: a normal stop that gives the OS its shutdown and keeps the disks, which stay billed.
- Idle stop: as on AWS, the VM powers itself off from inside once its idle time ends, and Daintree stops it from this computer when only the power-off permission is missing. A VM in a managed instance group or with a local SSD is left running.
- Delete: permanent, with the boot disk Daintree created for it. Deleting a VM you added leaves its disks to their own deletion settings.
DigitalOcean
Droplets on your own DigitalOcean team: a Linux machine that runs until you stop it and bills until you delete it.
- Connect: a Personal access token with full access, or custom scopes covering Droplets, SSH keys, tags, regions, sizes, images and account reads. Who pays is the token's team, or Personal.
- Create: a region, an image (Ubuntu 22.04 LTS or later, Debian 12 or later; Ubuntu 24.04 by default) and a size with at least 2 GB of memory, cheapest first, with its hourly price. Daintree registers its SSH key on the account. A first-boot script then removes that key from
root, creates adaintreeuser, installs the libraries Daintree needs and turns on linger. On images that restrict unprivileged user namespaces through AppArmor, it lifts that restriction system-wide so the AppImage can run. It authorizes the key fordaintreelast, so the machine accepts it once the script has finished. - Host key: DigitalOcean doesn't report one, so you confirm the fingerprint once.
- Stop: a graceful shutdown, never a forced power-off. DigitalOcean bills a stopped Droplet in full until it's deleted.
- Idle: the machine doesn't stop when the host's idle time ends, because stopping wouldn't save anything. To stop paying, remove the host and delete its machine.
- Delete: permanent.
- Retrying a create: DigitalOcean has no way to recognize a repeated create. If a create goes unanswered and Retry's lookup finds nothing, it sends the create again, so check the console for an extra Droplet.
Providers From Plugins
An installed plugin can contribute more providers. You pick one by its name beside the built-in ones, and its account row names the plugin it comes from. A repository's project plugin can't: a repository must never be able to add something that creates machines on your account just by being opened. Building one is covered in Contribution Points.
A plugin's provider gets nothing until you agree. Connecting its first account asks Allow … to use your cloud accounts? and says that the plugin, not Daintree, then:
- Receives the credentials you enter, including when you check them, and those saved for any of its accounts;
- Chooses the machines Daintree connects to, and vouches for their identity;
- Creates machines that bill your own account.
Allow and continue covers every provider the plugin declares. If an update changes what its providers declare (the credentials they ask for, what they can do, their API address), its accounts pause until you allow it again with Review access on the account row. An account connected to an API address the provider no longer declares has to be connected again. Daintree hands a plugin the credentials one call at a time, and only while the provider still declares the address the account was connected with, but the plugin's code runs as a full process and can keep or send on what it is handed; allow only plugins you trust with those credentials.
While a plugin is off, blocked, failed to load or uninstalled, its accounts and machines stay listed as unavailable, with the last state Daintree saw and a link to the provider's console, and nothing is asked of the provider. Uninstalling the plugin from the Plugin Manager asks whether to keep its cloud accounts, credentials sealed for a reinstall, or remove them with their hosts; daintree-plugin uninstall always keeps them. Either way, nothing is stopped or deleted at the provider.