// the take
AssppWeb is a self-hosted web app for downloading IPA licenses from Apple's servers using your own Apple ID and sideloading them onto an iOS device, without going through the App Store. It's aimed at people who want to install apps on devices without the App Store app, or grab region-locked/delisted versions they're entitled to under their account.
The zero-trust design is the real engineering here: all Apple API traffic (auth, purchase, download) runs client-side in the browser via a WASM libcurl + Mbed TLS build, so a hosted instance's server only sees an opaque Wisp-over-WebSocket relay and never the Apple credentials themselves. The SAP authentication and X-Apple-ActionSignature signing were reverse-engineered and reimplemented rather than shelled out to ipatool or Asspp's native code, and there's real test coverage on the hard parts (sap handshake, crypto, wsProxy, manifest building) on both frontend and backend. Deployment is genuinely multi-target with working instructions for Docker Compose, Railway, and Cloudflare Workers+Containers, not just a single docker-compose.yml afterthought.
The project's own README admits the core threat model is incomplete: a malicious or compromised public instance can simply serve a modified frontend bundle and harvest Apple credentials before they ever hit the 'safe' client-side encryption, so the zero-trust claim only holds if you fully trust whoever's serving the JS. Everything hinges on undocumented, unstable Apple endpoints (the SAP exchange, purchase/license APIs) — these can and do change without notice, and there's no fallback path when Apple breaks something server-side. Self-hosting requires a reverse proxy that correctly forwards both HTTPS and WebSocket traffic for the Wisp relay; get that wrong (common with NAS proxies not setting X-Forwarded-Proto correctly) and you're stuck debugging redirect loops or a dead relay with no clear error surfaced to the user. There's no built-in rate limiting or abuse protection beyond an optional static access password, so a public instance eats full IPA-sized bandwidth (hundreds of MB per install) per request unless you bolt on a CDN yourself.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →