Support
Which channel to use, what each plan includes, and what to send so we can answer on the first reply.
2分钟 读取·级别 参考·修改于 2026年10月23日
此页面尚不支持您的语言。它以英文显示。
该英文文本是根据法文原文自动生成的，尚未经过审查。
#
Channels
1. Channels by plan
| Plan | Channel | Availability commitment |
|---|---|---|
| Free | Community on Discord | Best effort (99.0%) |
| Pro | E-mail to support@aurabase.cloud | Reply within 24 business hours, 99.95% |
| Team | Priority support by e-mail | See your contract |
| Enterprise | 24/7 on-call, 15-minute response for a blocking incident (Sev-1) | 99.99% (Multi-AZ) |
There is no published response time for the community channel.
#
Details
2. What to send
- The
request_idof the failing call: it is in the body of every error (error.request_id). - The error
code(for exampleQUOTA_EXCEEDED) and the HTTP status. - The project URL (
https://<slug>.aurabase.cloud), never the keys. - The version of the SDK (
npm ls @aurabase/aurabase-js) and of the CLI (aura --version).
#
安全性
3. Security issues
Do not open a public message for a vulnerability. Follow the contact and the encryption key published in /security.txt.
#
状态
4. Status
The state of each service is on the status page.
最后更新· 2026年10月23日