Contact VibeInfra
One inbox, a public issue tracker, and a GitHub organization. Pick whichever fits — everything below reaches the people who build the platform.
Where to write
| What about | Where |
|---|---|
| General enquiries, support, billing, partnerships | [email protected] |
| API, SDK or MCP server questions and bug reports | GitHub issues, or the developer portal |
| A lab that is broken, mis-graded or unclear | Use the in-lab feedback control, or email [email protected] with the incident ID |
| Security vulnerability disclosure | [email protected] — see below |
| Privacy requests (access, correction, deletion) | [email protected] — see the privacy policy |
| Open-source repositories | github.com/vibeinfra |
We read everything that arrives at [email protected]. Please include the
incident ID and roughly when it happened if you are writing about a specific lab — it
is the difference between a same-day fix and a long thread.
Reporting a security issue
Email [email protected] with "security" in the subject line. Please include enough detail to reproduce the issue, and give us a reasonable window to ship a fix before disclosing publicly.
Note that lab sandboxes are intentionally broken systems: an injected fault inside a disposable practice container is the product working, not a vulnerability. What we want to hear about is anything affecting the platform itself — session handling, account isolation, sandbox escape, or access to another learner's data.
Who we are
VibeInfra operates vibeinfra.id
and the API at api.vibeinfra.id. Support is available in English and
Indonesian. More about the platform is on the
about page.