Ross ROSS = Recommend OSS · open-source software intelligence for agents

MaterializeInc/materialize

The live data layer for apps and AI agents. Create up-to-the-second views into your business, just using SQL observed · 2026-08-28

github.com/MaterializeInc/materialize · homepage · Rust · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

99/100

  • Activity 99
  • Release rhythm 99
  • Longevity 100

Flags: no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 6
  • age_days: 2749
  • days_rel: 6
  • days_push: 7
  • n_releases_24m: 14

Full methodology

Adoption not part of the score

6361 stars · 512 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Materialize is a streaming database that uses incremental computation to maintain always-fresh, strongly consistent SQL views over data from sources like PostgreSQL, MySQL, and Kafka. It is available as a managed cloud service, a self-managed Kubernetes deployment, and a Docker emulator, and exposes a PostgreSQL wire protocol plus an MCP server for AI agents.

Use cases

  • keep dashboards up to date with real-time data using SQL
  • serve fresh context to AI agents and RAG pipelines
  • offload expensive read queries from a production Postgres database
  • build an operational data store with CDC from multiple databases
  • power an online feature store for real-time ML inference
  • stream incrementally transformed data to downstream systems
  • build a live context graph of business data products

When to choose

  • you need sub-second, strongly consistent views over streaming data without building custom pipelines
  • your team knows SQL but not stream-processing frameworks like Flink
  • you want to serve operational analytics or ML features without overloading OLTP databases
  • you need CDC ingestion from Postgres, MySQL, SQL Server, or Kafka with incremental view maintenance

When to avoid

  • you only need batch analytics or scheduled ETL with no freshness requirement
  • you want a fully open-source license - Materialize is BSL, not OSI-approved
  • your workload fits comfortably in a traditional database with simple materialized views
  • you need a lightweight embedded database rather than a distributed streaming system

Facets

service · maturity active

database streaming etl rag mcp monitoring databases large-language-models analytics microservices cloud self-hosted rust stream-processing materialized-views incremental-computation cdc change-data-capture postgresql-wire-protocol kafka operational-data-store cqrs real-time-views bsl-license feature-store sql data-engineering streaming real-time docker kubernetes

10 sources

Member repositories

RepositoryRoleHealth v2
MaterializeInc/materializemain99

For agents

markdown · JSON · MCP: product_card(name="MaterializeInc/materialize")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem