FLUIDFLUID
  • Introduction
  • Quickstart
  • Why FLUID
  • FAQ
  • What FLUID Is
  • Core Principles
  • Agentic-Native Layer
  • FLUID vs ODCS / ODPS
  • Reference Implementation
  • Anatomy
  • Cheatsheet
  • Minimal Contract
  • Specification
  • Versions
  • Changelog
  • JSON Schema 0.7.5 (stable) ↗
  • Reference 0.7.5 (HTML) ↗
  • Preview: 0.7.6
Examples
How-to
What's New
Deck
  • Contributing
  • Governance ↗
  • Conformance Corpus ↗
  • Vision
GitHub
GitHub
  • Introduction
  • Quickstart
  • Why FLUID
  • FAQ
  • What FLUID Is
  • Core Principles
  • Agentic-Native Layer
  • FLUID vs ODCS / ODPS
  • Reference Implementation
  • Anatomy
  • Cheatsheet
  • Minimal Contract
  • Specification
  • Versions
  • Changelog
  • JSON Schema 0.7.5 (stable) ↗
  • Reference 0.7.5 (HTML) ↗
  • Preview: 0.7.6
Examples
How-to
What's New
Deck
  • Contributing
  • Governance ↗
  • Conformance Corpus ↗
  • Vision
GitHub
GitHub

FLUID

One declarative contract for trustworthy, governable, agent-ready data products.

Get Started →Minimal ContractFLUID vs ODCS / ODPS

Contract-First

One .fluid.yml is the source of truth — schema, quality, build, lineage, governance. Version-controlled and schema-validated.

Agentic-Native

agentPolicy, sovereignty, and semantics give LLM agents machine-readable answers to PII, allowed-use, metric, and residency questions — and an MCP gateway can enforce them on every read.

Operational Superset

Covers build, orchestration and source-aligned acquisition alongside the data contract and its governance.

Interoperable

Compiles to Bitol ODPS + ODCS via the forge-cli reference implementation for DataHub / OpenMetadata / Datamesh Manager catalog interop.

Federated by Design

Built for Data Mesh — decentralized ownership, globally unique product ids, one unified fabric.

Open & Apache 2.0-Licensed

An open specification under the Apache License 2.0, with a public conformance corpus and no CLA.

Your agents are only as trustworthy as the data products they consume.

FLUID is one YAML file that describes a data product end to end — schema, build, orchestration, agentic governance, sovereignty, and semantics. Write it once; validate it, compile it, and deploy it anywhere.

The shape of a contract

fluidVersion: "0.7.5"
kind: DataProduct
id: demo.bronze.hello_world
name: Hello World
metadata:
  owner:
    team: data-platform
exposes:
  - exposeId: hello
    kind: table
    contract:
      schema:
        - name: id
          type: STRING
          required: true
    binding:
      platform: local
      format: parquet
      location:
        path: ./hello.parquet

→ Build it up step by step in FLUID by Example.

Where to go next

  • Guide — what FLUID is, the quickstart, and the FAQ.
  • Concepts — the agentic-native layer and how FLUID compares to ODCS / ODPS.
  • Schema Reference — every top-level block, a cheatsheet, and the full specification.
  • What's New in 0.7.5 — the latest stable version: streaming Kafka → Iceberg sink, Confluent Cloud Tableflow, and a pgvector output port.
  • 0.7.6 (preview) — packaging modes, declared consumers, cross-mesh pins; opt-in, and still subject to change.
  • See the deck — the FLUID story in slides.
  • Contributing & governance — how the standard is maintained, and how to take part.
Licensed under the Apache License 2.0 | Copyright 2025 The FLUID Authors