Developer preview · Best effort

Support starts with a safe diagnostic boundary.

Strust is not generally available. This page states what can be supported today, what must stay out of email, and how to create a redacted diagnostic before asking for help.

Public release status

No Strust package is generally available yet. The download page is the authority for promoted platforms and supported public artifacts.

Developer-preview support

General product and installation coordination is best effort. The public email route is not yet verified; a signed design-partner agreement may define a protected route and narrower response commitment.

Evidence stays customer-controlled

Do not email source, raw fixtures, receipts, findings, credentials, or exploit details. Request a protected transfer path before sharing sensitive material.

Redacted support bundle

Inspect before you share.

strust doctor -c strust.toml \
  --support-bundle support.json --json

The bundle contains Strust/runtime versions and stable doctor check ids and statuses. It omits contract names and paths, commands, environment values, source, fixtures, baselines, receipts, reports, and credentials. Its SHA-256 detects accidental changes; it is not a publisher signature. Read the JSON yourself before sending it.

Non-sensitive coordination

Contact Strust without attaching customer evidence.

The general address below is listed for non-sensitive product coordination, but its domain mail routing has not yet been published and tested. Do not rely on it for a time-sensitive request. There is no public support SLA during the developer preview.