Bitrise Remote Dev Environments - Cloud Macs your coding agents can actually build on

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.

Add a comment

Replies

Best

Another from me:

How does your Remote Dev Env solution differentiate from others like GitHub Codespaces, Daytona, or E2B for the "give my coding agent a real sandboxed machine" use case?

 Github Codespaces and E2B do not have macOS support, while Daytona has, their primary target is agent ephemeral sandboxes. On Bitrise you can do all: code, run agents, can use as ephemeral or persistent.

More flexible. Also check prices ☺️

   lol, I did not know that other players in the space is so expensive :)

Last one that's come to mind...

How do you approach egress? e.g. During RDE sessions can egress be restricted, or will an AI agent have the same network access like a normal CI job?

 this is a very interesting question :) Let me ask our awesome tech team))

 the honest answer is that today a session gets the same network access as a CI job on the same infrastructure. Egress controls are not something we expose yet. Tell me what you'd need, allowlists, a proxy, per-workspace policy, and I'll take it to the team. This comes up mostly from enterprise teams and it's on our radar.

Congrats on the launch! How does pricing actually work for your product, per seat, per machine, or per minute? And if an agent leaves a session running overnight, what stops the bill running with it?

 Thanks for your support 💜 We tried to make pricing as simple as possible:

We charge per minute of runtime, not per seat or per machine. Each plan has a small base fee and includes up to 1,440 minutes a month per OS, with macOS and Linux getting their own separate allocation. Beyond that it's per minute: on Basic that's $0.0288/min for macOS and $0.0044/min for Linux, Pro is double that for bigger machines.


We also have caps:


 On the overnight question, there's a hard ceiling. Each OS type has a monthly cap, and once your bill for that type reaches it, that OS is free for the rest of the month. So a forgotten session can't run the bill up indefinitely :)

 on the self-serve packages each package has a monthly maximum cap for macOS and Linux. If you reach that, metering stops and you have a flat price for the month.

Important: this means total minutes, not individual VMs. So you can stop/start/recreate as many VMs per month as you want, the bill remains the same

Congrats team. If I need an older Xcode to reproduce a bug, can I get one? And how long do you keep old versions around?

 Thanks for checking Bitrise RDE, Artyom 💜

 

> If I need an older Xcode to reproduce a bug, can I get one?

Yes, that's one of the main reasons people use it. You pick the stack when you create a session, so you can start one on an older macOS and Xcode without touching your laptop. Stacks are removed on a published schedule with at least four weeks' notice.

🙏 Worth knowing: a session keeps a permanent dependency on the stack it was created from and can't be moved to another one, and when a stack is removed the sessions created from it are erased. So don't park long-lived work on a stack that's already scheduled for removal.

If you want to cteck it, policy is here:

 this is one of the most requested features and use cases: you can by a click or prompt go back to older Xcode versions and simulators and test. Comes very handy compared to trying to reinstall your laptop with an older version right? 😅

I have one follow up question: what if I archive my VM, am I paying for it?

 Good question. Let me double-check it. Can't find anything on this on our pricing page

 so, billing is per minute of runtime, and an archived session isn't running, so the meter stops. Storage isn't charged either at the moment.

I hope it helps 💜

Amazing to hear that the age old problem of "it works locally" will finally meet its end!!

I had not even thought about how when agents hit this wall it likely results on a pit of burnt tokens trying to fix something that is not trivial to fix. Centralizing the environment this way is huge in this regard

 hey Lex, thanks for checking RDE 💜

Kudos on launching your product. A bit basic, but why have decided to have a mobile focus for your RDE?

Congrats with the launch! Great product!

I know RDE solves a real problem as I watched it grow internally, out of the friction our own teams kept running into. The gap between where you write code and where it actually gets built and tested is where most of the wasted time is, and it's the kind of thing you stop noticing because it was always there.

Seeing it go from an internal tool to something anyone can spin up in a few commands made me genuinely proud to watch. It's also amazing to see Bitrise on Product Hunt again!

Congrats on the launch, team! 🚀

 hey Gabor :) Thanks for your support! I think we were on Product Hunt is 2018? lol, long time ago

 I think it was 2015? :D Anyway, good to be back!

 no way, we should be in the 10-year club then :) By the way, I got a Silver Kitty from Product Hunt in 2017-2018

 indeed we started building this for ourselves. And then Customers started asking for the same

Hey Product Hunt 👋, I'm Barnabas, CEO at Bitrise.

We first launched here back in 2014, when the problem was simply getting mobile builds to run reliably in the cloud. 11 years later we're back with Remote Dev Environments 🚀, and the problem has changed shape: it's not just developers who need a machine now, it's their agents too.

Happy to be back, and happy to answer anything in the comments today.

 So cool to be on Product Hunt again 💜 I didn't realize that you launched earlier than my startup - my first launch was in 2017.

I think Birise should deserve 10 year club kitty award :)

 dang. That was over a decade ago 😳

How does this compare to the previous? 😆