FlyDex is the only one of the three with a documented browser-first QR flow and a one-line desktop helper path live on the public site.
Comparison guide
FlyDex vs Remote Codex vs Remodex
These products solve adjacent problems, but they optimize for different operator trade-offs. FlyDex focuses on browser-first remote operations for local Codex on macOS and Windows. Remote Codex currently markets a phone-to-desktop relay with a waitlist. Remodex is an open-source bridge plus a native iPhone app aimed at self-hosters and operators willing to sign their own iOS build.
Remodex publishes bridge source, iOS source, and self-hosting notes, so operators can run their own relay path end to end.
Remote Codex exposes a polished landing page and demo video, but it does not currently publish a deeper technical docs surface or install runbook on the public site.
Overview
Executive summary
If the priority is the lowest-friction public setup for remote approvals and thread control, FlyDex is the strongest fit. If the priority is a native iPhone client and a self-host-friendly source tree, Remodex is the stronger reference. If the priority is early access to a hosted phone relay experience and a quick watchlist, Remote Codex is the closest analogue, but the public trust and operations story is still thin compared with the other two surfaces.
| Product | Delivery model | Remote client | Setup path | Pricing | Best fit |
|---|---|---|---|---|---|
| FlyDex | Public web control plane for local Codex on macOS and Windows | Browser-first mobile control with QR pairing | One-line npx desktop helper + QR scan on phone | 72-hour trial, then $10/month | Operational remote control, fast approval handling, and machine continuity without exposing local Codex publicly. |
| Remote Codex | Hosted remote layer for a desktop Codex session | Phone-oriented web surface shown on landing page | Currently a waitlist form on the public landing page | Waitlist promo advertises the first month at $3 | Simple marketing surface and demo video, but the public site does not publish detailed install, endpoint, or trust-model documentation yet. |
| Remodex | Open-source local-first bridge + iOS app | Native iPhone app | Install the bridge from npm, then build and sign the iOS app from source before pairing | Open source; self-hosting and device-signing costs depend on the operator | Strong fit for self-hosters who want inspectable source, an iOS-native experience, and control of their own relay path. |
Feature matrix
Where FlyDex pulls ahead
Windows + macOS coverage
FlyDex publicly supports both desktop platforms. Remodex is Mac-first and iPhone-first. Remote Codex does not publish platform support details on the landing page.
Operational approvals
FlyDex explicitly documents approval handling, thread reads, and remote prompt continuation. Remote Codex and Remodex both imply shared continuity, but FlyDex is the clearest about the intervention loop.
Trust model transparency
FlyDex publishes architecture, security, privacy, and routing notes publicly. Remodex publishes source. Remote Codex currently publishes only the landing-page summary.
Performance comparison
Latency and operator friction
FlyDex
Best when the constraint is approval latency and operator responsiveness, because the product is optimized around machine-aware browser control rather than full desktop remoting.
Remote Codex
Looks lightweight from the landing page, but the public site does not yet expose enough implementation detail to evaluate relay durability or recovery behavior.
Remodex
Potentially the most flexible for power users, but setup friction is higher because operators must manage npm bridge install, iOS build signing, and any self-hosted relay choices.
Security architecture
Where the trust boundaries differ
FlyDex keeps the browser off the local Codex runtime, pushes traffic through a localhost-only connector, and documents short-lived QR claims plus action-level approval boundaries. Remodex exposes more operator control because the bridge and iOS app are open source, which is ideal for self-hosters but shifts more operational burden to the user. Remote Codex publicly states a secure encrypted relay and shared thread continuity, but the landing page does not yet publish the artifact-level detail needed for a deeper design review.
Pricing
Commercial model
- FlyDex: one-time 72-hour trial, then $10 per month.
- Remote Codex: waitlist banner advertises the first month for $3.
- Remodex: open-source project; no hosted subscription price is presented in the README.
Best use cases
Which product fits which operator
- Choose FlyDex if you want the cleanest public onboarding, Windows support, and operational docs you can send to a team.
- Choose Remote Codex if you mainly want to watch the hosted product category and compare emerging relay UX once the waitlist opens.
- Choose Remodex if you prefer inspectable source, iPhone-native UX, and you are comfortable owning the self-hosting and device-signing path.