AssppWeb iOS IPA installer: self-hosted review
AssppWeb is a practical self-hosted iOS IPA installer for users willing to operate the security boundary themselves. Its browser-side credential handling is thoughtful, but a public host can still serve altered code; self-hosting and HTTPS make it worth using.
A self-hosted iOS app installer
AssppWeb is a self-hosted iOS sideloading web app that signs into Apple services, searches for apps, obtains licenses, and builds installable IPAs. Apple API traffic stays in the browser through WebAssembly, while the server relays TCP and compiles files from public CDN downloads.
Installing IPAs without the App Store
AssppWeb provides a browser-based workflow for obtaining iOS apps from outside the App Store, and server operators need not provide Apple ID credentials. It combines Apple ID authentication, license acquisition, downloading and compiling an IPA, and device installation all within one deployable service.
Browser-side authentication and blind relay
- โApple ID authentication runs inside the browser, keeping credentials away from the AssppWeb server under its intended operating conditions.
- โApple API requests use WebAssembly with libcurl.js and Mbed TLS 1.3, avoiding an Apple executable or private framework.
- โThe backend operates as a blind TCP relay through the Wisp protocol rather than interpreting the encrypted application traffic.
- โA fresh browser-side SAP exchange signs the exact request body with X-Apple-ActionSignature, while verification-code submissions continue in the same in-memory session.
- โCompiled IPAs are downloaded from public CDN sources and exposed through install manifests for itms-services installation on a device.
- โDeployments can use a local Docker Compose setup, Cloudflare Workers with Containers, Railway, or a manually managed Docker Compose server.
Deployment options and requirements
For a local source build with OrbStack or Docker, run `docker compose -f compose.yml -f compose.local.yml up --build -d`, then open `http://localhost:8080`. For Docker Compose, download `compose.yml` with `curl -O https://raw.githubusercontent.com/Lakr233/AssppWeb/main/compose.yml` and run `docker compose up -d`. Cloudflare deployment uses Workers with Containers and the `ghcr.io/lakr233/assppweb:latest` image, but requires a paid plan and the specified Workers, Containers, and Cloudchamber permissions. Railway can deploy the same image; configure `/api/settings` as the healthcheck path, mount `/data`, and set `DATA_DIR=/data`. iOS installation requires a reverse proxy with a valid TLS certificate and working WebSocket support.
Strengths
- โCredentials remain in the browser during the normal AssppWeb flow instead of being submitted to the backend.
- โThe Wisp relay and WebAssembly request stack make the intended security boundary unusually explicit.
- โDeployment choices cover local development, Railway, Cloudflare, and conventional Docker Compose hosting.
- โIPA compilation, install manifests, storage controls, and access-password settings are handled by the same application.
- โThe MIT license makes the AssppWeb source available for inspection, modification, and commercial use.
Security and infrastructure limitations
- โณA public AssppWeb host can serve a modified frontend that captures Apple credentials before encryption. There are no official public instances, so self-hosting or a trusted partner is the sensible choice.
- โณInstalling apps through itms-services requires HTTPS with a valid certificate. Misconfigured forwarded-protocol headers can also cause redirect loops.
- โณThe reverse proxy or CDN must support WebSocket connections at `/wisp/`; otherwise AssppWeb cannot communicate with Apple servers.
- โณCloudflare deployment requires a paid plan because Workers Containers are unavailable on the free plan.
- โณPublic instances need rate limiting, access controls, and CDN protection because IPA downloads can consume substantial bandwidth.
Related iOS acquisition projects
Frequently asked questions
The AssppWeb server is designed not to receive Apple ID credentials because Apple API communication runs in your browser through WebAssembly. However, an untrusted host could modify the frontend and capture credentials before encryption, which is why self-hosting is recommended.
Self-hosting AssppWeb lets you control which frontend code is served and where the service runs. A public instance could serve altered JavaScript that captures Apple credentials before encryption, and the AssppWeb README states there are no official public instances.
AssppWeb needs a reverse proxy with a valid TLS certificate because iOS requires HTTPS for itms-services installation links. The proxy must also allow WebSocket connections at `/wisp/` so the browser-side Apple communication can reach the relay.
The AssppWeb Cloudflare deployment cannot use Workers Containers on the free plan. A paid Cloudflare plan is required, along with a deployment token that grants Workers Scripts Edit, Containers Edit, and Cloudchamber Edit permissions.
AssppWeb uses the Wisp protocol over WebSocket to provide a blind TCP relay for browser-side Apple API traffic. The server transports the connection without receiving the Apple ID credentials or encrypted application payload handled by the browser.
Yes. AssppWeb is distributed under the MIT License, which permits commercial use, modification, distribution, and sublicensing. The license terms still apply, including preservation of the license and copyright notice.
Best use cases
- โขFor a home-lab operator who wants to run the complete iOS acquisition and installation flow on hardware they control.
- โขWhen an organization needs a private AssppWeb instance rather than trusting an unknown public frontend with Apple authentication.
- โขFor testing an iOS sideloading web app against local source changes before making the service available to other users.
- โขWhen Railway or Cloudflare deployment fits an existing cloud operations setup and the paid-container requirements are acceptable.
Who should try it โ and who should skip
AssppWeb suits self-hosters and technically experienced iOS users who want an iOS IPA installer under their own control. It is a poor casual choice for anyone unwilling to secure a server, validate TLS, support WebSockets, and trust the frontend code served to the browser. Users who only need occasional App Store distribution should use Apple's normal installation path instead.
Still deciding about AssppWeb?
One click hands the question to an AI along with this page โ see what it says about AssppWeb.
