Community, forum, and support
Once you have a working fleet, you're past the official documentation and into the territory of "what are other operators doing?". This chapter points you at the support channels and community spaces that exist (and flags what's still being decided).
Time: 5 minutes to bookmark; ongoing to engage.
Official support
For account issues, billing questions, payout problems, or anything where you need a Zyra staffer to look at your account:
- Email: hello@getzyra.io — primary inbound channel today.
- In-app help. Help → Contact support opens a thread tied to your account so we already see your context.
[VERIFY: in-app support thread UI shape at GA] - Response time targets. Business hours response within one business day. Account-locking or payout-blocking issues prioritized.
For early-access testers, the response loop is tighter — flag yourself as early-access in the first message.
Community platform
The plan is a dedicated community space at launch. Whether that lands as Discord, a self-hosted forum, or a GitHub Discussions board is a founder decision still pending — see [VERIFY: community platform choice — Discord/Discourse/GH Discussions, founder decision pending].
What we know we want:
- A #getting-started channel/category for new operators.
- A #setups channel for sharing hardware, cooling, and schedule configurations.
- A #troubleshooting channel where operators help each other before involving support.
- An #announcements channel for agent updates, schedule changes, and incidents.
When the platform launches we'll publish the link on the device-owner index page.
Sharing setups and optimization tips
The community channel is the right place to share what's working: hardware specs, undervolt profiles, schedule shapes, noise mitigations, GPU driver versions. Be specific — "I get $X/month with this setup" is more useful than "this works great".
Don't share account-identifying information, payout amounts in a way that ties to your real identity if you'd rather not, or other operators' details.
Reporting bugs
Bugs in the agent or the dashboard:
- Reproduce-able bug. Email hello@getzyra.io with steps, your OS, agent version, and any logs. The agent log path is in Stage 2 chapter 1.
- Security issue. Don't post publicly. Email security@getzyra.io with details. We respond to security reports within one business day.
[VERIFY: security@ alias active] - Public bug tracker. A public GitHub issue board for the agent is on the roadmap; not live today.
[VERIFY: public GitHub issues — depends on public-repo flip decision]
Include in any bug report: device ID (from the dashboard URL), agent version, OS + version, what you expected vs what happened, and recent agent log lines.
Getting help from other operators
The community channel is the fastest path for "is this normal?" questions:
- "Capability score dropped 50 points overnight — what should I look at first?"
- "My GPU device idles for hours then catches a burst — is that expected?"
- "Anyone running 10+ devices in a residential location — how's your network setup?"
These get faster, more practical answers from operators than from support.
Public earnings leaderboards
A frequently-requested feature is a public leaderboard of top-earning operators. The current plan: opt-in only, anonymous by default. If we ship a leaderboard, it shows ranks and earning bands, not real names or precise dollar amounts, and you choose whether your row is on it at all. [VERIFY: leaderboard feature — privacy-by-default decided; UI not built yet]
Status page
Live operational status for the platform: scheduler health, payout processing, dashboard availability. Bookmark it for "is it me or is it Zyra?" moments. [VERIFY: status page URL — status.getzyra.io planned, not live yet]
What's next
Last reviewed: 2026-05-21