A single uniform interface that lets any circuit in the stack run unchanged on any backend — whether a local simulator, a cloud quantum API, or direct hardware. Hardware portability without application rewrites.
Quantum hardware is rapidly evolving — new providers emerge, qubit counts grow, and access models change. An application built directly against a single vendor's API becomes a liability as the hardware landscape shifts.
The hardware abstraction layer insulates every φCoherent application from those changes. Circuits are described once, against a backend-neutral interface. At runtime, the HAL routes execution to whichever registered backend is appropriate — a local simulator for development, a cloud API for scale, or direct hardware for final runs. Switching providers requires no application code changes: only the backend registration changes.
All circuit submission, job management, and result retrieval goes through a single interface regardless of backend. Application code never imports vendor-specific symbols.
A singleton registry where simulators and hardware API adapters register themselves. Any registered backend is immediately available to any code that calls through the HAL.
Switch from simulator to hardware — or from one hardware provider to another — by changing the registered backend, not by modifying the application or its circuits.
Results from all backends arrive in the same typed format, so post-processing, error-correction, and analysis code handles simulator and hardware results identically.
Portability layer — sits between all application code and all physical backends. The transpiler, runtime, and algorithm packages all submit circuits through the HAL. Adding support for a new quantum hardware provider requires writing one adapter that implements the HAL interface; nothing else in the stack changes.
Published under the GNU AGPLv3 with whitepaper and reference implementation. Commercial licensing is available for closed-source deployments.