Help center and support
Most questions are solved in a few minutes with the self-service guides. When that is not enough, this page shows how to reach the Zenifra team and what to send to get a fast answer.
1. Start with self-service
| Situation | Where to look |
|---|---|
| Build failed | Build Logs and build failures |
| App not responding | Quick diagnosis |
| Database connection error | Connection problems |
| Domain or HTTPS | Custom domain |
| Billing question | Payments and Manage payments |
| Setting up a framework | Framework guides |
| Unknown term | Glossary |
| Quick question | FAQ |
2. Check platform status
Before digging into your app, check status.zenifra.com. If there is an ongoing incident, the page shows the affected components and updates from the team.
3. Contact support
Email [email protected] from the address on your Zenifra account.
What to include
The more context, the faster the answer. Copy this template:
Subject: [Project <project ID>] <one-sentence summary of the problem>
Organization: <organization name>
Project: <project name and ID>
Affected URL: <https://...>
What happened:
<describe the observed behavior>
What was expected:
<describe the expected behavior>
When it started (date, time, and time zone):
<e.g. 2026-10-03 14:20 (UTC-3)>
What changed before the problem:
<deploy, variable, domain, plan...>
What I already tried:
<steps taken>
Relevant log lines:
<paste the error lines, without secrets>The project ID appears on the project page in the console and in the output of zenifra projects in the CLI.
Never send secrets
The Zenifra team never asks for passwords, API Keys, or variable values. Before pasting logs, remove tokens, passwords, and customers' personal data.
4. Security
Found a vulnerability or suspect unauthorized access to your account? See Security and, if needed, immediately revoke the affected API Keys.
Documentation feedback
Found something wrong, outdated, or hard to follow? Use the feedback button in the corner of the page: the message goes straight to the team with the page address. Suggestions for new guides are welcome too.
Next steps
Last updated on