Real engineers, real answers, no escalation theater.
Trueno is in early access. Support is best-effort and routed directly to engineering — there is no tiered queue, no auto-responder, and no fake SLA.
Email us
The fastest path to a real engineer is email. Include the checklist on the right and we'll triage from there.
info@gigant.techWhat to include
A reply takes minutes when the email already has enough context. Five short lines is usually enough.
- Workspace id
Available in the URL when you're signed in (org_…). Helps us scope the query to your data.
- Time range
Approximate UTC timestamp of when you saw the issue. Helps correlate with server logs.
- Expected vs actual
One line each. 'I clicked X, expected Y, got Z' is the fastest path to a fix.
- Affected AWS account id (last 4 digits)
We don't need the full 12-digit account id — last 4 is enough to scope.
- Screenshot or error message
If the UI shows an error, a screenshot or the literal text helps. Network-tab payloads if it's an API failure.
What to expect
Best-effort, business hours
We respond from a real engineer, usually within a business day during early access. No automated triage, no escalation tiers.
No published SLA
We don't sell support tiers and we don't promise response times we can't meet. Once we have an enterprise contract that needs one, we'll publish it.
Severity matters
If a scan is silently failing or an account looks disconnected when it shouldn't be, lead with that and we'll prioritize.
Reporting a security issue
Security reports go to the same address with the subject line [security]. The security page documents the access model + revocation flow.