Redpanda Cloud serverless Kafka-compatible cluster via the official Redpanda Terraform provider
Qovery creates it in your account with a third-party provider, using credentials you enter in the form, as a Blueprint service in one of your environments.
New to this? You don’t need to know Terraform or Kubernetes. Qovery sets up Redpanda Cloud in your account with the provider: you fill in a form, or paste the prompt below into your coding agent. The values it publishes, listed under Outputs, reach your other services as environment variables. Qovery tells you when a newer version of the Blueprint is available. Check the requirements in the Reference section before you start, and try it first in a development environment.
Open the environment, then New service › Blueprint.
Find Redpanda Cloud in the catalog and pick the major version.
Fill in the variables. Required ones are marked; the others use their defaults.
Create the service, and deploy it now or later.
List the catalog to get the latest tag, then create the service from it. qovery api signs the requests with your CLI session.
ORG_ID="REPLACE_WITH_ORGANIZATION_ID"ENV_ID="REPLACE_WITH_ENVIRONMENT_ID"qovery api "organization/$ORG_ID/blueprint/catalog" | jq '.. | objects | select(.name? == "redpanda-kafka")'cat > blueprint.json <<'EOF'{ "name": "redpanda-kafka", "tag": "EXTERNAL/redpanda-kafka/default/1.0.7", "icon": "app://qovery-console/redpanda", "variables": [ { "name": "redpanda_client_id", "value": "REPLACE_WITH_REDPANDA_CLIENT_ID" }, { "name": "redpanda_client_secret", "value": "REPLACE_WITH_REDPANDA_CLIENT_SECRET", "is_secret": true }, { "name": "cluster_name", "value": "REPLACE_WITH_CLUSTER_NAME" }, { "name": "serverless_region", "value": "REPLACE_WITH_SERVERLESS_REGION" } ], "spec_overrides": { "engine_version": "1.9.7" }}EOFBLUEPRINT_ID=$(qovery api "environment/$ENV_ID/blueprint" --method POST --input - < blueprint.json | jq -r .id)rm blueprint.json # it can hold secret valuesqovery api "blueprint/$BLUEPRINT_ID/deploy" --method POSTqovery api "blueprint/$BLUEPRINT_ID" # status of the latest deployment
Replace each REPLACE_WITH_ value. Add optional variables to variables the same way.
Paste this into Claude Code, Cursor, Codex or another coding agent with the Qovery agent skills installed (curl -fsSL https://skill.qovery.com/install.sh | bash).
Prompt
Add the Qovery Blueprint Redpanda Cloud (redpanda-kafka) to one of my Qovery environments and deploy it. Ask me for redpanda_client_id, redpanda_client_secret, cluster_name and serverless_region.Ask me before deploying to a production environment.Docs: https://www.qovery.com/docs/configuration/blueprints/redpanda-kafka.md
You don’t add any file to your repository. Qovery creates the Blueprint from the Console or the API.
Generated from qbm.yml at EXTERNAL/redpanda-kafka/default/1.0.7, the manifest the Console form is built from.
All 5 variables
Name
Type
Required
Default
Secret
Description
redpanda_client_id
string
Yes
Redpanda Cloud service-account client ID
redpanda_client_secret
string
Yes
Yes
Redpanda Cloud service-account client secret
resource_group_name
string
qovery
Redpanda resource group name to create
cluster_name
string
Yes
Max 60 chars
serverless_region
string
Yes
e.g. us-east-1, eu-central-1; must be one Redpanda Serverless supports.
Outputs become environment variables that other services in the environment can use. By default Qovery also creates an alias for each output, prefixed with the Blueprint’s name; see Aliases Qovery creates for outputs for the naming rules and the cases where no alias is created.
Secret variables and outputs are encrypted and masked in Qovery, but Terraform can also keep their values, and values derived from them, in its state. With the Qovery-managed state backend (the default), Qovery stores the state. If you use your own backend, protect it and keep state files out of version control.
From the Blueprint’s README.Provisions a Redpanda Cloudserverless Kafka-API-compatible cluster via the official redpanda-data/redpanda provider (~> 2.0).Resource chain: redpanda_resource_group → redpanda_serverless_cluster.
Paid SaaS (requires a Redpanda Cloud account + service account). Serverless is the low-friction path — Redpanda manages networking, no VPC resources.
serverless_region has no default: set a region Redpanda Serverless supports (invalid regions are rejected at apply).
To connect a client you also need SASL credentials — create a redpanda_user / ACL in the Redpanda console (or a follow-up Terraform step); this blueprint provisions the cluster and exposes kafka_seed_brokers + cluster_api_url.
