Bitrise Remote Dev Environments

@lisadziuba Congrats on going live! I’m wondering how easy is to to launch VMs/cloud Mac? Do I need to register account or can I can try it without registration?

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

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

Interesting project! What do you use to virtualize sessions on Mac? Wondering from the standpoint of executing browser-based tasks — wondering will it fire anti-bot protection on websites due to virtualization.

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?

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?

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.

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?

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?

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 😬)

I would like to know which testing problems teams usually struggle with most.

What a day! Big congrats on the launch 🚀

Congrats team for reaching this great milestone!

Hey Product Hunt!Absolutely thrilled to be releasing RDE with you all here! Developers have Macbooks, Agents now have RDE! If you are building a mobile app, after writing code you would launch the app in a simulator, test and iterate. Bitrise Remote Dev Environments gives Agents the same capability, and they perform better because of it. Not only does agents become more capable, RDE enables fully autonomous agents too. An orchestrator can pick up tasks from Slack or JIRA, spin up an RDE with an agent to do a task, create a PR and then shutdown or archive itself. Here is a demo of using RDE CLI to update an iOS App for Xcode 27

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! 🚀