Cloud iOS builds
Compile an IPA online — no Mac, no Xcode
Upload your source or paste your app's URL, and we compile a real .ipa on Apple-silicon machines in our cloud. Bring your own Apple Developer certificate (.p12) and the IPA comes back store-ready signed; without one, you get an unsigned IPA to re-sign yourself. We never ask for your Apple ID. First build is free, with a watermark.
How it works
Step 1: Upload your source code, or paste the URL of your deployed web app.
Step 2: We compile it in the cloud on real Apple-silicon hardware — the same class of machine Xcode runs on, minus the part where you have to own one.
Step 3: Download your .ipa. If you uploaded your Apple Developer distribution certificate (.p12), it arrives signed and ready for App Store Connect. If you didn't, it arrives unsigned, and you re-sign it with your own tooling. Either way, the build is yours to keep.
What you need (and what you don't)
For the App Store: an Apple Developer account. Apple charges $99/year for it, and there is no way around that — anyone who tells you otherwise is selling something. You export your distribution certificate as a .p12, upload it with your build, and we sign the IPA with it. Your Apple ID and password stay with you; we never see them.
For an unsigned IPA: nothing. No Apple account, no certificate. You get the compiled binary and handle signing on your side — useful if you already have a signing pipeline, an enterprise setup, or a device you sideload to.
For a home-screen install with zero signing: we also generate an iOS Web Clip (.mobileconfig) that puts your web app on the home screen with your icon. Honest trade-off: a Web Clip is not a native app — no push notifications, no App Store listing. It is the fastest possible path to an icon on an iPhone, and sometimes that is all you need.
What we can compile
Flutter source: upload your project and we build the iOS target in the cloud — dependency resolution, compilation, and packaging into an .ipa, signed or unsigned per the above.
Any deployed web app: paste the URL and we wrap it in a native iOS shell. Wrapped apps ship with push notifications, native navigation, and a splash screen — the things Apple's reviewers look for under Guideline 4.2 when deciding whether an app is more than a website in a frame.
What we can't do, so you don't waste a credit finding out: Kotlin or Java Android code cannot be converted into an iOS app — not by us, not by anyone. If your app builder only exports Android code or web code, the iOS route is wrapping your deployed URL, and that's the route we build for you.
Frequently asked questions
Will my IPA actually be signed, or is this another unsigned-IPA generator?
Both, and we're upfront about which you're getting. If you upload your own Apple Developer distribution certificate (.p12), the IPA is signed with it and ready for App Store Connect. If you don't, the IPA is unsigned — a real compiled binary, but you must re-sign it before it will install through normal channels. We never ask for your Apple ID or password; signing happens with the certificate file you control.
Can I put the IPA on TestFlight?
Yes, if it's signed with your certificate. TestFlight runs through App Store Connect, which requires an Apple Developer account ($99/year, paid to Apple, not to us). Build with your .p12 uploaded, then submit the signed IPA to your App Store Connect account and distribute through TestFlight as usual. An unsigned IPA cannot go to TestFlight until it's signed.
What does it cost?
Your first build is free and carries a watermark, so you can verify the pipeline works on your app before paying anything. iOS cloud builds are included in Pro at $99/month with 30 build credits. Starter is $29/month with 10 credits. Single App is $149 one-time for one app with lifetime updates. The $99/year Apple Developer membership is separate and paid to Apple — you only need it for App Store or TestFlight distribution, not for unsigned builds or Web Clips.
How long does a build take?
Minutes, not seconds — and it varies. A URL wrap is on the fast end; a Flutter project with a heavy dependency tree takes longer because we're resolving and compiling your actual code on real hardware. We won't quote you a fixed number because it depends on your app. You'll see the build's status live and get the IPA the moment it's done.
What happens if my build fails?
The credit is automatically refunded. You don't file a ticket or argue with support — a failed build costs you nothing. Builds can fail for real reasons (broken source, missing dependencies, an expired certificate), and when they do, the build log tells you why so you can fix it and try again.