Founder stories
Local-first iOS remote control for Codex and other Mac-based coding agents, with an open-source bridge, encrypted pairing, git actions, voice input, and App Store subscriptions.
How Emanuele acquired customers
Tools used to build Remodex
Emanuele Di Pietro turned a midnight challenge to control Codex from iPhone into Remodex, a local-first open-source remote that reached about $10K revenue in its first month.
Emanuele Di Pietro did not set out to build a polished enterprise devtool. The MRR Story case describes a 22-year-old computer-science student in Naples who was already living inside local AI coding agents. The frustration was simple: when Codex was running on his Mac, leaving the desk meant losing the ability to steer the session, answer prompts, push commits, or recover from a stuck run.
His first version was more ambitious than the final wedge. He had been exploring Phodex, a cloud-style remote setup with VPS and Docker pieces. Then rumors surfaced that OpenAI might ship an official mobile/remote direction. Instead of competing with a heavy cloud product, Emanuele narrowed the promise: ship a local-first iPhone remote for Codex before the official app arrived. Around midnight on March 8, 2026, he posted the challenge publicly, used Codex itself to help build, and had the first working version by about 4 AM.
Remodex's durable hook is trust. The live product page and App Store listing both frame it as a local-first Mac bridge plus iOS app: Codex, git, and workspace actions stay on the user's Mac while the phone sends instructions through an end-to-end encrypted session. The GitHub repo reinforces that boundary with open-source code, self-hosting notes, and a bridge architecture rather than a black-box cloud IDE.
Distribution came from proof, not paid ads. Emanuele launched in public, put the app on the App Store, and made the bridge open source so technical users could inspect the trust model. MacStories later reviewed Remodex as the best Codex remote client for iOS until an official OpenAI app exists, highlighting the same local Codex setup, App Store availability, and subscription pricing. MRR Story reports roughly $10,000 revenue within about 30 days. That is strong proof of paid demand, while still being a first-month sales figure rather than proof of steady recurring revenue.
When a platform shift creates urgency, a narrow wedge can beat a broader but slower product.
For developer tools that touch source code, local-first architecture and open source can be part of the go-to-market story, not just implementation details.
A public shipping challenge gives early users a narrative to share, especially when the product is built with the tool it extends.
Total first-month revenue is proof of paid demand, but it is not the same as recurring MRR without an explicit recurring-revenue source.
You have the story. Make it actionable: what worked, what to copy, what to avoid, and which channel to test first.
First Customer
Other
Action checklist
Keep the story context as you continue.
Inspired by Emanuele's journey? Generate a business idea in the Developer Tools space using AI and real founder data.
The journey, decisions, and context behind this milestone
See the complete breakdown: launch strategy, validation methods, startup costs, expert analysis, replication playbook, and more actionable insights.
Upgrade to PremiumInstant access to all founder journeys
Founders with similar journeys or strategies
We started Pocketed during the pandemic to help startups find grants and funding they didn't know existed. The Idea During COVID, there was sudd...
I built Fantasy Congress as a side project - a fantasy sports game but for politics. It went viral and taught me everything about building in public....
I validated Buffer with a landing page before writing any code. Within 4 days of tweeting about it, I had my first paying customer. The Validation...
Get more founder journeys like this delivered to your inbox every week.