Draft a E-Mail Communication with users, before/after merge

[mrnicegyu11]

[mrnicegyu11]

Dear o²S²PARC / osparc.io users,

On March 21st of 2026 we will start a planned backend migration of osparc.io to a shared deployment operated together with the sim4life.io app developed by Zurich MedTech (ZMT). This work is part of the NIH Common Fund’s SPARC program efforts to provide a sustainable, long‑term home for the o²S²PARC / osparc-simcore platform and its growing community of students and researchers.

To carry this out safely, osparc.io will be unavailable for up to 3 days starting March 21st. During this window the website and APIs may not be reachable, and running or new simulations will be paused. Please plan any time‑critical work accordingly and download any results you might need during that period.

For you as a user, this is intended to be a pure backend move: You will still access the platform via osparc.io, and the interface, projects, and services should look and behave essentially as they do today. Your account, groups, and projects, as well as your data in object storage and databases, will be migrated using dedicated, tested procedures so that strongly linked data and metadata remain consistent. The teams behind o²S²PARC and Sim4Life are coordinating this work with a strong focus on data integrity and reproducibility, in line with the SPARC program’s mission.

​The commercial sim4life.io tool and the academic osparc.io platform are powered by the same open-source o²S²PARC / osparc-simcore technology, developed under the NIH SPARC program and released under an MIT license. Sim4Life.web builds directly on this cloud framework to deliver the Sim4Life capabilities through a browser, which makes it natural to host osparc.io on the same technical foundation. Merging the o²S²PARC and Sim4Life deployments reduces duplicate infrastructure and DevOps overhead, freeing resources to improve stability, performance, and scientific features across the shared platform. In the longer term, it will also strengthen integration with the Sim4Life ecosystem and its advanced anatomical and physiological modeling capabilities that many of you already use for in silico research.​

If you would like to stay informed about this migration, its completion, and future improvements to the platform, please subscribe to ZMT / Zurich MedTech news and announcements, which are the primary channels for updates about Sim4Life and o²S²PARC in the future.

​
Thank you for your understanding and for trusting us with your data and research during this transition.

[mrnicegyu11]

Dear o²S²PARC / osparc.io users,

The migration of osparc.io to the shared backend deployment operated together with Sim4Life / Zurich MedTech (ZMT) has been successfully completed, and the platform is available again. The move consolidates the SPARC-funded o²S²PARC / osparc-simcore infrastructure with the cloud servers that also powers Sim4Life.io. You can continue to log in via osparc.io as before; your projects, services, and workflows should look and behave essentially the same, and your accounts, groups, and data have been migrated to the new environment. Behind the scenes, osparc.io now runs on the same cloud backbone that serves Sim4Life.web, which reduces duplicated infrastructure and allows more focus on stability.

​

Caveats, known issues, and workarounds (to be adapted before sending):

[Example] Some users may see older jobs listed as “unknown” or “failed” in the dashboard, even though their data is still present; if this affects you, you can safely re‑run the study or contact support with the study ID.

[Example] A small number of users might experience slower loading times for large projects while caches warm up on the new infrastructure; this should improve over the next days.

[Example] If you notice any missing services in your usual catalogs, log out and back in once; if the issue persists, please report it to the support contact listed on osparc.io.

If you encounter any unexpected behavior, missing data, or performance issues, please report them via the usual support channel linked from osparc.io, ideally including the study or project ID and a brief description of the problem. You can also reach out directly to ZMT / Sim4Life support through the contact options on the ZMT and Sim4Life websites if you suspect the issue may be related to the underlying shared infrastructure.​

Thank you again for your patience during the maintenance window and for your continued trust in the platform.