Code, build, and run agents on Bitrise Remote Dev Environments
On-demand cloud VMs on the same machines, stacks, and caches as Bitrise CI or Build Hub. Spin one up in seconds, archive it when you're done, pick up where you left off.
The dev environment moved off the laptop. Bitrise moved with it.
"Works on my machine" became "works on my agent's machine." AI coding agents need somewhere real to run, with the exact tools your build needs — and your developers do too.
Remote Dev Environments (RDEs) are that somewhere. The same machines your CI builds on, available the moment anyone needs them.
When the environment your code is written in matches the environment your code is tested in, a whole class of bug stops happening.
Start where you are.
Scale when you're ready.
Pick the layer that fits today, move up when you're ready.
Layer 1: Remote dev environments for your developers
Cloud VMs your engineers connect to from VS Code or Cursor, running the same stacks as your CI. Archive sessions when you're done, and the state survives the weekend without a meter running. Restore on Monday and pick up where you left off.
Layer 2: AI-assisted coding inside the VM
Claude Code or Codex pre-installed in the same environment your CI builds in, running on your own API keys.
Layer 3: Fully autonomous agents
Agents pick up tickets, spin up a VM, write the code, run the tests, open the PR, and shut down when they're done. Orchestrate parallel work through the open-source MCP server.
Everything you need to run real work
in a real environment
Session lifecycle
Create from templates with warmup scripts. Start, stop, archive, restore. Persistent disk across restarts. Bulk operations for fleet-scale work.
The same toolchain as your CI
Xcode, Git, Docker, npm, fastlane. Already installed, already cached. Reproduce a CI failure inside the same VM that produced it.
AI agent orchestration
Route tickets to agents through the open-source MCP server. Spin up parallel sessions, run them headless, archive results. Built for fleet-scale, not laptop-scale.
From template to PR in four steps
Define a template once. Spin up environments in seconds.
Define a template
Pick a machine image, add a warmup script, set credentials. Do it once, share with the team.
Spin up a session
Via the dashboard, the API, or an MCP call. Warm in seconds.
Code in it
Attach VS Code, let an agent run, or both. Full shell, file transfer, GUI on macOS.
Archive or destroy
Save block-level state and come back later, or shut it down clean.
The same fleet you'd trust to ship
Apple Silicon, multi-region, production-hardened, available in US and Europe.
Same machines as your CI.
Apple Silicon
M2 Pro, M4 and M4 Pro machines in US and EU data centres. Real macOS VMs with Xcode, Simulator, and the full Apple toolchain. The cache your CI builds with is the cache your dev environment uses.
Dedicated and shared clusters
From 2 to 48 vCPU machine sizes. Full Docker support, build toolchains ready to go.
Same as Bitrise CI
Production-hardened orchestration. Multi-region. Shared caches across CI, Build Hub and RDE. The same fleet you already trust if you already build on Bitrise.
Plays well with the tools
you already use
The vendor approval is already done
If your security team has signed off on Bitrise, the same sign-off covers RDE. Same infrastructure, same handling.
Isolation per session
Credentials scoped to the session. Per-workspace quotas stop any one team using the whole fleet.
Apple Silicon
Customers with dedicated hardware on Bitrise can run RDE on the same private pool. No extra security review.
Cloud dev environments that mobile teams love
RDE is in beta with mobile teams at some of the largest consumer apps in the world. If your developers want their environment ready when they sit down, or if you're running AI agents and tired of laptop-scale infrastructure, get in touch.
Frequently Asked Questions
What is Bitrise Remote Dev Environments (RDE)?
RDE gives developers persistent, on-demand cloud VMs that use the same machines, stacks, and caches as Bitrise CI or Build Hub. Engineers can attach VS Code or Cursor and code in the cloud, or run autonomous AI agents in the same environment.
How is RDE different from a standard cloud dev environment?
The environment your code is written in is the same environment your code is built and tested in. Same hardware, same toolchain, same caches. CI failures get reproduced in seconds, and AI agents stop burning tokens on environment setup errors.
Which tools does RDE work with?
RDE works with the IDEs and AI tools your team already uses, including Claude Code, Codex, Cursor, VS Code, JetBrains IDEs, Xcode, Gemini CLI, Windsurf, and any custom MCP client. The open-source MCP server is on GitHub.
What about security?
The security posture is the same as Bitrise CI or Build Hub you already use. Build VMs are never reused across customers, each VM is isolated and they can't access each other. Credentials are scoped to the session, and customers with dedicated hardware can run RDE in a private pool.
How does pricing work?
RDE is in beta. Talk to us about your team's setup and we'll work out what fits.