Skip to main content
CryoMaestro
Quick Start

Contact

Find the right route.

CryoMaestro is deployed under agreement rather than downloaded, so the channel that reaches someone useful depends on who you are. Pick the line below that describes you.

  1. 01

    Customers and deployment operators

    Use the contacts supplied with your deployment.

    Support and security routes are issued with your deployment package or commercial agreement. They reach people who can see your configuration, which a public inbox could not.

    Include

    • Product version and the affected workflow
    • Time window, in the facility’s local time
    • User-visible symptoms, and what you expected instead
    • Non-sensitive diagnostic identifiers — session, run, or job ids

    Never send ·  Research data, credentials, licence keys, and instrument secrets — unless the approved support procedure explicitly asks for them through a protected channel.

    Support and reporting routes
  2. 02

    Evaluating CryoMaestro

    Evaluation runs through onboarding, not a download.

    Deployments are sized against your instruments, storage, and compute during onboarding, and demonstration packages are issued through a CryoMaestro contact rather than published publicly.

    What the platform covers Cost of an instrument-hour Requesting a demonstration
  3. 03

    Reporting a vulnerability

    Not through any public channel.

    Customers should use the private security contact in their agreement. Until a general private-reporting address is published, do not post technical vulnerability details anywhere public — including issue trackers, forums, or social platforms.

    Responsible reporting Security configuration
  4. 04

    Extensions and partnerships

    Through an approved partner or facility relationship.

    Development materials for typed, reviewed extensions are provided under the applicable agreement. The public plugin catalogue is metadata, not a development kit, and does not grant access to platform internals.

    How extensions are contracted

Why there is no address on this page

A public inbox nobody is accountable for is worse than none.

A general support address and a private vulnerability-reporting address will be published once the operating entity and the reporting process behind them are finalised. Until then, the routes above reach people who can actually act — and no message is quietly collected by a channel nobody owns.

This site runs no contact forms, no analytics, and no third-party trackers, which is stated in full in the privacy notice.