Confluent Software / SaaS global

Notion

Enterprise Knowledge Search · Real-time Analytics

Notion's legacy event-logging architecture could not scale with rapid user growth, online indexing, AI features, and multi-destination integrations without driving up tooling costs and distracting a lean engineering team with infrastructure work.

100% of their time
just over a year
over 100 million users
tripled its productivity

Reported impact

Business outcome

Notion gained a scalable real-time AI backbone, tripled productivity, lowered operations cost, and freed the data platform team to spend all of its time on new features rather than Kafka operations.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Notion moved to a fully managed event-driven architecture on Confluent Cloud to make product events available in real time for analytics, integrations, and Notion AI. The platform replaces a brittle pattern of third-party tools and custom connectors with one managed Kafka backbone that scales clusters up and down, expands retention on demand, and streams changes directly into destinations such as Amazon S3, Snowflake, and PostgreSQL. Schema Registry and stream processing help the team enrich and govern events, while the AWS-native deployment fits cleanly into Notion's existing infrastructure. The most important use case is AI: as users update pages and workspace content, Confluent immediately synchronizes those changes into Notion's vector database so RAG search and content-generation workflows always use current context. By offloading Kafka operations, the engineering team can focus fully on new product features instead of running infrastructure.

Data flow

Workspace and application events stream through Confluent Cloud, flow into destinations like Amazon S3 and Snowflake, and are synchronized into Notion's vector database so RAG search, content generation, and connected-app integrations use current workspace context.

Solution architecture

4 components · 3 layers
  1. Storage
    • Amazon S3 Receives real-time event streams for storage and analytics use cases.
    • Snowflake Stores and analyzes streamed event data for downstream decision-making and product workflows.
  2. Governance
    • Schema Registry Supports real-time capture, enrichment, and governance of user events.
  3. Uncategorized
    • Confluent Cloud Acts as Notion's managed event backbone for analytics, integrations, and AI synchronization.

Architecture clues

  • Notion keeps its Kafka backbone on AWS and uses fully managed connectors to move data into storage and application systems.
  • The engineering team is evaluating additional Confluent features such as managed Flink and autoscaling on top of the current event-driven design.
  • The streaming platform keeps a vector database synchronized in real time for RAG search and generation.

Evidence from the source

"Faster Innovation: With infrastructure management and Kafka maintenance offloaded to Confluent, Notion's data platform team can now dedicate 100% of their time to bringing new features to market faster."
"The Confluent data streaming platform enables us to move at the scale of Notion, meaning that it can process the real-time messaging of over 100 million users generating many, many pages per day."
"With its powerful, fully managed connectors, we effortlessly stream data into destinations like Amazon S3, making real-time event logging scalable and efficient."
"With the Confluent data streaming platform as the backbone of Notion AI, Notion can ensure that changes made within the application are instantly reflected in its vector database for RAG."
Transparency Evidence & methodology 90/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Confluent

    Notion customer story

    First-party
    https://www.confluent.io/customers/notion/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived May 13, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 11, 2026 · Confluent · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.