Deployment and onboarding

CryoMaestro is delivered through a controlled onboarding process. Public documentation intentionally does not publish source-level installation commands, internal service topology, implementation language, or production credentials.

Information your facility provides

• Instrument and detector inventory, supported acquisition modes, and operator contacts
• Identity provider, role model, network zones, remote-access policy, and audit requirements
• Storage roots, retention policy, backup and recovery objectives, and expected data rate
• Compute resources, schedulers, accelerators, concurrent workloads, and maintenance windows
• Required integrations, approved third-party software, and license ownership
• Security, privacy, procurement, accessibility, and validation requirements

Acceptance stages

1. Architecture review — boundaries, data flows, integrations, and responsibilities are documented.
2. Non-production deployment — access, storage, backup, monitoring, and update paths are tested.
3. Instrument simulation — workflows and failure handling are exercised without live mutation.
4. Bounded instrument validation — trained staff supervise limited actions and verify readback.
5. Operational acceptance — the facility signs off on procedures, recovery, training, and ownership.

Deliverables

Your deployment package should include version-specific runbooks, environment-specific settings, recovery procedures, an integration inventory, operator training material, and an acceptance record. Those controlled documents take precedence over generic website guidance.