Support
Which channel to use, what each plan includes, and what to send so we can answer on the first reply.
2 мин читать·Уровень ссылка·Пересмотрено 23 окт. 2026 г.
Эта страница пока недоступна на вашем языке. Оно показано на английском языке.
Этот текст на английском языке был создан автоматически на основе французского оригинала и еще не проверялся.
#
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.
Последнее обновление · 23 окт. 2026 г.