Deploy Community Question Responder on your own infrastructure.
What this is: a short form, then a one-click Vercel deploy that clones Community Question Responder into your own GitHub and stands it up on your own Vercel account. No hosted version we control.
What you do here: tell us who you are and what you're trying to do with it, then click through. The deploy walks you through every API key the product needs — every key is yours.
Why it matters: the BYOK Factory model only works if Community Question Responder is genuinely zero-marginal-cost for us. Your keys, your bills, your control. The form is so we can learn what you're using it for.
Every key is yours
Community Question Responder never proxies through a Corporate AI Solutions account at runtime. Every metered API call lands on your own vendor account.
- · 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)
Opinionated stack
The deploy is opinionated to GitHub + Vercel + Supabase. If your stack is different, the product is open source — fork and adapt — but the one-click deploy assumes this combination.
No support included
Free + BYOK means no SLA, no managed updates, no on-call. Pick the paid hosted option from the Community Question Responder marketplace page if you want a supported version. Or, if your team wants the substrate installed in-house, see studio-in-residence engagements.
A few details before the deploy
Four fields. We use this to follow up on how you got on with it — not to sell you anything.
Want the hosted version of Community Question Responder instead? Back to the product page for the paid path.