Platform · Architecture
Architecture built around institutional control.
How an AXIS CSM deployment is laid out: where capture happens, how sessions are coordinated, where recordings are stored, and where consent and access gates sit before anything leaves the hospital.
Deployment architecture
AXIS CSM deployment at a glance
AXIS CSM components
The role of each component
CSM OR Console application
Runs at the operating room on an interactive console, AXIS Edge or AxisEdge+. Captures, records and runs live sessions from compatible sources.
CSM Command Center
Coordinates rooms, sessions, users, recordings and storage requests across the institution.
CSM Live
The authorized viewing and collaboration experience for teaching rooms, auditoriums and remote participants, built on AXIS LIVE.
Storage patterns
On-premises, cloud and hybrid
Hospital / on-premises
Recording, storage and Command Center inside hospital infrastructure. No mandatory cloud upload.
Cloud with AXIS SurgiVault
Authorized media stored in the managed cloud for long-term retention and multi-site access.
Hybrid
Local recording with selective, policy-controlled transfer to AXIS SurgiVault.
Operating-room hardware
Two distinct edge platforms
| Attribute | AXIS Edge | AxisEdge+ |
|---|---|---|
| Summary | Compact edge hardware for running supported CSM OR Console application services at the operating room: recording, secure handling and live connectivity without requiring a full interactive workstation in every room. | GPU-equipped operating-room hardware designed to support compatible edge AI and advanced video-processing workloads alongside connected surgical workflows. |
| Role | Compact OT edge deployment | Advanced GPU-equipped OT edge hardware |
| Runs | Supported CSM OR Console application functions | Supported CSM applications plus compatible GPU-dependent workloads |
| Typical use | Recording, secure local handling, upload, streaming and Command Center connectivity | Edge connectivity functions plus acceleration for compatible AI and video processing |
| GPU | No dedicated GPU requirement implied | A dedicated GPU is the defining differentiator |
| Emphasis | Connect more operating rooms with a smaller footprint | Bring AI-ready compute closer to the operating room |
| Specifications | Source count, resolutions and I/O depend on configuration | GPU model, AI models, throughput and performance are verified per configuration |
| More | Explore AXIS Edge » | Explore AxisEdge+ AI Hardware » |
Specifications depend on selected configuration. Official specification sheets are provided on request.
Boundaries
Integration boundaries and gates
Plan your architecture with our team
Every deployment starts with a technical assessment of rooms, sources, network, storage and security requirements.