Ticket Relay
Discord support tickets, filed as GitHub issues.
Node.js 24 · TypeScript · Fastify · SQLite · Discord Interactions · GitHub Apps
Members submit tickets from a panel in Discord. Each ticket is routed to the right repository and filed by a GitHub App. Reporters never need a GitHub account.
Features
Discord tickets
- Discord-native: members open tickets from a panel in your server and get a private confirmation with the issue link. No GitHub account needed.
- Ticket types and forms: members pick a type (e.g. Bug report, Feature request); each adds its GitHub label and a
[Bug]title prefix. Each type has its own Discord form with short-answer, paragraph and file-upload questions; answers appear as headings in the issue. - Screenshots: members attach PNG or JPG images (up to 10 MB per ticket). They're stored on your server with location data removed and embedded in the issue.
- Inbox: every ticket with its status, triage and GitHub link; retry, link an existing issue or close, with search and filters.
- Spam and duplicates: a per-member rate limit and duplicate window; a ticket is never filed twice, even when GitHub's reply is unclear.
- Files: see what's stored, clean up files of closed or spam tickets by rule (or automatically once a day), and set a storage limit.
Tools
- GitHub issues: search every issue, open and closed, across your connected repositories, including the ones opened directly on GitHub. Kept up to date every 2 minutes, no webhooks needed.
- AI triage (optional): Claude flags priority, duplicates, regressions, spam and more, and sorts tickets with your own label groups. Each action can be off, a suggestion, or automatic above a confidence threshold, with separate settings for issues opened directly on GitHub.
- AI triage › Review lists everything with suggestions waiting, from Discord tickets and GitHub issues. Every ticket shows its triage state (To review, Partly applied, Applied…), and suggestions say exactly what applying them does.
- Apply or dismiss in bulk, e.g. all duplicates at 80%+ confidence.
- Re-run triage on older tickets and compare settings before applying anything.
- AI triage › Activity shows what it's doing live, with a log kept 90 days.
- It runs in its own worker with a monthly limit and keeps GitHub API headroom for filing, so filing never depends on it.
- If Claude stops (out of credits, a rejected key, the monthly limit), every page shows an alert until it's fixed. Out of credits, it checks again every 5 minutes and carries on by itself.
- Contributor roles: a second panel where members sign in with GitHub and get a role based on their merged PRs or commits across all your apps, e.g. Junior Contributor at 1, Contributor at 10.
- Server health: processes, memory, disk, queues, GitHub API usage and alerts, with a Dev mode so restarts while you deploy aren't counted as crashes.
Team
- Roles: owners, admins and moderators; several workspaces on one install.
- Moderators: start with the tickets inbox and contributor verifications, view only. Admins give each one no access, view or edit on every page of every tool (tickets, issues, AI triage, contributor roles, Apps & repositories, server health), a whole tool at once or page by page.
Reliable and secure
- Duplicate and rate-limit protection, retries, and queues that survive restarts.
- Credentials stay on the server; stored tokens, the Claude key and ticket text are encrypted.
Screenshots
Overview: tickets needing attention, stats for each tool and the latest tickets.
Quick start
npm install
cp .env.example .env # PUBLIC_URL, ENCRYPTION_KEY
npm run dev # http://localhost:3000
Set DEV_LOGIN=true to use the console locally without Discord credentials.
Self-hosting
One host, PM2 and a TLS reverse proxy. No external database: state is a single SQLite file. Serverless platforms such as Vercel are not supported.
npm ci && npm run build
cp .env.example .env # PUBLIC_URL, ENCRYPTION_KEY, provider credentials
pm2 start ecosystem.config.cjs # web (1) + queue workers (2) + triage (1); migrations run on boot
pm2 save && pm2 startup
Then:
- Proxy HTTPS to port
3000(setHOST=127.0.0.1so the port isn't public). - Register the Discord application and the GitHub App: docs/PROVIDER_SETUP.md.
- Open
PUBLIC_URL, sign in with Discord and follow the setup steps.
Processes, operations, backups and scaling: docs/DEPLOYMENT.md.
Configuration
| Variable | Description |
|---|---|
DATABASE_PATH |
SQLite file (default ./data/ticket-relay.db) |
FILES_DIR |
Files attached to tickets (default ./data/files, next to the database) |
PUBLIC_URL |
Public HTTPS origin |
ENCRYPTION_KEY |
openssl rand -base64 32; keep it stable |
DISCORD_* |
APPLICATION_ID, PUBLIC_KEY, CLIENT_SECRET, BOT_TOKEN |
GITHUB_* |
APP_ID, APP_SLUG, CLIENT_ID, CLIENT_SECRET, optional WEBHOOK_SECRET |
GITHUB_APP_PRIVATE_KEY_FILE |
./secrets/sec.pem (git-ignored; see secrets/) |
PLATFORM_ADMIN_DISCORD_IDS |
Discord user IDs allowed to create workspaces |
ANTHROPIC_API_KEY |
Optional fallback Claude key for AI triage; workspaces normally add their own in Settings |
Optional variables are listed in .env.example. Everything else is configured
in the console.
Scripts
| Command | |
|---|---|
npm run dev |
Dev server with reload |
npm run build · npm start |
Production build and run |
npm run start:worker |
Queue worker process |
npm run start:triage |
Triage and issue-sync worker |
npm run migrate |
Apply migrations (also runs on boot) |
npm run typecheck |
Type-check source and tests |
npm test |
Test suite (self-contained; uses a temporary SQLite file) |
Docs
- Provider setup: Discord application and GitHub App registration
- Deployment: runtime, scaling, retention, operations
- Architecture: ticket lifecycle, endpoints, schema, security
Scope
Not included: GitHub ↔ Discord comment sync, status updates to members after filing (the console shows each issue's live state), private ticket channels.


