CasaOS users have reasonable grounds to ask whether the project has been abandoned, but the evidence is more nuanced than a simple yes-or-no answer. The community thread began in February 2025 after users noticed that the main CasaOS repository had not published a new stable release since December 2024 and many GitHub issues appeared inactive.
As of 2026, the CasaOS core stable release cadence is clearly much slower than it was before, and development attention has shifted heavily toward ZimaOS. At the same time, it is not accurate to say every CasaOS-related project stopped: the CasaOS App Store continued receiving commits in 2026 and published a v2.0.0 release in July 2026, while related CasaOS repositories and pull requests also continued to exist. The safest conclusion is that CasaOS core development has slowed substantially, while parts of the broader ecosystem remain maintained.
Why Users Thought CasaOS Had Been Abandoned
The original author raised the question on February 24, 2025 because the main CasaOS release had not changed since December 2024 and GitHub issues appeared to be accumulating without visible progress.
The concern grew stronger later in the thread. In August 2025, the same user pointed out that almost nine months had passed since the December 19, 2024 CasaOS release. By February 2026, other users were also describing CasaOS as abandonware and asking how to migrate existing Ubuntu/Docker installations.
Those observations are source-supported: the main CasaOS GitHub releases page still shows v0.4.15 as the stable core release published on December 19, 2024.
There Is No Source-Supported Official EOL Statement in This Thread
The important distinction is between slow or stalled core releases and an official end-of-life announcement. The source thread does not contain an IceWhale statement saying that CasaOS has been formally discontinued, killed, or declared end-of-life.
Several community members inferred abandonment from the release cadence. That is their interpretation, not an official product lifecycle notice.
When publishing this page, do not turn a community conclusion into an official statement that IceWhale has not made.
Development Attention Shifted Toward ZimaOS
Multiple community replies explained that IceWhale is a relatively small team and that much of its development effort had shifted toward ZimaOS and newer Zima hardware.
That is consistent with the visible product direction. ZimaOS is now IceWhale's actively developed NAS-focused operating system, with current documentation and ongoing product integration.
Users evaluating that newer path can review ZimaOS.
The thread also discussed ZimaBoard 2 as a newer hardware direction. The current product path is the ZimaBoard 2 single-board server.
The CasaOS App Store Was Still Active in 2026
One reason the word “abandoned” is too broad is that CasaOS-related repositories did not all stop moving.
The CasaOS App Store repository shows active commits during 2026, including app updates, documentation work, build-system changes, and new store metadata. The App Store also published v2.0.0 in July 2026.
That does not mean the CasaOS core is receiving the same development investment as ZimaOS. It means the ecosystem has not uniformly gone dark.
CasaOS Core, UI, App Store, and Apps Are Different Layers
A recurring point in the community discussion was that users often treat every problem in a CasaOS-managed application as a CasaOS core bug. CasaOS is a management layer around Docker and storage integrations; the containers themselves come from upstream projects.
It helps to separate four layers:
- CasaOS core: the main service and API layer.
- CasaOS UI/components: the web interface and supporting services.
- CasaOS App Store: app definitions and metadata.
- Upstream applications: Nextcloud, Jellyfin, OneDrive/rclone integrations, and other containerized software.
A stale upstream API or container can break even if CasaOS itself has not changed. Conversely, a problem in CasaOS's integration code still requires IceWhale-side work.
The OneDrive Issue Shows Why Layering Matters
The thread included a practical example. The original author reported that OneDrive mounted but files would not open, while Dropbox and Google Drive still worked.
An IceWhale team member suggested updating rclone:
sudo rclone selfupdateThe user confirmed that this fixed the OneDrive issue in February 2025.
This showed that at least one apparent “CasaOS problem” was related to an outdated dependency rather than proof that the whole platform was dead.
But 2026 Also Showed the Cost of Slow Integration Maintenance
In January 2026, another user posted an Azure authentication error indicating an expired Microsoft application client secret in the OneDrive integration. That is a different failure from an old rclone binary and illustrates why cloud integrations need ongoing maintenance even when the local Docker-management layer remains stable.
The thread does not contain a confirmed resolution for that 2026 expired-secret error. Do not reuse the 2025 rclone selfupdate fix as a universal answer for every later OneDrive authentication failure.
CasaOS Is Not a Full Linux Distribution in the Same Sense as ZimaOS
Community replies repeatedly emphasized that CasaOS is installed on top of an underlying Linux system such as Debian or Ubuntu. Your base operating system, Docker engine, kernel, storage, and network stack continue to exist separately from the CasaOS management layer.
This matters when planning a migration: removing or replacing CasaOS does not automatically mean the underlying Linux host disappears, but it also does not guarantee that every app, network, volume, and Samba setting can be moved without planning.
Should You Keep Using CasaOS?
Remaining on CasaOS can still be reasonable when:
- your current setup is stable;
- you understand the underlying Linux/Docker host;
- you do not depend on rapid CasaOS core feature releases;
- the applications you run continue receiving their own upstream updates;
- you have backups and can maintain the host if a CasaOS integration stops working.
There is no requirement to migrate a stable server simply because the UI has a slower release cadence.
When Should You Consider Migrating?
A migration becomes more reasonable when:
- you depend on a CasaOS integration that is no longer functioning;
- you need security or platform fixes that are not arriving in the core project;
- your host operating system has moved beyond the versions CasaOS expects;
- you want active first-party NAS features available in ZimaOS;
- or you prefer managing Docker directly with another maintained interface.
ZimaOS Is Not a Drop-In Upgrade for Every CasaOS Host
One February 2026 participant specifically used CasaOS on a general-purpose Ubuntu computer for gaming and Docker workloads and did not want a dedicated NAS operating system. That is an important use-case boundary.
ZimaOS is an operating-system deployment, not a package you simply install over an existing Ubuntu desktop while preserving the machine's role unchanged. If the current host is also your desktop or gaming PC, plan a migration as an infrastructure change rather than a CasaOS package update.
Can You Move to Plain Docker or Portainer?
The community later asked whether removing CasaOS and managing the existing Docker environment with Portainer CE or standard Docker tools would be a reasonable option.
Conceptually, yes: CasaOS-managed applications are Docker containers, and Docker volumes, bind mounts, networks, and Compose definitions are Docker concepts. But the source thread does not provide a verified one-command CasaOS-to-Portainer migration procedure.
Before removing CasaOS:
- Export or record every app's Compose/configuration.
- Record host-to-container volume mappings.
- Record Docker networks and exposed ports.
- Back up app configuration directories and databases.
- Document CasaOS-managed Samba or cloud-storage integrations separately.
- Confirm which services are CasaOS components and which are your own containers.
Do Not Uninstall CasaOS Blindly on a Production Host
Even if the Docker containers themselves can be recreated independently, CasaOS may also be managing mounts, storage integrations, app definitions, service files, and networking conveniences around them.
Take a host backup or snapshot where possible and test the exported Compose definitions before deleting CasaOS services.
CasaOS Status in 2026: The Most Accurate Summary
| Area | Observed status |
|---|---|
| Main CasaOS stable core release | Stable release cadence has stalled since v0.4.15 in December 2024. |
| CasaOS App Store | Still showed active 2026 development and a v2.0.0 release in July 2026. |
| GitHub ecosystem | Issues and pull requests remain open; some related components continued receiving work. |
| Official EOL statement in source | None. |
| IceWhale product focus | Clearly shifted toward ZimaOS and newer Zima hardware. |
What CasaOS Users Should Do Now
- Do not panic-migrate a stable server solely because the core version number is old.
- Back up Docker app data and databases.
- Export or document container definitions.
- Keep the underlying Linux distribution and Docker engine secure and supported.
- Track upstream app updates separately from CasaOS updates.
- Watch the CasaOS GitHub repositories rather than relying only on the main version number.
- If a critical integration stops working, decide whether to repair it independently, move to direct Docker management, or migrate to another platform.
- If moving to ZimaOS, treat it as an OS migration rather than an in-place CasaOS upgrade.
CasaOS Development Status FAQ
Has IceWhale officially said CasaOS is abandoned?
Not in the source thread or the public evidence used for this page. Community users have described it as abandoned because the stable core release cadence stalled, but that is not the same as an official end-of-life announcement.
When was the last stable CasaOS core release?
The main CasaOS GitHub releases page shows v0.4.15 from December 19, 2024 as the stable core release referenced throughout the community discussion.
Is anything CasaOS-related still maintained?
Yes. The CasaOS App Store showed active commits in 2026 and released v2.0.0 in July 2026. That does not erase the core-release slowdown, but it shows the broader ecosystem is not completely inactive.
Should every CasaOS user move to ZimaOS?
No. ZimaOS is a different operating-system deployment and is better suited to some dedicated-server/NAS workflows. CasaOS users running a general-purpose Ubuntu or Debian machine need to evaluate the migration impact first.
Will my Docker containers survive if I remove CasaOS?
The thread does not provide a guaranteed migration procedure. Docker containers and data can often be recreated independently, but you should export configurations, volumes, networks, databases, and CasaOS-managed services before removing anything.
