LiveContainer

LiveContainer runs guest iOS apps inside its own installed host. It is an app launcher, not an emulator, hypervisor, normal IPA installer, or jailbreak.

Why it exists

A free Apple Account normally allows only three installed apps and ten App IDs during a seven-day period. LiveContainer can hold many guest apps while consuming one host app slot and App ID. The host still needs a valid installation and refresh path.

The official project requires iOS/iPadOS 15 or later and AltStore 2.0+ or SideStore 0.6.0+ for its standalone path (LiveContainer).

The trade-offs

• Guest apps are not ordinary SpringBoard installations.
• Guest entitlements do not become host entitlements.
• App extensions are not registered normally.
• Remote push notifications do not work.
• URL schemes, file pickers, notifications, and hardware services may need workarounds.
• Guest apps inside LiveContainer are not sandboxed from one another in the normal per-app way.
• Some apps need JIT; others can use JIT-less signing.

That shared guest environment makes the provenance of the LiveContainer build especially important. The maintainers warn that a modified host can access guest app data and credentials.

Best use cases

• Testing several low-risk apps under one Personal Team slot.
• Multiple versions or data containers of an app.
• Apps that do not depend heavily on extensions, push, App Groups, or protected services.
• Advanced users who understand when JIT is required.

Poor use cases

• Banking, password-manager, work-authentication, or other sensitive guests.
• Apps requiring reliable push notifications or extensions.
• Users expecting every app to behave exactly like a native installation.

Installation variants

LiveContainer ships as standalone and SideStore-integrated variants. Follow the project's current installation documentation because minimum SideStore/AltStore releases, extensions, pairing, and JIT helpers change frequently.