Channel / assistance

Support

Clear signal beats volume. We triage product issues, access questions, press asks, and partnership threads with the same discipline we apply to simulation systems.

Bugs Access Press Partners
Open ticket form

Routing

Send it down the right pipe first

Commercial Pricing & engagement

Scoping, quotes, licensing, and co-dev windows — start here if money or contracts are in play.

 Trust Security disclosure

Vulnerabilities and safety issues belong in the disclosure flow — not in a generic support ticket.

 Legal Privacy & data rights

Access, deletion, or policy questions route through privacy channels once published addresses exist.

Response cadence

We aim to acknowledge inbound messages within several business days, depending on volume and travel. Production incidents for signed partners use escalation paths defined in your statement of work.

A public status dashboard may appear here when online services need uptime transparency. Until then, active partners hear from us through agreed channels.

Before you write

  • Do not paste secrets — redact tokens, keys, and credentials.
  • One thread per issue keeps history coherent for everyone.
  • Link to repro assets under NDA instead of attaching huge binaries blindly.

Signal quality

What a strong bug report carries

Platform (PC / console / cloud) and hardware class when it changes repro odds.
Build identifier, branch, or version string we can grep in CI.
Minimal reproduction steps and expected vs. actual behavior.
Logs or crash dumps you are contractually allowed to share.
Screenshots or short video when visuals disambiguate the defect.
Timezone and session length if the bug is time or heat related.

Ticket intake

Submit a request

Tell us what happened, what you expected, and what you already tried. When your backend is wired, we can auto-tag by request type and severity.

Demo: connect action + API keys before production.

Front-end demo only — wire this form to your helpdesk or serverless endpoint.

Back to home