Free-AppleId-Serve: a daily-updated shared Apple ID and proxy node repository

What Free-AppleId-Serve actually distributes

The repository solves a narrow access problem: getting a US-region Apple ID so that a user can install Shadowrocket from the App Store, and getting a proxy subscription so that the installed client has somewhere to connect. It is aimed at readers who are not comfortable buying an overseas account or running their own server, and who want a copy-paste path instead. The README lists the audience indirectly through its own framing: it says the shared accounts update daily, and it repeatedly points to paid airports and exclusive accounts for people who want stability. That split is the honest description of the project. The free tier is a trial surface. The repository is written in Chinese, with an English README-EN.md alongside it, and the primary language of the code is Python. The topics list covers appleid, clash, quantumult-x, shadowsocks, v2ray and chatgpt, which matches the range of client tutorials stored as markdown at the top level. Anyone expecting a maintained proxy service will be disappointed. Anyone looking for a set of setup guides for iOS and desktop clients will find them here.

The Python side: apple.py and a requirements.txt with three pins

The code in the repository is small. requirements.txt pins beautifulsoup4==4.9.3, requests==2.25.1 and pytz, and apple.py is the script that uses them. The combination tells you the mechanism without needing to run it: requests fetches a page or an endpoint, BeautifulSoup parses the HTML, and pytz handles the timezone so that the daily update is stamped correctly. The output is content, not a running service. There is no server component, no API, and no database in the repository layout. The top-level entries are almost entirely markdown tutorials (Android-Clash-Meta, MacOS-ClashX-Pro, Windows-Clash-Verge-Rev, Windows-v2rayN, iOS-Shadowrocket, iOS-Sing-box, and others), plus an images directory and a .github directory. That shape matters for evaluation. The Python is a build step for the README, and the README is the product. If the upstream page changes its markup, the parser breaks and the daily update stops being daily. The repository does not document a fallback for that case.

Setting up the scraper from requirements.txt

The README does not give install steps for apple.py, so the only concrete dependency information comes from the repository file itself. Here is that file in full.

beautifulsoup4==4.9.3
requests==2.25.1
pytz

Those three lines are what a reader can act on. The README is silent on the Python version, on how to invoke apple.py, and on where its output is written, so anything beyond installing those pins would be guesswork. If the goal is only to configure a client, the markdown tutorials at the top level need no build step at all: iOS-Shadowrocket（小火箭）-使用教程.md, MacOS-ClashX-Pro-使用教程.md and Windows-v2rayN使用教程.md are plain files. The README also points to a mirror at help.wwkejishe.top/free-shadowrocket for the same content, which is the practical entry point when GitHub is slow.

Where the shared-account model breaks down

A shared Apple ID is a single credential used by an unknown number of people. Apple's own account protections work against that: sign-in attempts from many locations trigger verification, and the README acknowledges a related failure mode in its ChatGPT section when it says that a phone verification step is a risk-control response and must be solved by the user. The same logic applies to the Apple ID. The README does not document rollback, account recovery, or what to do when a shared ID is locked, and it does not state a licence, which leaves redistribution terms undefined. There is also a practical limit on the free nodes: the README describes them as shared and updated daily, and separately recommends paid airports for people who want stability. That is the project telling you the free tier is not the stable tier. The wrong user for this repository is anyone who needs a reliable connection for work, or who would sign in to a shared Apple ID with a personal iCloud account attached. Use a separate Apple ID for App Store downloads only, and expect the credential to stop working without notice.

How this differs from running your own server

The alternative approach in the same README is self-hosting: buy a VPS and deploy a proxy stack yourself. The README includes a long prompt for an AI agent that walks through installing Docker, Marzban, Cockpit and Netdata on a VPS, creating a VLESS + Reality inbound, and generating subscription links and QR codes for Clash Meta, v2rayN, Nekobox and Shadowrocket. The difference in approach is ownership. With Free-AppleId-Serve you consume someone else's credentials and nodes, you get no control over uptime, and you share capacity with everyone else reading the page. With a VPS you pay for the machine, you hold the keys, and the node stays up as long as you maintain it. The cost is time and a monthly bill. The README also lists Just My Socks as a middle option, described as a managed service from the BandwagonHost side with multiple routes, which trades money for not having to run anything. Three tiers, three trade-offs: shared and free, managed and paid, or self-hosted and paid with your own labour.

Maintenance, licence and upgrade cost

The last push to the repository was on 2026-09-14, and the README carries an update date of 2026年9月14日, so the daily-update claim is consistent with the commit history at the time of writing. The repository is not archived. Maintenance work here is content maintenance: refreshing account lists, node subscriptions and tutorial screenshots. Upgrades to the Python side are a different matter. The pins in requirements.txt are old (requests 2.25.1 and beautifulsoup4 4.9.3), and pip will install them as written, but any later environment that resolves dependencies differently may need those pins relaxed. No releases are listed, so there is no versioned artifact to track. The licence is not stated in the repository metadata, which means the terms for reusing the markdown or the script are undefined; if you plan to redistribute the content, that gap is the first thing to resolve, and it is a question for the author rather than something to infer. Nothing in the repository indicates a support commitment.

A first real use: from shared ID to a working client

The intended flow, based on the tutorial files, is: get a US-region Apple ID, sign in to the App Store with it (not with iCloud), install Shadowrocket, then import a subscription. The iOS tutorial file is named iOS-Shadowrocket（小火箭）-使用教程.md. The README's mirror page at help.wwkejishe.top/free-shadowrocket is presented as an identical, domestically reachable copy of the same content, which is the practical entry point if GitHub is slow. For desktop users the equivalent paths are MacOS-ClashX-Pro-使用教程.md and Windows-v2rayN使用教程.md, and the README notes a separate guide for swapping the Clash for Windows core to the mihomo core. The README does not include a literal subscription address in the extracted text, so treat any link you find on the mirror page as the source of truth and verify it before importing. Expect the node list to change on the next daily update.

Editorial conclusion

Adopt this repository only as a pointer: read the tutorial markdown files for ClashX Pro, v2rayN or Shadowrocket setup, and treat the shared Apple ID and free node links as disposable. Do not adopt it if you need a stable connection, a private account, or any guarantee that a node will work tomorrow, because the README itself routes users toward paid airports and exclusive accounts for stability. Before using anything here, verify the licence, since the repository does not state one, and check whether the apple.py scraper still runs against the current page structure.

Frequently asked questions

Official sources

1. dongyubin/Free-AppleId-Serve on GitHub
2. Issues
3. Project website
4. README