Zealot defaults its container build to Chinese package mirrors
Self-hosted beta app distribution for Android, iOS, macOS, Linux and Windows apps, with iOS/Android SDKs, fastlane and a rich component library.
At a glance
- What is it?
- A self-hosted beta distribution server for mobile and desktop apps, written in Rails with a Vite frontend and a pnpm workspace. The build is well tuned for one region, and the region is not stated anywhere in the README.
- Who is it for?
- Zealot is a serious piece of infrastructure for a team that already has signing identities and a CI system, and it covers the awkward parts of app distribution that a store upload does not. Two things decide whether it suits you.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly Ruby, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- tryzealot/zealot1,369 ★ · +16
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| tryzealot/zealot | 1.4k | 1.4k |
16 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The default image build redirects every package source to a Chinese mirror
The Dockerfile opens with a set of build arguments that are not cosmetic:
ARG REPLACE_CHINA_MIRROR="true"
ARG ORIGINAL_REPO_URL="dl-cdn.alpinelinux.org"
ARG MIRROR_REPO_URL="mirrors.ustc.edu.cn"
ARG RUBYGEMS_SOURCE="https://gems.ruby-china.com"
ARG NPM_REGISTRY="https://registry.npmmirror.com"The flag that controls all of it defaults to true, and when it is on the build rewrites the Alpine package repositories in place:
sed -i "s/$ORIGINAL_REPO_URL/$MIRROR_REPO_URL/g" /etc/apk/repositoriesthen adds the Chinese gem source and removes the default one:
gem sources --add $RUBYGEMS_SOURCE --remove https://rubygems.org/and repoints the JavaScript registry as well:
pnpm config set registry $NPM_REGISTRY;So three separate package ecosystems are fetched from third-party mirrors unless a builder passes the flag to false. Inside China this is a sensible way to make builds fast. Outside it, it means the default image is assembled from hosts chosen for a different region, which is a decision most people adopting a self-hosted tool never make consciously and cannot easily audit after the fact. The mitigation is one build argument.
Alpine means every native gem is compiled on your machine
The base image is Alpine:
FROM ruby:3.4.8-alpine AS builderand the bundle configuration compensates for what that choice costs. Because there are no precompiled native gems for musl, the install is told to compile from source and to do it in parallel:
bundle config set force_ruby_platform truebundle install --jobs $(nproc) --retry 3Deployment mode is on as well, frozen mode is set, and the development and test groups are excluded, so the image carries runtime gems only into vendor/bundle. All of that is correct, and the practical consequence is that the first build is a compile. The build packages list carries a C toolchain, image libraries and PostgreSQL headers precisely because those extensions have to be built rather than unpacked.
Two details are worth knowing. The image sets YJIT on through an environment variable, so you are relying on the interpreter in the base tag supporting it rather than adding a build flag yourself. And multi-architecture support, which the README advertises for both amd64 and arm64, is not expressed in this Dockerfile at all; a single FROM line means the architectures come from how the image is built and published, not from the file you can read.
Assets are precompiled with a literal placeholder secret
The frontend is built inside the image, and the step that does it names the secret explicitly:
SECRET_KEY_BASE=precompile_placeholder bin/rails vite:buildThat is the standard Rails arrangement for precompiling assets in a container, and it works because the key is only needed to satisfy the framework during the build. The risk is that the placeholder is a known constant. Anything the framework signs with that key, and anything that later starts with it still in place, is signed with a value published in the repository.
The image itself is not the danger, since a real deployment supplies its own value at run time. The danger is a container start command that forgets to, which is easy to do because the build succeeded and nothing in the image complains. The Dockerfile also pins the bundler app config directory and the production environment as environment variables, so the runtime environment is mostly described by the image rather than by the compose file, and a deployment that replaces those values silently inherits a different bundler configuration.
Both of these are the kind of detail a self-hosted tool should state in its installation page rather than leave inside a build file.
The developer kit is three other repositories
The README advertises a REST API, an iOS SDK, an Android SDK and a fastlane plugin as the developer toolkit. None of the three SDKs is in this repository. Each is a separate project: an iOS package, an Android package and a fastlane plugin, all under the same owner.
That arrangement is normal for client libraries, and it keeps this repository's release cycle independent of them. It also means there is no single place where the server and its three clients agree on a version. Zealot's own tags, currently 6.2.2, describe the server. Whether the fastlane plugin that calls it expects 6.2 behaviour is a question you answer by opening three more repositories, and the README does not state a compatibility range.
For an evaluator this is the first thing to check, because it determines whether you are looking at one project or four. It also tells you where the interesting integration work sits: the server is the distributable part, and the clients are thin by design.
Version comparison and device detection both run in the browser
Two runtime dependencies in the frontend package are more telling than the styling stack. compare-versions is present, so the web interface decides on its own whether a build is newer than what a tester has installed, rather than asking the server for a verdict. And ua-parser-js is present, so the interface reads the browser's user-agent string to work out what kind of device is asking.
"compare-versions": "^6.1.1",
"ua-parser-js": "^2.0.10"Together they are what lets an installation prompt be specific rather than generic. An update notice can say whether it applies to this platform and whether this build is ahead of the one on the device, and it can say so without a round trip.
The rest of the stack is Rails 8 on the server side, with Turbo and Stimulus driving the pages:
"@rails/actioncable": "^8.1.301",
"@hotwired/turbo-rails": "^8.0.23",ActionCable is the interesting one for this product. An app distribution server needs to push a new build to a tester who has the page open, and a websocket channel is how that notification arrives. The styling is Tailwind with a component library on top, built by Vite and served through the Rails asset pipeline.
The default branch is develop, so a fresh clone is not a release
The repository's default branch is develop rather than main, and the README's own links point into that branch for the change log and the licence file. Anyone who clones the project and builds it without checking out a tag is building unreleased work, which is worth stating plainly because most tooling defaults to the primary branch and will do exactly that.
The release history explains what unreleased looks like here. Version 6.2.0 shipped on 18 December 2025, then nothing for seven months, then 6.2.1 on 23 July 2026 and 6.2.2 on 25 July 2026. Two patch releases two days apart after a long gap is the pattern of a fix that needed a follow-up fix, and it means 6.2.1 and 6.2.2 differ in ways that were not in the original plan.
The repository is not archived, the last push is dated 30 September 2026, and there are 12 open issues. The licence is MIT.
Documentation is translated through Crowdin, and only the tagline is English
The README is written Chinese first. Its feature list, its links to the documentation and every descriptive line are in Chinese, while the single English sentence is the tagline in the header. For an English reader the README is a landing page that links to a documentation site rather than a description of the software.
"crowdin": "crowdin"The translation runs through Crowdin, with a crowdin configuration file at the top of the repository and a script in the frontend package that invokes the client. That is a sensible setup for a project with both an English and a Simplified Chinese documentation site, and both sets of pages are linked from the header.
The cost is the usual one. Documentation moves through a translation pipeline, so the two language versions drift apart by whatever a round trip takes, and a page describing a flag added last week will exist in one language before the other. The same applies to the README itself: features listed in Chinese are the authoritative list, and the English version of the site is the place to check whether something has changed. The tree also carries a Crowdin badge, which at least tells you the translation is real rather than machine output left unreviewed.
Editorial conclusion
Zealot is a serious piece of infrastructure for a team that already has signing identities and a CI system, and it covers the awkward parts of app distribution that a store upload does not. Two things decide whether it suits you. The build defaults to package mirrors in China, so anyone elsewhere should pass the flag that turns that off before the first build. And the SDKs you will need for CI integration live in three separate repositories with no shared version, so budget time to check compatibility before wiring fastlane up.
Frequently asked questions
What platforms can Zealot distribute builds for?
The README lists macOS, iOS, Android in both apk and aab form, Windows and Linux. It also covers multi-architecture deployment for amd64 and arm64, and it includes an iOS device sync feature that can register a new device with Apple Developer in one action.
How do I deploy Zealot?
The project ships a Dockerfile and the README links a self-hosted installation page, with separate pages for the API, a developer guide and a user guide. The repository also carries a Procfile, a fly.toml and a render.yaml, so the same application can be targeted at Fly.io or Render as well as at your own container runtime.
Where do the Zealot iOS and Android SDKs live?
In separate repositories rather than in this one: an iOS package, an Android package and a fastlane plugin, all published under the same owner. The README describes them together as the developer kit, alongside the REST API.
Can I log in to Zealot with an existing account system?
Third-party sign-in is supported for Feishu, GitLab, GitHub, Google, LDAP and OIDC. The feature list also names a webhook that can forward events to any notification service, so distribution events do not have to stay inside the app.
What licence is Zealot released under?
MIT. The licence file is referenced from the repository's develop branch, and the most recent release tags are 6.2.2 and 6.2.1, both published in July 2026.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tryzealot-zealot)Star history chart for your README
[](https://hysenlabs.com/projects/tryzealot-zealot)Was this useful?