Send a message and we'll get back to you. Best for multi-tenant deployment questions, tenant-isolation and quota design, sandbox configuration, migration from single-tenant OpenClaw, and paid support or integration inquiries. For quick community questions, GitHub issues and Discord (linked below) are often faster.
Thanks — your message is on its way. We'll get back to you soon.
Sorry, something went wrong. Please try again or email us directly at contact@neullabs.com.
Other ways to reach us
GitHub issues — the default
For bug reports, feature requests, and questions that might help other users, open an issue at https://github.com/neul-labs/openclawmu/issues ↗. Issues are read daily by the maintainer.
Discord — for community chat
The OpenClaw Discord (shared with upstream) is at https://discord.gg/clawd ↗. Good for quick "how do I…" questions, sharing what you're building, and getting input from other operators.
- General & paid support: contact@neullabs.com
- Security disclosures: security@neullabs.com
LinkedIn — for direct outreach
Reach the maintainer directly on LinkedIn ↗. Best for partnership conversations, press, or hiring within the Neul Labs ecosystem.
Response times
- Security issues — acknowledged within 48 hours, fix or mitigation within 14 days.
- GitHub issues — read daily; responses within 1–3 days.
- Email / contact form — within a few business days, longer for non-urgent items.
- Discord — community-paced; the maintainer drops in regularly.