crunr cloud is live — no AWS needed
Run code,not infrastructure.
One command turns your local script into a cloud compute job. No AWS setup. No DevOps. No SSH. Your code runs, outputs land on your laptop, and the machine disappears the moment it's done.
you, after $ crunr run
$
meanwhile, in the cloud
You see $1.50/hr. You pay $4,500/mo.
Compute rates are cheap and honest. Everything around compute isn't — the instance running all weekend while you sleep, the engineer keeping it alive, the setup that took three days, the 3am alert when a job silently hung and kept billing until breakfast. None of that shows up on the pricing page.
invoice / your cloud, 2026
invoice / your cloud, 2026
One command. Code runs in the cloud.
You type crunr run. Everything between hit-enter and results-in-your-folder is handled. No console. No tab to leave open. No DevOps. No instance you'll forget about.
Write a script. Type one command.
Any script you'd run locally — Python, Node, bash, R, go. No SDK. No decorators. No cloud-specific rewrites. Hit enter, close your laptop.
Spins up a box, runs your script.
Picks the cheapest matching spot instance, rsyncs your code, installs your deps (pip, apt, npm — whatever your script needs), runs the job. All without touching a dashboard.
Results in your folder. Bill drops to zero.
Outputs sync back to your laptop. The instance terminates the second the job finishes — or if it crashes. You come back to results, not a running charge.
One CLI. Four places to live in it.
crunr runs between your terminal and the cloud. Shell, CI, scripts, monitoring — one binary, one command.
For AI engineers. Indie hackers. Anyone running scripts.
No cloud knowledge required. No job title required. Run the script, get the results, and the box dies when you're done.
AI & ML engineers
Run training jobs on the exact hardware you need. No shared clusters, no idle costs, no cloud console.
Indie hackers & solo founders
Add cloud compute to your product without hiring DevOps or signing cloud contracts. One command, done.
Startup engineering teams
Get compute working before you've written your first Terraform file. Or instead of one entirely.
Data scientists
Run jobs on real data volumes without booking a permanent cluster you don't always need.
Researchers & students
Run on the right machine for each experiment. Pay for minutes, not month-long bookings.
Any developer with a script
If it runs locally, it runs with crunr. No cloud knowledge required. No DevOps. No overhead.
No setup. Or bring your own AWS.
crunr cloud takes 60 seconds — no AWS account, no IAM, no policies. If you already have AWS and want direct control, BYOC connects your laptop straight to your account.
crunr cloud
No AWS account. No IAM user. No policies. Get an API key at cloud.crunr.com and you're running in under a minute.
crunr cloud login --key <api-key>crunr run train.py --gpu- no aws account required
- no iam users · no policies
- your code and outputs are yours
bring your own aws
One-time setup. Your code goes directly from your laptop to your AWS account — zero relay, not even crunr cloud in the path.
crunr authcrunr run train.py --gpu- direct to aws — zero relay
- keys never leave your machine
- your account, your bill, your data
Direct from your laptop to AWS. Not even crunr sees it.
Direct from your laptop to AWS — no crunr backend, no crunr cloud relay, nothing in between. Your credentials, your code, and your outputs never leave your own account. Full AWS compatibility. Full ownership. Zero middleman.
Your keys stay on your laptop.
crunr reads from ~/.aws/credentials — the same file the AWS CLI and boto3 use. Nothing is sent to any crunr server, including crunr cloud.
~/.aws/credentialsDirect to AWS. Zero relay.
The CLI talks directly to AWS over the network. No crunr backend. No crunr cloud server in the path. Between jobs, crunr has zero footprint.
your laptop → awsAccess keys never reach EC2.
Instances use an attached IAM role — not your access key. Your AWS credentials are never written to any instance crunr launches.
IAM role · not your keyDon't trust us. Read it.
Every credential write, every API call, every file transfer is auditable on GitHub. If something looks wrong, you'll find it.
github.com/crunr-dev/crunrcrunr & crunr cloud never see, store, or transmit
- your aws access key
- your secret key
- your code
- your data
- your outputs
- your job history
- anything via crunr cloud
- anything via any crunr server
Your next GPU job. One command.
Free. Open source. No DevOps. On crunr cloud: just Python and an API key. On AWS: bring your own account.