Support
Get Help
Start with the self-serve options below; they resolve most issues faster than waiting on a reply. If you're still stuck, email us directly.
Self-serve
Run the doctor first
Most local issues (a wedged gate, an orphaned process, a stale loopback token) are fixed by the built-in self-repair:
mergen-server doctor --fix
FAQ
How the gate works, what it blocks, latency, privacy, plans, and how it differs from monitoring tools.
Read the FAQ →Troubleshooting
Common failure modes: hook not firing, gate unreachable, HITL buttons rejected, and how to recover each.
Read the guide →System status
Check whether an issue is on Mergen's side (website, cloud API, or HITL delivery) before you write in.
View status →Contact a human
Email omer@mergen.app, and include your plan, the command or tool call involved, and (if you have it) the output of mergen-server doctor. For bugs or feature requests, open an issue on GitHub.
Response times by plan
Security enforcement itself never depends on plan. Plan only changes how fast a human gets back to you.