How to get help

GitHub Issues

Public bug reports, feature requests, and questions. Most product issues are resolved here within 1 to 5 business days. Search existing issues before opening a new one. ERPClaw maintainers triage daily.

Best for: Best for: bug reports with reproducible steps, feature requests, questions answerable in async public discussion.

GitHub Discussions

Long-form architectural questions, integration patterns, customization help, and showcase. Community + maintainers participate. Slower than Discord but higher signal for design conversations.

Best for: Best for: 'how should I model this?' questions, integration design, sharing what you built.

Discord

Real-time chat with maintainers and the community. The fastest path for a quick question or a stuck-on-install moment. Active during US Pacific business hours; async coverage from international community.

Best for: Best for: quick questions, install help, real-time troubleshooting.

Email AvanSaber Inc.

Direct line to Nikhil (co-founder). Use this for confidential issues, business-relationship questions, or matters that don't fit a public channel. Response within 1-2 business days.

Best for: Best for: confidential questions, paid implementation interest, partnership inquiries.

Paid implementation services

AvanSaber Inc. offers paid implementation, migration, and ongoing-support engagements for teams that prefer managed help. Pricing scales with scope; typical engagements run 4-12 weeks elapsed. Email Nikhil to scope.

Best for: Best for: mid-market teams with a defined timeline who want a vendor on the hook.

What is the response time for an open-source ERP support question?

GitHub Issues: 1 to 5 business days for triage. Discord: same-business-day for active hours, longer for async. GitHub Discussions: variable, depending on question complexity. Email: 1 to 2 business days. There is no SLA on community-tier support; if your business requires guaranteed response times, email about a paid support contract.

Is community support enough for a real production deployment?

For most SMB-to-mid-market deployments, yes. ERPClaw is on the Stripe Marketplace with paying customers running real production books on community-tier support. The architectural advantages (immutable GL, 18 constitutional articles, 3,629 automated tests) reduce the support surface significantly compared to a SaaS where opaque vendor cloud issues require vendor cooperation. For Fortune 500 deployments with strict SLA requirements, paid support contracts are available.

Does ERPClaw offer 24/7 enterprise support?

Not as a default community-tier offering. Paid support contracts from AvanSaber Inc. can include 24/7 coverage; pricing scales with the SLA requested. For SMB-to-mid-market deployments, the typical setup is community-tier with optional paid support for specific incidents.

What about legal liability or warranty?

ERPClaw is provided under GPL v3 without warranty (standard open-source disclaimer). Paid implementation contracts from AvanSaber Inc. can include defined warranty terms for the implementation work; the underlying open-source software remains as-is. Most teams handle this the same way they handle Linux on production servers: open-source software plus optional paid support.

Where do I report a security vulnerability?

Email Nikhil directly at [email protected] with the details. We follow responsible disclosure: report privately, give us a reasonable window to fix, then coordinate public disclosure. We do not currently run a paid bug-bounty program but we credit security researchers in release notes.