Coiled Product Detail

Easy to Use

Coiled is designed for humans. We use Coiled daily and love the experience. We hope you do too.

Easy Setup in Your Cloud Account

Why it matters.
By using your own cloud account, you keep your data and computation easily accessible and under your control. You can get started with just a few clicks or right in your terminal.

Our Design.
To let Coiled manage resources in your account, you give us the access key for a specially created IAM role. This IAM role only needs a specific set of permissions, so you can limit Coiled’s access to only what’s needed to run a cluster.You can create these roles manually, or, for AWS users, you can do all of this setup with a quick script, which you run from either your local machine (if you have the AWS CLI configured) or by logging in to the AWS console and running our script from AWS CloudShell (see our documentation to learn more).

Easy to setup in your cloud account

Package Sync

What is it?
Replicate your local software environment to your cluster, allowing for both reliable execution and rapid iteration.

Why it matters.
Safely transport your local code to your cluster without fiddling with credentials. Rapidly iterate on locally developed software. No more painful mismatched version errors or fighting with Docker.

Our Design.
When you enable package sync, we plug into conda and pip to scan every locally installed package. Then we figure out how to replicate these packages on a remote machine.The local and remote environments often differ in platform (macOS vs Linux) or architecture (x86 vs ARM), requiring different packages. We intelligently fuzz the environment, allowing us to ignore highly platform dependent packages, while leveraging conda/pip to fill in the gaps resulting from underlying platform differences and still maintain critical compatibility.Then in your remote cluster, we rapidly install these packages on all your Dask workers. This process is highly optimized to improve startup time, often beating the speed of a Docker pull, resulting in a fast, seamless experience while still being highly flexible. For locally installed or private git packages, we build a wheel locally, store it on S3, and pull it onto your workers. The S3 bucket has auto-delete policies to ensure code privacy.

Credentials

What is it?
Full access to most VM instance types on the fly.

Why it matters.
You can use the cluster as an extension of your laptop, rather than a separate entity, without going through the frustration of setting up permissions and authentication.

Our Design.
We generate temporary STS tokens that replicate your local AWS permissions, and ensure every worker has them. For Google Cloud, we use a service account if you provide one.

Level up your Dask using Coiled

Coiled makes it easy to scale Dask maturely in the cloud