Support center.

Get help with deployments, servers, monitoring alerts, access, billing, and API integrations.

Account and access

Deployment history, rollback targets, server status, monitoring charts, and Docker workflows.

Razorpay payment links, webhook records, invoices, subscription plans, and payment history.

Good context shortens triage time and keeps sensitive data out of tickets.

Organization name, project slug, environment, and affected deployment or server ID.
Exact timestamp, browser, operating system, and whether the issue happens on public domain or localhost.
Relevant invoice number, payment ID, or webhook event ID for billing issues.
Screenshots are useful, but never include passwords, API keys, SSH private keys, or webhook secrets.

Use severity to decide how quickly to escalate.

Critical: production deployments, login, billing, or monitoring are unavailable for an organization.
High: a core workflow is blocked but a manual workaround exists.
Medium: documentation, UI state, or non-production workflow has an issue.
Low: product feedback, roadmap requests, and non-urgent improvements.

Get help with deployments, servers, monitoring alerts, access, billing, and API integrations.

Deployment history, rollback targets, server status, monitoring charts, and Docker workflows.

Razorpay payment links, webhook records, invoices, subscription plans, and payment history.

Good context shortens triage time and keeps sensitive data out of tickets.

Organization name, project slug, environment, and affected deployment or server ID.
Exact timestamp, browser, operating system, and whether the issue happens on public domain or localhost.
Relevant invoice number, payment ID, or webhook event ID for billing issues.
Screenshots are useful, but never include passwords, API keys, SSH private keys, or webhook secrets.

Use severity to decide how quickly to escalate.

Critical: production deployments, login, billing, or monitoring are unavailable for an organization.
High: a core workflow is blocked but a manual workaround exists.
Medium: documentation, UI state, or non-production workflow has an issue.
Low: product feedback, roadmap requests, and non-urgent improvements.