crunr icon

crunr

crunr is a local CLI for sending compute jobs to AWS, running them in your own account, and collecting logs and outputs back on your machine. It supports GPU and CPU workloads without requiring a cloud console or hosted backend.

crunr

Local CLI for running compute jobs on AWS

crunr is a local command-line tool for shipping compute jobs to AWS from your terminal. It is designed for scripts that need more machine than a laptop can provide, especially GPU workloads, batch processing, and other jobs that should end cleanly when they finish.

The workflow is straightforward: install the CLI, authenticate against your AWS account, run a script with `crunr run`, watch logs stream back, and receive outputs in your local folder. The docs say the tool handles provisioning, upload, execution, collection, and termination inside a single process on your machine, with no crunr server in the middle.

The product emphasizes that your AWS credentials stay on your laptop, EC2 instances use an IAM role instead of your access key, and the instance is terminated automatically inside a `finally`-style cleanup path. The site also describes optional S3 persistence, multiple AWS profiles, and support for both GPU and CPU jobs.

Core capabilities

Local AWS authentication

Use `crunr auth` to save AWS credentials locally, verify them with STS, and manage named profiles from the CLI.

Language-agnostic script execution

Run Python, shell, Node, R, Go, or other local scripts without rewriting them for a cloud SDK or decorator-based workflow.

Instance selection controls

Launch the cheapest matching AWS instance for the job, with options for GPU, memory, exact instance type, spot pricing, region, and disk size.

Live logs and result collection

Stream stdout and stderr live while the job runs, then sync `outputs/` back to the local machine or optionally back jobs with S3.

Automatic cleanup

Terminate the instance automatically when the job ends, even on failure or Ctrl+C, so billing stops when the work is done.

No hosted middleman

Provide a local CLI-only workflow with no crunr backend server or long-lived cloud daemon, so jobs run in the user's AWS account.

Where crunr fits

  • ML and AI workloads

    Run training, fine-tuning, or evaluation jobs on the GPU instance that fits the workload, without maintaining a permanent GPU box.

  • Data processing and ETL

    Launch batch jobs and heavier data processing work directly from the terminal, then collect results locally when the run completes.

  • Early-stage engineering

    Give startup teams a way to ship compute jobs on AWS before they have a dedicated DevOps setup or Terraform-based infrastructure.

  • Research and student experiments

    Run experiments on real hardware for research or coursework while paying only for the time the instance is active.

  • GPU rental replacement

    Move ad hoc GPU jobs away from rented platforms and into your own AWS account when you want tighter control over billing and credentials.

Pros and Cons

Pros

  • Runs as a local CLI, so there is no crunr server or hosted backend to manage.
  • Keeps AWS credentials on your machine and uses IAM roles on launched instances.
  • Handles provisioning, upload, dependency install, log streaming, output collection, and termination in one flow.
  • Supports both GPU and CPU jobs across common script types such as Python and shell.
  • Includes optional S3 persistence, multiple profiles, and a command set for auth, jobs, logs, SSH, ps, clean, and s3.

Cons

  • Requires an AWS account plus local dependencies such as `ssh` and `rsync`.
  • The docs note that spot instances can be interrupted with short notice if you choose spot pricing.
  • The public pricing page was unavailable in the collected sources, so cost details are limited to examples and docs coverage.

FAQ

How do I use crunr?

crunr is a local CLI that runs on your machine and connects directly to AWS. You install it with `pip`, authenticate with an AWS access key, and run jobs with commands like `crunr run`.

What do I need before installing crunr?

According to the docs, you need Python 3.10 or newer, `ssh`, `rsync`, and an active AWS account with an IAM access key. macOS and Linux work out of the box; Windows is supported through WSL 2 or Git for Windows if `ssh` and `rsync` are available.

What happens when a job finishes?

`crunr run` launches a compute job, streams stdout and stderr in real time, and then syncs outputs back to your laptop. The docs also mention optional S3 persistence for outputs and a job history view with `crunr jobs`.

Is crunr open source and how is it priced?

The source says `crunr` is open source and MIT licensed. The public docs describe the CLI, setup flow, command reference, and security model, but the pricing page itself is not available in the collected material.

Quick Facts

Category
Developer Tool
Platform
macOS, Linux, and Windows via WSL 2 or Git for Windows
Delivery model
Local CLI that talks directly to AWS
Primary users
ML engineers, data scientists, startup engineers, researchers, GPU renters, and AWS users
License
MIT
Source domain
crunr.com