Support and responsible reporting

Not sure which of these applies to you? Contact routes by audience.

Customers and deployment operators

Use the support and security contacts in your deployment or commercial agreement. Include the product version, affected workflow, time window, user-visible symptoms, and non-sensitive diagnostic identifiers. Do not send research data, credentials, license keys, or instrument secrets unless the approved support procedure explicitly requests them through a protected channel.

Product feedback

Customers should use the support route supplied with their deployment. A general public feedback address has not yet been published; do not submit product details or confidential information through an unverified third-party channel.

Security reports

Do not disclose vulnerability details publicly. Customers should use their private contractual security contact. Until a general private-reporting address is published, do not send technical vulnerability details through public channels.

Extension proposals

Extension development materials are provided only through an approved partner or facility relationship. Public catalog metadata is not a software-development kit and does not grant access to platform internals.