A quick commerce platform’s journey from self-hosted CI chaos to automated mobile delivery
Managing CI/CD for thousands of white-label mobile apps became an infrastructure challenge rather than an engineering workflow. After moving to Codemagic, our team stopped spending time maintaining build systems and started focusing entirely on shipping products. What used to take hours of manual setup is now fully automated through a single pipeline. - Mohammad Azeem, Software Developer at Hyperzod
Hyperzod is a Forbes India DGEMS select 200 company that builds white-label mobile apps and a complete delivery ecosystem comprising customer ordering apps, merchant management apps, and driver delivery apps, and a robust admin panel for 5,000+ quick commerce businesses across 40+ countries. Every client receives a fully branded experience with custom icons, colors, app names, URL schemes, deep link domains, and platform-specific credentials. Each app is independently built, signed, and published. They currently run 1,200+ builds per month across Android and iOS.
For Mohammad Azeem, Mobile Lead at Hyperzod, an AI-first quick commerce software company, the breaking point came when onboarding a single new client required hours of manual Jenkins configuration. With hundreds of active clients and deployments across 40+ countries, that approach just stopped scaling. All applications are built from a shared React Native codebase with dynamic build-time branding. The same pipeline provisions completely different production applications using environment-driven configuration, client-specific assets, and isolated signing credentials.
Why Hyperzod switched from Jenkins to Codemagic
Jenkins is a powerful automation platform, but operating mobile CI/CD at scale introduced infrastructure challenges that required significant engineering effort. Building iOS and Android apps on Jenkins meant maintaining macOS build agents across Xcode upgrades, handling Apple code signing in shared environments, managing toolchain compatibility, and debugging failures caused by shared agent state. These weren’t flaws in Jenkins itself, but they were mobile infrastructure problems that demanded constant operational attention.
Every toolchain update, whether it was Xcode, Gradle, Node.js, CocoaPods, or Android SDK changes, required manual intervention on the build agents. Without a dedicated DevOps team managing mobile infrastructure, engineering time was constantly diverted away from product development.
White-label complexity scaled linearly
Hyperzod’s business model depends on white-label customization at scale. Every client deployment includes its own:
- app name
- bundle identifier
- app icons
- splash screens
- signing credentials
- feature flags
- platform-specific configurations
Initially, every new client required updating shell scripts and manually editing configuration files. A small mistake could silently affect unrelated builds, and the operational complexity increased with every additional client.
Shared agents caused non-deterministic failures
Jenkins agents accumulated state between builds. Stale derived data, leftover keychains, conflicting provisioning profiles, and cached dependencies created failures that were difficult to reproduce consistently. Hyperzod was initially spending roughly 10–15% of engineering time maintaining CI infrastructure instead of shipping features.
How Codemagic Solved the Problem
The team evaluated several CI/CD options with a clear set of requirements:
- Zero infrastructure management
- Dynamic build configuration per client
- Automated iOS code signing
- React Native support
- Store publishing for both platforms
- Webhook integration for backend automation
- Providing API’s for trigger builds
- Detailed logs
Codemagic met the team’s core operational requirements. The migration just took weeks.
A single pipeline now handles every client deployment. Environment variables such as app name, bundle ID, icon URLs, colors and many more are changed at build time using codemagic.yaml file. The pipeline automatically downloads client assets, applies branding, configures platform settings, and generates production-ready applications without modifying source code.
iOS automation with Fastlane
While Codemagic provides its own CLI tools for managing code signing, build versioning, and app distribution, teams already using Fastlane can bring their existing setup directly into Codemagic. This makes migration straightforward, allowing you to preserve established automation workflows while taking advantage of Codemagic’s CI/CD platform.
For iOS, Fastlane runs directly inside the Codemagic pipeline to manage:
- version increments
- build numbering
- signing configuration
- deployment automation
Codemagic initializes fresh keychains for every build, fetches certificates and provisioning profiles directly from Apple Developer Portal, and applies signing automatically. Every build starts from a clean environment, eliminating stale certificates and shared keychain conflicts.
Publishing and backend notifications
Every successful pipeline execution produces:
- APK + AAB artifacts for Android
- Signed IPA artifacts for iOS
Artifacts are automatically uploaded to Hyperzod’s backend through webhooks along with:
- Build status
- Artifact URLs
- Publishing metadata
- Deployment information
Codemagic’s APIs provide end-to-end visibility across the entire release pipeline.
Results
Infrastructure overhead has been drastically reduced. Codemagic’s Apple silicon infrastructure now handles all mobile builds. The team no longer manages:
- macOS updates
- Xcode installations
- Shared build agents
- Disk cleanup
- Signing conflicts
- Toolchain maintenance
The operational burden around CI/CD dropped dramatically.
Provisioning a new white-label client became a fully automated workflow. What previously required manual pipeline configuration can now be completed through a single trigger with environment variables and client assets. Average onboarding time for new deployments dropped from several hours to under 15 minutes.
Code signing became deterministic and reproducible. Fresh ephemeral build environments removed conflicts caused by stale provisioning profiles and shared keychains.
Every build now runs in an isolated, clean VM environment. Non-deterministic failures caused by shared state were largely eliminated.
The 10–15% of engineering time previously spent maintaining Jenkins infrastructure was redirected back into product development and platform improvements.
Conclusion
By migrating from Jenkins to Codemagic, Hyperzod transformed mobile delivery from an infrastructure-heavy process into a scalable, automated workflow. What once required manual configuration, build maintenance, and ongoing operational effort now runs through a single parameterized pipeline capable of producing fully branded Android and iOS applications at scale. With more than 1000+ client applications in production and over 1,200 builds each month, the team can focus on delivering new features and expanding its platform rather than managing CI/CD infrastructure. As Hyperzod continues to grow globally, Codemagic provides the reliability, automation, and flexibility needed to support that scale.
