How to Create and Share an AltStore Repo with CocoCloud
If you've used AltStore, Scarlet, eSign, or any similar sideloading client, you've added a "repo" or "source" — a URL that lists a bunch of installable apps in one place. CocoCloud can turn your own signed apps into exactly that kind of source, with a public link you can share, a real showcase page, and one-tap "add to my client" buttons. Here's how to set one up.
Creating a Repo
Head to User → Repos and create a new one. You'll fill in:
- Repo name and Subtitle
- Description (up to 2,000 characters) — shown in the CocoSign app's community directory if you opt into that later, not inside AltStore/Scarlet itself
- Scope —
both(default),signed, orunsigned, controlling which of your apps are eligible to appear in it
Standard accounts get one repo; Pro accounts can create as many as they want.
Customizing It
From the repo's edit page you can set:
- A tint color (defaults to
#4C6FFF) that sideloading clients use to theme the source - An author name (defaults to your username)
- A custom icon
- Exactly which of your apps are included, via a per-app checkbox picker
- Whether the repo is public, and whether it's listed in the CocoSign app's community directory — both are separate toggles you control
The edit page also shows your repo's URL with a one-tap copy button, so you don't have to piece it together yourself.
Two Different Links, Two Different Audiences
Every repo has two URLs, and they serve different purposes:
/repo-sharing/{token}— a human-facing showcase page. This is what you post in a Discord server or send to a friend so they can browse the apps before deciding to add the source./repo/{token}.json— the raw machine-readable manifest. This is the actual URL you paste into a sideloading client's "add source" field.
The manifest is deliberately built to match the format real-world community repos use (closer to what clients like Scarlet, TrollApps, eSign, and GBox expect) rather than a narrower spec, so it should drop into most of the popular clients without any extra fuss.
One-Tap "Add Source" Links
Rather than making people copy-paste the manifest URL into their client manually, you can link directly into most clients with a custom URL scheme:
| Client | Link format |
|---|---|
| AltStore | altstore://source?url={repo_url} |
| Scarlet | scarlet://repo={repo_url} |
| eSign | esign://addsource?url={repo_url} |
| GBox | gbox://AddSource/{repo_url} |
| Feather | feather://source/{repo_url} |
| CocoSign app | cocosignapp://source/{repo_url} |
({repo_url} is your /repo/{token}.json link, URL-encoded where the client expects a query parameter.) Drop a row of these buttons wherever you're sharing your repo and people can add it in one tap instead of hunting for the "add source" field themselves.
A Detail Worth Knowing: What Actually Expires
Your repo's URL itself is permanent and bookmarkable — it won't stop working on its own. What is time-limited are the individual app download links generated inside the manifest each time it's fetched (capped at two hours, for security). In practice this is invisible to end users: a client that re-fetches your repo's manifest gets fresh download links automatically. The only time it matters is if someone saves a raw download URL out of the manifest directly instead of going through their client — that specific link can go stale, even though the repo itself hasn't.
Getting Discovered
If you'd rather not rely purely on word of mouth, toggling "Display on CocoSign App" lists your repo in the official CocoSign app's community directory, so people browsing there can find and add it without you sharing a link at all.
Recap
Create a repo, pick which apps go in it, customize the name/icon/color, grab the /repo/{token}.json link (or the friendlier /repo-sharing/{token} page to share first), and optionally list it in the community directory. That's a fully working AltStore-style source, no server of your own required.
Comments (0)