| name | groq-deploy-integration |
| description | Deploy Groq integrations to Vercel, Cloud Run, and containerized platforms.
Use when deploying Groq-powered applications to production,
configuring platform-specific secrets, or setting up deployment pipelines.
Trigger with phrases like "deploy groq", "groq Vercel",
"groq production deploy", "groq Cloud Run", "groq Docker".
|
| allowed-tools | Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*) |
| version | 1.11.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","groq","deployment"] |
| compatibility | Designed for Claude Code |
Groq Deploy Integration
Overview
Deploy applications using Groq's inference API to Vercel Edge, Cloud Run, Docker, and other platforms. Groq's sub-200ms latency makes it ideal for edge deployments and real-time applications.
This SKILL.md is the high-level workflow. Every platform recipe — full source for the Vercel Edge Function, Dockerfile, Cloud Run command, Express health-check server, and Vercel AI SDK handler — lives verbatim in references/implementation.md. End-to-end walkthroughs that chain those recipes are in references/examples.md.
Prerequisites
- Groq API key stored in
GROQ_API_KEY
- Application using
groq-sdk (or @ai-sdk/groq for the Vercel AI SDK path)
- Platform CLI installed (
vercel, docker, or gcloud)
Instructions
Pick the deployment target, then follow its recipe in references/implementation.md.
- Write the handler. For Vercel Edge, create
app/api/chat/route.ts with export const runtime = "edge" and stream Server-Sent Events when the request asks for them; otherwise return a JSON completion. See Step 1 in references/implementation.md.
- Store the secret. Never bake
GROQ_API_KEY into an image. Use the platform's secret store — see the Environment Variable Config table below.
- Deploy.
vercel --prod for Vercel (Step 2); build the Dockerfile (Step 3) and gcloud run deploy --source . for Cloud Run (Step 4) — all in references/implementation.md.
- The Express server (Step 5) exposes that pings Groq with the cheapest model (, ) and reports latency, so orchestrators can probe liveness cheaply.
