v1.0 · public beta · no cap

run it.
ghost it.
forget it.

crunr is the CLI that sends your script to AWS, streams logs back to your terminal, drops the outputs on your laptop, and torches the instance the moment it's done. Zero idle. Zero markup. Zero infra to babysit.

your aws. your bill.no controller VMSIGINT-proof teardown
~/research/diffusion
LIVE · streaming stdout
crunr · running cost
$0.00/this run
▲ $1.04/hr · spot · g5.xlarge
that EC2 you forgot
$847
still burning · 27 days idle
1command to run
~12scold start to streaming
$0idle cost, period.
100%your AWS account
The real bill

Your AWS bill isn't the compute.
It's the stuff you forgot to kill.

The staging box nobody touches on weekends. The g5 you spun up for “five minutes” three Fridays ago. The training job that finished at 2am while you were asleep, then billed you ‘til breakfast. Cloud is cheap by the hour and brutal by the month.

i-0a3f9b...e21
staging-api-v2 · t3.large
uptime 142d$284
i-0c7e1a...4d2
"test-gpu-dont-delete" · g5.xl
uptime 11d$278
i-09bb22...8f7
jupyter-fri-night · m5.4xl
uptime 3d 14h$74
i-04dd3c...9aa
finetune-v3-final-final · p4d.24xl
uptime 19h$622
i-0e1ff7...c10
scratch-instance-i'll-delete-it-tmrw · c6i.2xl
uptime 47d$432
i-08aa11...bd3
demo-monday · t3.medium
uptime 8mo$246
Surprise charges · last 12 months · ~10k devs surveyed

The collective “oh no” tax
on cloud compute.

$0
before crunr
the 9-step death march
  • 01open the AWS console, pray.
  • 02guess at instance types & AMIs.
  • 03fight security groups & SSH keys.
  • 04wait. wait. wait for boot.
  • 05scp your code up like it's 2008.
  • 06pip install & cross fingers.
  • 07babysit the job.
  • 08scp the outputs back, manually.
  • 09forget to terminate. cry next month.
9
steps, plus the one you'll skip
with crunr
one line. done.
  • crunr run train.py --gpu
  • auto-picks the cheapest matching spot box.
  • uploads code, installs reqs, runs the script.
  • streams logs to your terminal in real time.
  • downloads outputs/ back to your laptop.
  • terminates the box in a finally: block.
  • Ctrl+C? still terminates. crash? still terminates.
  • nothing left in your account. nothing.
  • your bill goes back to zero. for real.
1
command, end-to-end
/ 04 steps

The whole tool,
on one page.

$ crunr auth// 01

plug in your aws, one time, forever.

Interactive wizard. Access key, secret, region from a numbered menu — no memorizing ap-south-1 like a goblin. We write to ~/.aws/credentials, verify with a real call, peace.

$ crunr run// 02

send it. cheapest spot, auto-picked.

We poll live spot pricing, grab the cheapest box that matches your flags, rsync your code up, install your requirements.txt, kick off the job. stdout streams back like it's local.

outputs/ ←// 03

outputs come home on their own.

Anything your script drops into outputs/ rsyncs back to your laptop the moment the run finishes. Models, checkpoints, CSVs, generated images — all here, no manual scp.

finally: terminate()// 04

the instance gets torched. always.

Wrapped in a finally block. Job done — gone. Job crashed — gone. You Ctrl+C'd because lunch — still gone. Termination isn't a feature flag; it's the whole point.

/ the core design principle

zero
idle.
zero markup.

crunr has no infrastructure of its own. No controller VM. No always-on daemon. No SaaS dashboard skimming a monthly fee. The CLI on your laptop is the system. When you're not running a job, your AWS bill for crunr is $0.00 — and that's not rounded.

/ built for

For people who touch grass
between runs.

ML researchers · students
Train when you need to. Pay for the minutes. Stop.

"A 2-hour spot GPU run costs less than my oat latte."

Can't justify a permanent GPU box? Don't. Run experiments on the actual right machine, then walk away from a $0 bill until next time.

backend devs
Big ETL energy, zero infra debt.

"Bigger than my laptop, smaller than a platform."

Heavy data processing, batch jobs, video transcodes, scraping pipelines — fire it at crunr, walk back when the outputs land in your folder.

indie hackers · solo founders
Cloud compute without a DevOps minor.

"What's a VPC and why is it screaming."

No security groups to wire up. No AMIs to pick. No IAM YAML to learn. Just a key and a script — crunr handles the boring stack.

data folks
Burst, not boil.

"My laptop fans sound like a 737. Not anymore."

Process the big CSV. Run the sim. Generate the report at scale. Use the cloud the way it was supposed to be used — short, sharp, gone.

anyone with an aws horror story
Opened the bill. Saw the ghost. Never again.

"$847 from a box I forgot existed. Cooked."

If you've ever rage-googled "how do i find what's running in my aws account", crunr was literally built for you.

teams of one to ten
One CLI, many AWS profiles.

"--profile work, --profile client, --profile chaos."

Personal, work, client, scratch — switch with a flag. Credentials stay where AWS expects them. No new auth surface to manage.

/ ship it

One line. And you're free
of the AWS console forever.

$ pip install crunr
requires python 3.10+ · ssh · rsync · an aws access key. that's the list.
get crunrread the docs →