← Back to store

Support that helps you reach a working result

Start with the product documentation, then use the support assistant for common questions. If the issue involves billing, access, delivery, or a failed result, send the exact product name and the step that failed. Support follows the documented severity path; no unsupported uptime or response guarantee is implied.

Customer requestproduct + symptomDocumented answerFAQ + buyer docsEvidence or escalationlive status · human review
A support answer is grounded in published documentation and current service state; uncertain or sensitive cases go to a human.

Before purchase

Compare products, verify the intended workflow, and check the public pricing and product page.

View pricing · Browse products

After purchase

Use the buyer documentation and download instructions included with your product. Keep your receipt and order email available.

Contact support

Private AI and compute

For installation, workflow, or API questions, include your environment, product slug, and a safe description of the failure. Never send secrets or API keys.

Compute support · View operational evidence

Common questions

Is support automatic?

The support assistant handles common product questions and escalates cases that require a human. Do not paste credentials, private keys, or customer data.

What should I include?

Product name, operating system, relevant version, exact error, and the last successful step. Redact tokens, passwords, private URLs, and personal data.

Where are billing questions handled?

Billing and refunds are handled through the payment provider and the order details associated with your purchase. We can help identify the correct product/support path.

Open a support request