LM-Kit OneThe Private AI Application Server
Promoted
Bitrise is the leading mobile DevOps platform, empowering over 8,500 brands worldwide including Generali, Shopify, TripAdvisor and BuzzFeed. Bitrise provides a full-stack, vertically integrated mobile DevOps solution that unites the tools, processes and testing frameworks engineering teams need to build best-in-class mobile experiences.
This is the 3rd launch from Bitrise. View more
Bitrise Remote Dev Environments
Launching today
Bitrise RDE gives you cloud Macs & Linux machines that start in seconds, the same machines, stacks and caches as your CI.
Give every agent its machine and run them in parallel via MCP, or attach VS Code, Cursor or Claude Code. Archive when you stop, restore later.
Free Options
Launch Team / Built With
Bitrise
Hey Product Hunt, I’m Arpad, VP of Engineering at Bitrise (mobile DevOps startup).
Agents need somewhere real to run.
You can hand an agent a task, but it has to execute somewhere.
❌ On your laptop it fights you for the CPU and the simulator, running multiple in parallel and you won’t be able to do a video call without CPU clipping and fans screaming.
❌ In a throwaway container it has no real device tooling, no warm dependencies and no memory of the last run, so it spends its first tokens rebuilding an environment it’s about to lose again.
✅ Bitrise Remote Dev Environments are that somewhere:
Bitrise RDE are on-demand cloud VMs (real macOS on Apple Silicon, or Linux) that an agent drives headless through our open-source MCP server.
Start a batch on different branches, → let them work in parallel, → collect the PRs. Or attach VS Code, Cursor or Claude Code over SSH and work in it yourself, like a laptop, but many.
The reason it actually works: these are the same machines that run production builds for mobile teams at scale. Same Apple Silicon hardware, same stacks, cloned from the same golden image the CI build fleet uses.
🤷♀️ Honestly this came out of a thing that annoys all of us. CI fails on something your laptop never hits: a different Xcode, a stale pod cache, a simulator runtime you don't have locally. You pull the branch, it passes, and your afternoon is gone comparing two machines instead of fixing the bug.
Agents made it worse: same problem, none of the judgement. It burns tokens down rabbit holes, sometimes fixes the environment only to hit the same wall next run in a fresh VM, then confidently opens a PR that can’t build – or fixes the wrong thing.
So we gave the human and the AI agent the same machine. When the environment you write code in is the one that tests it, a whole category of works-on-my-machine stops existing. Ask me anything about how it works, what it costs, or where it still falls short.
Hey, member of the Bitrise docs team here 📝
First of all, congrats! 🎉 And a quick question about templates for iOS.
How much of an existing Bitrise setup carries over (thinking stack, connected repo, workspace secrets) versus needing to be defined again for RDE? And where does code signing land: are certs and profiles part of the template? Or something you set up per session?
(Okay, this is a COUPLE of quick questions 😬)
Bitrise
@ilana_zholobovsky1 hello Ilana 👋 Thank you so much for your support :)
Bitrise
@ilana_zholobovsky1 Stacks carry over directly, an RDE session runs the same stack image as your CI and Build Hub builds, and stays pinned to it.
Bitrise
Hi Product Hunt!
RDE started as an internal tool to solve our own daily headaches at Bitrise. I wrote the first commit in January and designed the core: a template describes the machine, the scripts, and the secrets, and every session is a self-contained snapshot of it. That is the boring foundation behind "pre-configured and ready to go out of the box", and it is why we quickly realized this could work for other teams too.
💜 The decision I am proudest of came in the first month. We put a terminal with Claude Code into every session and shipped an MCP server, so an agent could open, drive, and clean up an RDE without a human in the loop. At the time it looked like a nice extra. It quickly became the main way sessions got opened at Bitrise!
Bitrise
@balazsrostas I loved seeing how much passion the engineering team put into Bitrise Remote Dev Environments 💛
What's exciting is how RDE works: instead of wrestling with local setup, you direct an agent to spin up a pre-configured Linux or macOS VM, run end-to-end tests, and validate ideas in minutes.
So with device sessions, the agent can boot an iOS simulator or Android emulator, install the build, tap through it, and screenshot to verify. "Run the app and tell me if the new screen looks right" is now a real instruction. And this is insanely cool
Bitrise
Hi Product Hunt!
I worked on Bitrise CI before joining the RDE team, and what surprised me most was how much carried over. Running macOS and Linux machines at scale, keeping stacks and images current, making a VM boot fast and come up identical every time. That's years of work we didn't have to redo. RDE started from there instead of from zero.
The same holds a level up. Bitrise is a platform, not just CI (Build Cache, Release Management, the integrations underneath all of it) and RDE is one more thing that plugs into it.
Our GitHub integration is the example I know best: if your workspace has repos connected to Bitrise, your engineers get git access inside an RDE without anyone pasting a personal token into a VM. A team that's already on CI onboards in minutes.
There's still a long list of things the platform already does that we haven't wired up yet, and that list is the fun part. It goes the other way as well: a lot of what we're building for RDE is going to end up back in the rest of the platform.
Bitrise
@gabor_szakacs This is so cool! What would be the next plans for the roadmap? :)
Bitrise
@lisadziuba Thanks! The near-term theme is reusing what a workspace has already set up for CI: third-party integrations, secrets, connected repos. If it's configured for your builds, it should be available in RDE without a second setup step.
Beyond that, two things I'm personally excited about. One is Build Cache: the same cache that speeds up CI builds could serve builds running on an RDE, so a fresh environment doesn't start cold.
The other is Release Management: an RDE can already run simulators and emulators, so it's a natural place to install an app bundle from a release and let a human or an agent test it, with no local device setup.
Plenty more on the list, but those are the ones I'd bet on first 🙂
Bitrise
@gabor_szakacs Thanks for the details, I think all of that will 10x the product. On the caching side it always amuzed me how it can speed up time
Bitrise
👨🔧 More technical details on Bitrise Remote Dev Environments if you’d like to learn more:
Real macOS on M2 Pro / M4 / M4 Pro (M6 and M5 Pro coming soon) + Linux from 2 to 48 vCPU. US and EU regions.
$20/month gets you 1,440 minutes per OS.
Overage is $0.0288/min on macOS, $0.0044 on Linux, and it stops at a monthly cap – hit the cap and you keep running free for the rest of the month.
14-day trial, no auto-charge.
Agents running inside the VM use your own account and API keys.
🔗 Docs: https://docs.bitrise.io/en/bitrise-rde/getting-started/remote-dev-environments-overview
❌ What it isn’t: no Windows. And it’s mobile-first by heritage. If you’re a pure web team you’ll find it works fine, but you’ll notice we built the Apple path first.
Bitrise
@arpadk Any plans for focusing on web direction?
Bitrise
@arpadk @lisadziuba Absolutely, and you don't have to wait for it, you can already use RDE for non-mobile projects today. Docker is preinstalled, so a typical web stack works out of the box.
The way we think about it: RDE is really about reliable, scalable, isolated environments, and the interfaces around it so you can quickly create as many of these as you need, manually or via an AI agent. Mobile builds and tests just happen to be the most demanding case, so if it's powerful enough for those, it's more than enough for a web project. But nothing in the interface is mobile-specific - you can work on any project in RDE, with any agent.
We're continuously gathering feedback from RDE users and shaping the product around it, so if you (or anyone reading this) try it with a web project, tell us what's missing, that's exactly what drives what we build next.
Bitrise
@arpadk @viktorbenei Thanks for the details 🗺️
Slideshot
Looks awesome! Congrats with the launch, team! 🙌
How do I start using the RDE?
Bitrise
@geek_1001 Thanks for the support!
You can try out RDE with a 14 day trial here. Our docs can be useful when you're getting started.
Let us know if you have any other questions!
Bitrise
@geek_1001 On the technical side, you can create and connect to sessions through several clients. CLI, UI, MCP server, or VS Code plugin. I think the Quickstart will be the best place to explain the tech setup: https://docs.bitrise.io/en/bitrise-rde/getting-started/rde-faq
Hey, congrats on the launch. I've got Claude Code running locally today. What changes if I run it inside one of these instead, and whose API key pays for it?
Bitrise
@atanas_bitrise Thanks for checking RDE, Atanas 🙏
Bitrise
@atanas_bitrise good question,
So RDE brings the environment where your agents run; you bring the agent and API key or subscription.
We have tight integration with Claude Code built into the UI. You can run any agent inside the VM or let your agent use the VM via MCP and do coding/testing remotely with exec or SSH.