CII HERO keeps the working database local for speed and day-to-day operation, while backing every transaction up to the cloud so your records are not dependent on one workstation alone.
CII HERO is local-first, not local-only. The working database lives on the designated pharmacy workstation so daily use stays fast and responsive. At the same time, each transaction is backed up to the cloud for disaster recovery.
CII HERO keeps its working database on the pharmacy workstation where staff are actually doing the daily Schedule II work. That local-first design supports the performance the app was built for and avoids making ordinary day-to-day operation dependent on internet access.
The local database is encrypted. That means the pharmacy keeps the speed of a local workflow without treating the workstation like an unprotected notebook or spreadsheet.
The cloud is used for disaster recovery, not as the primary workflow surface. Each transaction is backed up so the record trail is still recoverable if a workstation needs to be replaced or restored.
This is a practical split: local for speed and focus, cloud for recovery and continuity.
If the workstation fails, install CII HERO on a replacement PC, activate it, choose the cloud restore path in the migration flow, and restore from cloud. You can also use Settings > Security > Restore from Cloud after setup if needed.
That means the pharmacy is not starting over from scratch just because one machine needs to be replaced.
Single-station is a workflow choice, not a data-risk choice. The app centralizes the CII workflow for accountability, but the record trail is still backed up so the pharmacy is not exposed to a single-device failure.
CII HERO is not choosing between speed and safety. It is using local-first design so the app stays fast and using cloud backup so the record trail stays recoverable.
Read the local-first workflow guide, the C2 compliance guide, or the full FAQ if you want the operational reasoning behind the CII HERO design choices.
Read the FAQ