COMMUNITY

Build with TucDesk

Join engineers, security teams, and operators building on TucDesk. Get help, contribute, and shape the roadmap.

DISCORD

Real-time help and release discussion

#announcements

New releases, security notices, package updates, and migration reminders.

#general

Platform discussion, setup questions, and operational feedback.

#help

Installation, configuration, relay, dashboard, and agent debugging.

#showcase

Share production setups, self-hosted topology, and integrations.

#contributors

Development discussion, pull requests, RFCs, and docs work.

#security

Responsible disclosure coordination for invited reporters.

GITHUB DISCUSSIONS

Long-form RFCs and architecture

Use GitHub Discussions for longer-form questions, architecture proposals, and decisions that need searchable history.

Open GitHub Discussions →
CONTRIBUTING

How to contribute

Bug Reports

Open an issue with reproduction steps, platform info, TucDesk version, and relevant logs.

Feature Requests

Start with a discussion. Describe the use case and operational risk before proposing implementation.

Code Contributions

Fork the repository, open a pull request against main, include tests, docs, and a signed-off-by line.

Security Research

Email security@tucdesk.app. We follow coordinated disclosure with a 90-day timeline.

COMMUNITY STANDARDS

Be kind. Be specific. No spam.

TucDesk community spaces are for useful engineering discussion. Keep reports reproducible, avoid drive-by promotion, and treat security disclosures with care.