Community Question Responder
Thoughtful drafted replies for community channels. Free, BYOK, your infrastructure.
What this is: a deployable tool that turns slow, half-answered community channels into a queue of vendor-quality drafts you approve in one click.
What you do here: clone the repo into your own GitHub, deploy to your own Vercel, drop in your own API keys, walk a setup wizard. No account on this site. No hosted version we control.
Why it matters: CQR is the proof-of-shape for the BYOK Factory methodology. Free with your keys; the studio comes into your dev shop only if you want the substrate installed in-house.
The BYOK form is four fields, then a one-click Vercel deploy that prompts for every key during setup. Every key is yours; no CAS-owned fallback.
The problem
Vendor community queues sit unanswered for days; meanwhile, third-party answers get moderated out. Both sides need a tool the channel admin can run themselves.
Polls a community Slack or Discord, classifies incoming questions, retrieves from a vendor-specific knowledge base, drafts a high-quality reply in the operator's voice, holds it for one-click approval, posts on approval. Two deployment modes: customer-self-serve (point it at any vendor's public surfaces, drafts for you without posting) or vendor-self-deploy (run it in your own community channel, your team approves drafts). One codebase. Same architecture. BYOK across every key — Anthropic, Supabase, Slack, ElevenLabs, OpenAI, Resend. No CAS-owned fallback.
Two deployment modes. One codebase.
Same architecture. Pick the one that matches who you are.
Customer self-serve
You operate inside someone else's community as a third party. CQR points at a vendor's public surfaces, drafts replies you can post or share. You stay the voice; the vendor never sees an automated bot.
- Drafts only — you approve and post in your own client.
- No bot account in the vendor channel.
- Knowledge base scoped to a single vendor's public docs.
Vendor self-deploy
You operate inside your own community as the vendor. CQR runs as a bot inside your Slack or Discord, drafts replies, holds for approval by your team, posts on the vendor account.
- Bot posts on the vendor account after approval.
- Team-level approval queue.
- Knowledge base scoped to your own product docs.
Demo
Walkthrough of the approval queue and a real draft posting cycle.
Demo video ships with the public release.
Until then, the GitHub README has setup screenshots and the doctrine gist explains the approach.
Keys you provide
No managed-for-you secret. Every credential below is one you create on the vendor's site and paste into the Vercel deploy flow.
- ANTHROPIC_API_KEY (or OPENROUTER_API_KEY)
- OPENAI_API_KEY (embeddings)
- SUPABASE (URL + anon + service-role)
- SLACK_BOT_TOKEN + SLACK_SIGNING_SECRET
- RESEND_API_KEY
- ELEVENLABS_API_KEY (voice agent — auto-provisions agent_id)
Voice agent built in
CQR ships with an ElevenLabs Conversational AI agent — voice-capture-a-learning. Operators record a one-line lesson into the approval queue while walking between tasks. The agent is provisioned via the vendor's API on first run; your ElevenLabs key, your agent.
The methodology
CQR is the first artifact of BYOK Factory — a methodology for shipping BYOK-first AI products that ride on the user's keys, infrastructure, and control. Tools below describe the doctrine and the engagement model.
- README on GitHub
- Doctrine gist · published with public ship
- Factory Floor essay #1 · published with public ship
- Studio-in-residence engagements
Ready to run it on your own infrastructure?
Take the repo, deploy with your keys, walk the setup wizard. If you want help installing the BYOK Factory substrate inside your dev shop, that's the engagement path.