Support
VinTekh is in pilot. Support runs through three channels — pick whichever matches the urgency.
1. Operational issues (something broken)
Check the live status page first. If it shows a partial outage, you've already found the cause. For incidents not on the status page:
- Email support@vintekh.example.com with the URL you were on, the error message + the digest hash if you have one (it appears on the error page), and the approximate time.
- Customers on a paid plan get a Slack Connect channel. Use that for P0/P1.
2. Security-relevant reports
Disclosure goes to security@vintekh.example.com. We acknowledge in <24h, triage in 5 business days. We honour CVD with 90-day disclosure timing.
3. Sales / commercials
For pricing, contract terms, MAU plan changes: sales@vintekh.example.com
What to include in a bug report
- Your tenant id (visible at the bottom of every error page)
- The URL and time you saw the issue
- The error digest if shown (8-char hex)
- What you expected vs. what happened
- Whether it's blocking work for you right now
Response times (pilot)
| Severity | Acknowledgement | Resolution target |
|---|---|---|
| P0 (production down) | <30 min business hours | 4h |
| P1 (major feature broken) | <2h business hours | 1 business day |
| P2 (workaround exists) | <1 business day | 1 sprint |
| P3 (cosmetic, requests) | <5 business days | Roadmapped |
Once the pilot ends, the contractual SLA in the order form supersedes these targets. The values above are the pilot best-effort.
Browse docs
- Help home
- Getting started
- How VinTekh works
- Read-only model
- Connect a source
- Azure Reader SP
- AWS cross-account role
- GCP Workload Identity
- External ID & MAU
- SCIM 2.0 provisioning
- Investigate a finding
- Recommendations
- Service coverage
- Platform capabilities
- Troubleshooting
- Glossary
- REST API
- Admin guide
- Release notes
- Support