<a id="cloud-overview"></a>

# Confluent Cloud Overview

Confluent Cloud provides Apache Kafka® as a cloud service, so you no longer need to install,
upgrade, or patch Kafka server components. You also get access to a
[cloud-native design](../_glossary.md#term-Kora), which offers [Infinite Storage](../_glossary.md#term-Infinite-Storage),
[elastic scaling](../_glossary.md#term-Elastic-Confluent-Unit-for-Kafka-eCKU) and an uptime
guarantee. If you’re coming to Confluent Cloud from open source Kafka, you can use data
streaming features only available from Confluent, including tools for
monitoring and observability, a browser-based user interface, and
enterprise-grade security and data governance features.

Beyond [brokers](../_glossary.md#term-Kafka-broker) and [topics](../_glossary.md#term-topic), Confluent Cloud
provides these server processes for streaming data in a production
environment:

- Kafka Connect
- Schema Registry
- Confluent Cloud for Apache Flink®

Confluent Cloud integrates the components you need to stream data at scale. The
following sections describe Confluent Cloud’s key features and industry advantages.

## Cloud-native architecture with Kora

At the heart of Confluent Cloud is the Kora engine, a cloud-native re-architecture of
Kafka. Kora is designed to be elastic and cost-efficient, unlike open source
Kafka running directly on cloud infrastructure.

This architecture enables:

- **Elastic autoscaling**: The platform scales compute and storage
  independently and automatically, from zero to gigabytes per second (GBps) of
  throughput, so your cluster meets demand without over-provisioning.
- **Performance and latency**: The service delivers consistently low tail
  latencies for reliable delivery of mission-critical data.
- **Cost efficiency**: With a pay-as-you-go model and serverless clusters, you
  pay only for the resources you consume, without having to manually size and
  manage capacity.

## Complete integrated platform

Confluent Cloud includes the tools you need for data streaming, so you do not have to
build and manage a multi-vendor stack.

- **Fully managed connectors**: A library of pre-built, fully managed
  connectors simplifies data integration to and from popular databases, data
  lakes, and other services. This removes the operational overhead of
  running your own Kafka Connect clusters.
- **Stream processing**: Confluent Cloud for Apache Flink provides a cloud-native, serverless
  service for Flink that enables simple, scalable, and secure stream
  processing that integrates with Kafka. Your Kafka topics appear automatically
  as queryable Flink tables, with schemas and metadata attached by Confluent Cloud.
  Confluent Cloud for Apache Flink supports creating stream-processing applications by using
  Flink SQL, the [Flink Table API](../flink/reference/table-api.md#flink-table-api) (Java and
  Python), and custom [user-defined functions](../flink/concepts/user-defined-functions.md#flink-sql-udfs).
- **Data governance**: Built-in features like Schema Registry ensure data quality and compatibility
  across all your applications. You can centrally manage schemas and prevent
  data errors at the source.

## Enterprise-grade networking and security

Confluent Cloud provides security and networking features that help organizations meet
compliance and privacy requirements.

- **Data encryption**: All data is encrypted by default.
  - Data in motion is secured using Transport Layer Security (TLS) 1.2.
  - Data at rest is encrypted using native cloud provider services.
  - Bring Your Own Key (BYOK) lets you encrypt data at rest with your
    own encryption keys.
  - Client-Side Field Level Encryption (CSFLE) protects sensitive data at the application
    layer before it is written to Confluent Cloud.
- **Private networking**: To keep traffic off the public internet, Confluent Cloud
  offers multiple private networking options:
  - Virtual private cloud (VPC) or virtual network (VNet) peering: A direct
    network connection between your cloud network and your Confluent Cloud
    clusters.
  - AWS PrivateLink, Azure Private Link, and Google Cloud Private Service Connect:
    These provide a more secure, one-way, and simpler alternative to
    peering, allowing your applications to connect to Confluent Cloud privately
    without exposing the IP space of your network.
- **Identity and access management**: The platform includes identity
  controls, such as:
  - Role-based access control (RBAC): Granular permissions for users and
    service accounts to ensure that only authorized entities can perform
    specific actions on resources.
  - Auditing: Comprehensive audit logs track all user and application
    activity for security monitoring and compliance.

## Operational simplicity and reliability

Confluent Cloud offloads most of the operational burden of running and maintaining your
data streaming infrastructure.

- **Zero-downtime upgrades**: Confluent handles all software upgrades and
  patches automatically, so your clusters run the latest, most secure version
  without service disruption.
- **99.99% uptime service level agreement (SLA)**: The following cluster
  types provide a strong SLA for core Kafka operations, keeping your data
  streaming infrastructure highly available and resilient:
  - Standard
  - Enterprise
  - Freight
  - Dedicated
- **Expert support**: As the original creators of Kafka, Confluent provides
  24/7 expert support to help you solve complex Kafka issues.

## Related content

- [Confluent Cloud Free Trial](free-trial.md#free-trial)
- [Stream Governance on Confluent Cloud](../stream-governance/index.md#cloud-dg)
- [Manage Networking on Confluent Cloud](../networking/overview.md#cloud-networking)
- [Kafka Cluster Types in Confluent Cloud](../clusters/cluster-types.md#cloud-cluster-types)
- [Quick Start for Schema Management on Confluent Cloud](schema-registry.md#cloud-sr-config)
- [Use Confluent Documentation with AI Tools](docs-ai.md#agents-md)
- Confluent whitepaper:
  [Migrating from Kafka services to Confluent (PDF)](https://assets.confluent.io/m/2745775bbd1fa224/original/20240425-EB-Migrating_From_Kafka_To_Confluent.pdf)
