▸ ephemeral gpu sessions for coding agents
One command gives Claude Code a real GPU. No AWS account, no SSH keys, no setup.
▸ why gpus r us
01
Runs entirely in our infrastructure. No AWS, no IAM roles, no VPCs. Your agent gets a GPU shell — you don't touch a thing.
02
nvcc, the CUDA toolkit, and accelerated libraries — pre-built and ready to compile. No driver installs, no environment setup, no wasted time.
03
Per-second billing. Your agent can iterate on the same session all day — you're only charged for actual GPU time.
04
When the work is done, your agent opens a pull request with the results. Your code, your branch, zero manual steps.
▸ how it works
You describe the task. Your agent handles the rest — provisioning, iterating, and cleaning up when done.
01
One command installs and configures everything. Your agent picks up the GPU tools automatically — no config files, no manual steps.
02
Describe the task in plain language. Your agent picks the right environment and provisions a GPU — ready in under a minute.
03
Your agent compiles, benchmarks, reads the output, and retries — all in one session. When done it terminates and you're billed only for what ran.
▸ runtime environments
Pre-built Docker images on NVIDIA-optimized instances. No setup, no driver installs — containers start and run.
Full CUDA toolkit with nvcc, CMake, GDB, and build essentials. For writing, compiling, and profiling custom CUDA kernels on real hardware.
CUDA-accelerated libraries ready to go — PyTorch, RAPIDS, and Jupyter from the NVIDIA NGC stack. Verify your GPU code paths actually hit the GPU.
▸ pricing
Buy credits upfront, spend them as your agents run. No subscriptions, no minimums. Credits never expire.
starter
$10
10 credits
builder
$50
team
$100
▸ faq
No. GPU instances run entirely in our infrastructure. You never provide cloud credentials, manage IAM roles, or configure networking. We handle all of that — you just use the MCP tools.
Run claude mcp add @gpu-runners/mcp in your terminal. After authenticating with your GPUs R Us account, Claude Code discovers all GPU tools automatically the next time you start a session.
We currently support the g4dn family on AWS: g4dn.xlarge (1× T4, 16 GB VRAM), g4dn.2xlarge (1× T4, 32 GB), and g4dn.12xlarge (4× T4, 192 GB). More instance types — including A10G and H100 — are on the roadmap.
Transparent spot interruption handling is coming soon. When it ships, your workspace will be automatically checkpointed to a git branch and restored on a new instance — Claude sees a brief delay but never loses context. Today, sessions run on on-demand instances.
Yes. Connect your GitHub account in settings and Claude can use the create_pr MCP tool to open pull requests with results, trained models, or any artifacts from the session.
Credits are deducted from your balance as GPU time accrues, billed per second. Your dashboard shows your real-time balance and any charges accruing on active sessions. When a session terminates, the final charge is settled. You can always see your current spend in the top bar.
The MCP server is purpose-built for Claude Code, but the underlying REST API is open. If you want to integrate GPU provisioning into your own agent or workflow, get in touch.
▸ get started
One command sets everything up. Then just describe your task.
# Install and configure in one step $ curl -fsSL https://gpusr.us/install.sh | bash # Then just describe your task to Claude $ claude > Write a fused softmax kernel and benchmark it against torch on a T4
▸ yours for as long as the job runs