Aiven for Apache Kafka BYOC
Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Enable BYOC with Aiven, apply the provider-specific Terraform template, then provision Classic Kafka through the Aiven Console or CLI.
External vendor control plane
Runs in
Documented customer environment
Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Vendor or service partner
Aiven manages provisioning and maintenance. The customer provides the cloud account, network configuration, IAM, quotas, and backup storage access.
Deployment boundaries by provider
- AWS: Customer cloud account · Vendor / partner-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Aiven custom cloud on AWS ↗ · Source checked 2026-11-21
- Azure: Customer cloud account · Vendor / partner-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Aiven custom cloud on Azure ↗ · Source checked 2026-11-21
- Google Cloud: Customer cloud account · Vendor / partner-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Aiven custom cloud on Google Cloud ↗ · Source checked 2026-11-21
Aiven operates and maintains Kafka in the customer's custom cloud. Its separate management plane provisions and monitors the service through delegated access; the customer supplies cloud-account, network and policy prerequisites.
Operating responsibility source ↗ · Checked 2026-11-21
BYOC networking and control plane ↗
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Enable BYOC with Aiven, apply the provider-specific Terraform template, then provision Classic Kafka through the Aiven Console or CLI. |
|---|---|
| Infrastructure | Servers / containers Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion. |
| Licensing model | Commercial Only Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately. |
| License | Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Organization administrators can configure a SAML identity provider and verified domains for Aiven Console users. BYOC Kafka is provisioned through that same Aiven organization and Console. This authenticates the vendor-hosted management plane; Kafka client authentication is a separate configuration.
Aiven organization / Console identity for the managed BYOC service, not Kafka protocol clients. · Source ↗ · Kafka BYOC Console prerequisites ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
AvailableEvidence and scope for Deployment artifact / IaC
After BYOC approval, Aiven generates a customer-specific Terraform template in Console or CLI. The customer downloads and applies it to prepare the cloud account and delegated access, then provisions Kafka in the custom cloud. This is account-specific managed-service onboarding, not a public standalone self-managed Kafka installer.
AWS custom-cloud Terraform onboarding; obtain and review the generated template and permissions. · Source ↗ · Google Cloud generated Terraform onboarding ↗ · Azure custom-cloud onboarding ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The Kafka BYOC guide requires a fixed Classic Kafka plan and gives business-4 as a CLI example, but does not establish a quantitative minimum topology for the customer's provider, region and workload. Diskless topics have separate eligible plans and can add a PostgreSQL service. Obtain broker counts, instance resources, storage and availability-zone design from Aiven; the example plan name is not a sizing guarantee.
Managed Kafka BYOC sizing unresolved; do not substitute Aiven-hosted Free/Developer plans. · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
BYOC is a bespoke commercial managed service requiring an Aiven commitment and Advanced or Premium support. Pricing depends on the agreement. Aiven bills managed-service fees separately from the customer's cloud infrastructure and network traffic; standard all-inclusive Aiven Cloud rates do not establish BYOC charges.
Commercial Kafka BYOC eligibility and separate billing; request the supported plan and a quote. · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
Classic Kafka uses fixed service plans. Diskless topics require enablement and an eligible custom cloud and plan. Aiven documents limited OCI access for its wider BYOC program. Confirm product and region eligibility. Metrics and logs reach Aiven, and controlled support access is documented. Agree how to migrate topics and remove delegated access before exit.
Category fit
- Streaming
- Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.
Compare within Streaming
- Apache KafkaDistributed event streaming platform for durable publication, storage and consumption of event streams.
- Google Cloud
- Apache PulsarDistributed publish-subscribe messaging and streaming platform for persistent event workloads.
- AWS
- Cloudera on CloudCloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
- AWS
- Azure
- Google Cloud
- Confluent Platform Self-ManagedSelf-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.
- AWS
- Azure
- Google Cloud
- Redpanda BYOCManaged Kafka-compatible streaming in your cloud account.
- AWS
- Azure
- Google Cloud
These products address related workflows; read their category-fit notes before comparing scope. See all of Streaming →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Kafka BYOC provisioning ↗aiven.io
- Private networking and vendor access ↗aiven.io
- BYOC eligibility and billing ↗aiven.io
- Shared responsibility matrix ↗aiven.io
- Aiven custom cloud on AWS ↗aiven.io
- Aiven custom cloud on Azure ↗aiven.io
- Aiven custom cloud on Google Cloud ↗aiven.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Aiven custom cloud on AWS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The customer applies a Terraform template in its AWS account and grants Aiven permissions through an IAM role.
- Aiven custom cloud on Azure ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The customer sets up an Azure custom cloud in its subscription before provisioning Kafka.
- Aiven custom cloud on Google Cloud ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The customer sets up a Google Cloud custom cloud in its project before provisioning Kafka.
- Aiven custom cloud on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked