Support
How can we help?
Describe the problem, keep your reference and get back to the engineering.
Create a support case
Your email is used to contact you about this case. The subject helps route it and is stored as unencrypted case metadata; keep both the subject and message free of secrets. Read how support data is handled.
Do not submit card numbers, API keys, passwords, activation claims, identity documents or third-party confidential RTL. There is no file upload: describe the problem and ask before transferring sensitive material.
What happens after submission?
After you submit
A successful response displays a case identifier. Save it: the form records your message in the support queue but does not send an automatic confirmation email. Operator triage and any reply are separate; submission does not guarantee immediate resolution or a particular response time.
If delivery cannot be confirmed, your draft stays in the form. Wait before retrying to avoid duplicate cases. If you already have a case identifier, include it when following up rather than creating several unrelated reports.
Try this first
Find help by topic
Choose a category for a short, safe next step. Nothing is sent when you open these guides.
Installation or startup
- Match the package to your OS and CPU architecture, then compare its checksum and signature.
- Keep Linux runtime files together and launch from a graphical desktop session. On Windows, start from the installed application.
- If a signature check fails, stop; do not bypass the warning.
Installation guide · Guided setup
Still stuck? Include package filename, application version, OS, architecture and the exact redacted error in your case.
Create an installation case ↓AI connection or approval
- Check the supported external CLI setup; the model is not bundled with the application.
- On Windows, follow the supported isolated WSL connection route.
- Review the selected context and approval step before execution. Never paste API keys or login tokens here.
AI setup and approval guide · Context boundaries
Include the connection stage and a redacted error, not your conversation or confidential source.
Create an AI connection case ↓Missing tools or engineering checks
- Distinguish a tool-not-found diagnostic from a failing design check.
- Confirm the configured simulator, synthesis or formal tool and its supported version.
- Try the small public first-project example before sharing a private design.
Engineering tool setup · Reproducible first project
Include the selected tool, version, command stage and redacted diagnostic. Do not send proprietary RTL.
Create an engineering tools case ↓Payment, activation or refund
- Downloading does not buy or activate a subscription.
- Follow the activation instructions for the purchase you made. Do not share activation claims.
- For billing help, use the Stripe receipt identifier, never card details.
Payment and activation guide · Refund policy
Create a billing case ↓Project recovery or an unexpected change
- Preserve the current project and available backups before experimenting.
- Record which operation ran and which files were affected. Avoid repeated retries that might overwrite evidence.
- Follow the recovery guide; do not upload raw crash dumps or private source.
Safe recovery and diagnostic collection · Application rollback
Create a recovery case ↓Accessibility, privacy or security
For an accessibility issue, include the page URL, browser and assistive technology if relevant. No medical information is needed.
For a privacy request, identify the record and requested action. For a vulnerability, provide only a minimal safe reproduction.
Privacy procedure · Security reporting
Create a case ↓