AI agents can write your app — shipping it is still the hard part: build toolchains, tests, signing, releases, publishing. AppRelay is one native Mac & Windows console that does all of it. Point it at a folder and it auto-detects 25 toolchains. Build ≠ Distribute — one build fans out to 27 destinations (App Store, Play, Vercel & more). Runs 100% on your machine: no account, no cloud, no subscription. iOS & Android companion included.
No reviews yetBe the first to leave a review for AppRelay for Mac & Windows
Maker
📌
Hey Product Hunt 👋 I'm Aaron, the maker of AppRelay.
I build a lot of apps — iOS, Android, macOS, Windows and web — and for years every one of them shipped differently. One needed an Xcode scheme and a notarize step. Another was ./gradlew plus a half-remembered Play Console dance. The web ones were deploy scripts I'd rewritten five times. Every release meant reloading a different mental model, and I dreaded the project I hadn't touched in three months.
That was already a problem worth solving. But something bigger is happening now that makes it urgent.
We're at the start of a real shift in how software gets built. AI coding agents are collapsing the cost of *writing* software — someone can describe an app and watch working code appear, without deep engineering experience. But shipping software was never really about the code. The moment it's written, the actual gauntlet begins: build toolchains, tests, signing, versioning, releases, and publishing to the App Store, Google Play, the web and everywhere else. That's the part no agent hands you — and it's exactly where new builders stall.
AppRelay closes that gap. It's one native console — on Mac and Windows — where every project lives side by side. Point it at a folder and it detects the stack (25 toolchains, from Xcode and Gradle to Flutter, Tauri, Go and Rust), reads the real version, and gives every project the same command center: overview, source control, run & debug, a test console, and release.
The idea I'm proudest of is Build ≠ Distribute. A build says how a project compiles; a distribution says where it goes — so one build fans out to the App Store, Google Play, Firebase, Vercel and more, 27 destinations in all. Adding one is an entry, never a code change.
A few things that matter to me:
• Runs 100% on your machine. No account, no cloud — your code and secrets stay put.
• Orchestrates the real tools (xcodebuild, gradle, eas, fastlane, vercel, docker) — it doesn't replace them, so you learn the real pipeline as you go.
• Drive it however you work — the GUI, a Claude Code sidebar, an MCP server for agents, a headless CLI, or your phone (iOS & Android) as a remote when you're away from your desk.
• Portable projects — export any project as a single encrypted .relay file and open it on another machine.
Start free (one project, three builds, one real release); unlock everything for $99 once — no subscription, a year of updates included. I can also issue/gift license keys for anyone interested in trying out the Studio version.
If an agent can write your app, AppRelay is how you get it into people's hands. I'd love your feedback — especially on Build ≠ Distribute and which toolchains or destinations you'd want next. I'll be here all day. 🚀
Report
finally something that gets rid of the signing and release nightmare. pointed it at a vite project and it basically figured everything out on its own, no account setup, just worked. kind of wild that this runs entirely local.
Report
Maker
@ferdi788603 Thanks Ferdi — signing and release was exactly the itch. It's the part I kept re-solving badly on every new project. Vite comes in through the Node/web adapter, so it reads your package.json and prefills the lane instead of asking you to describe your own project back to it. And local is deliberate: no account, no login, nothing leaves your machine. Signing secrets live in the Keychain, not in a config file.
Report
Pointed it at a small Flutter project and it picked up the toolchain without me touching a config file, which was a nice surprise. The fan-out to multiple stores from one build feels like the part I have always wanted automated.
Report
Maker
@irmakmemik Thank you! That fan-out is basically the reason AppRelay exists — build and distribute being one welded-together step never made sense to me. A lane defines how the project builds, distributions define where that build ships. So one Flutter build can go to Play, TestFlight and Firebase together, and adding a fourth destination is a config entry rather than a new script.
Report
The auto-detection of 25 toolchains from just a folder is genuinely clever, saves a ton of setup headache. Love that it runs fully local with no account dance, feels like software built by people who actually ship.
Report
Maker
@sonkupu68668 Appreciate that! The detection work came out of being annoyed at myself — I had 40-odd repos spread across Xcode, Gradle, Expo and web, and I was re-learning each one's incantation every few months. The no-account rule was there from day one: it runs on your machine, so it shouldn't need mine.
finally something that gets rid of the signing and release nightmare. pointed it at a vite project and it basically figured everything out on its own, no account setup, just worked. kind of wild that this runs entirely local.
@ferdi788603 Thanks Ferdi — signing and release was exactly the itch. It's the part I kept re-solving badly on every new project. Vite comes in through the Node/web adapter, so it reads your package.json and prefills the lane instead of asking you to describe your own project back to it. And local is deliberate: no account, no login, nothing leaves your machine. Signing secrets live in the Keychain, not in a config file.
Pointed it at a small Flutter project and it picked up the toolchain without me touching a config file, which was a nice surprise. The fan-out to multiple stores from one build feels like the part I have always wanted automated.
@irmakmemik Thank you! That fan-out is basically the reason AppRelay exists — build and distribute being one welded-together step never made sense to me. A lane defines how the project builds, distributions define where that build ships. So one Flutter build can go to Play, TestFlight and Firebase together, and adding a fourth destination is a config entry rather than a new script.
The auto-detection of 25 toolchains from just a folder is genuinely clever, saves a ton of setup headache. Love that it runs fully local with no account dance, feels like software built by people who actually ship.
@sonkupu68668 Appreciate that! The detection work came out of being annoyed at myself — I had 40-odd repos spread across Xcode, Gradle, Expo and web, and I was re-learning each one's incantation every few months. The no-account rule was there from day one: it runs on your machine, so it shouldn't need mine.