The durable part of this announcement is that BigBearCasaOS became a default/pre-installed app-store option across IceWhale's ecosystem rather than something every CasaOS or ZimaOS user had to add manually. The current BigBearCasaOS repository still describes the store as pre-installed alongside IceWhale's own app store on CasaOS, ZimaOS, and IceWhale hardware.
The equally important boundary is ownership. BigBearCasaOS is not the same project as IceWhale's first-party App Store. BigBearTechWorld says it is independently developed and maintained by BigBearTechWorld/BigBearCommunity, and explicitly says IceWhale does not fund the project. A package being visible by default therefore should not be interpreted as IceWhale taking over upstream maintenance or support for every BigBear app.
What “Default” Changed for Users
Before the integration, CasaOS users commonly added the BigBear store manually using its repository ZIP. The 2025 announcement said the curated catalog would be available out of the box on IceWhale platforms, reducing the setup needed to reach a much larger application selection.
BigBear Remains a Separate App Store
The current BigBear README describes the store as pre-installed alongside IceWhale's own store. That wording matters: the catalogs can coexist, and their app packages, update cadence, maintainers, and support channels are not identical.
See the current BigBearCasaOS repository.
App Updates Are Maintained by BigBearTechWorld
The repository currently lists more than 200 applications and uses automated platform-sync workflows. That does not mean each upstream application is authored by BigBear; the project packages third-party Docker applications for CasaOS/ZimaOS and tracks their versions separately.
When an app breaks after an image update, identify whether the package came from IceWhale's first-party catalog, BigBear, or another community store before deciding where to report it.
Support Follows the Package Maintainer
BigBear's current README directs package issues and feature requests to the BigBearCommunity. IceWhale support may still help diagnose ZimaOS-level Docker, storage, or networking behavior, but a broken BigBear Compose definition or stale BigBear version remains a third-party package concern.
ZimaOS App Store 2.0 Makes Store Identity More Explicit
ZimaOS 1.7 introduced App Store 2.0 with a redesigned discovery/management model and a formal v2 store protocol. Current developer documentation gives each store its own stable store_id, maintainer metadata, URL, localized description, and independent generated catalog.
Use the current ZimaOS store identity model.
Review Third-Party Packages Before Giving Them Powerful Mounts
A default-listed community package can still request Docker socket access, host networking, privileged mode, GPU devices, or broad storage mounts. Read the current Compose definition and upstream documentation before installing sensitive applications.
BigBearCasaOS FAQ
Is BigBearCasaOS currently described as pre-installed on IceWhale platforms?
Yes. BigBear's current repository still says it comes pre-installed alongside IceWhale's own store on CasaOS, ZimaOS, and IceWhale hardware/software platforms.
Is BigBearCasaOS maintained by IceWhale?
No. BigBear explicitly says the project is independently developed and maintained by BigBearTechWorld/BigBearCommunity.
Does “default store” mean every BigBear app is an IceWhale first-party app?
No. The store integration and the individual package/upstream ownership are separate concerns.
