Get help with a CutCtx deployment.
For product, billing, licensing, or incident questions, contact the CutCtx team at hello@aoexl.com. Include enough context for investigation, while keeping credentials and sensitive customer data out of the message.
What to include
- CutCtx version and deployment mode (local, Docker, Kubernetes, or hosted control surfaces).
- UTC timestamp, request ID if available, client, provider, endpoint, and status code.
- A short description of the expected and observed behavior, plus safe reproduction steps.
- Redacted logs and recent configuration changes relevant to the issue.
Incident severity
Critical means data loss, credential exposure, a paid capability unavailable to all users, or a proxy outage without a working bypass. High means a supported client or provider path fails, recovery is degraded, or routing or billing evidence cannot be trusted. Medium and low issues have a workaround or are documentation and usability defects.
Credential safety
Never send provider keys, license keys, access tokens, full request bodies containing secrets, or unredacted customer data by email or chat. We do not publish response commitments on this page; any response target must be agreed in writing for the applicable engagement.
Commercial account help
For invoices, subscriptions, refunds, or license recovery, identify the account email and relevant invoice or order reference. See Manage license and the Refund policy for self-service paths.