The declarative control plane for data engineering in the Agentic Era.
Documentation Β· Getting Started Β· FLUID Specification Β· The Book Β· Community
FLUID (Federated Layered Universal Instructional Declaration) is an open-source declarative framework for building, validating, and deploying data products across any cloud. You write a single YAML contract describing what your data product is β its schema, quality rules, access policies, and scheduling β and FLUID Forge compiles that into provider-specific infrastructure (BigQuery, Snowflake, AWS Glue, Athena, or local DuckDB) with full governance baked in.
Think of it as Terraform for data products: one contract, many clouds, zero boilerplate.
contract.fluid.yaml β fluid validate β fluid plan β fluid apply
(declare) (check) (preview) (deploy)
Data engineering is stuck in the dark ages of imperative spaghetti code. You want to ship data products fast, but compliance teams demand governance. You end up with Configuration Sprawl: .tf files for Terraform, schema.yml for dbt, .rego for OPA, and a web of Airflow DAGs.
FLUID Forge is the compiler that ends the chaos. You declare what your data product is. The CLI compiles that into a validated, deterministic execution plan across any supported cloud.
| π The Old Way (Imperative Chaos) | β¨ The FLUID Way (Declarative Order) |
|---|---|
| Weeks of boilerplate to wire up IaC, SQL, and DAGs. | Minutes to deploy. Just declare your intent and apply. |
| Vendor lock-in. Your DAGs only work on one cloud. | Provider-agnostic. Switch clouds by changing one line of YAML. |
| Governance as an afterthought. Manual compliance tickets. | Governance-as-Code. Policies compile to native IAM before deployment. |
| "Works on my machine." Broken production deploys. | Deterministic plans. See exactly what will change before it runs. |
| AI hallucinations. Agents don't understand your tables. | Semantic Truth. Built-in OSI semantics so LLMs query perfectly. |
Data engineering shouldn't require weeks of handwritten infrastructure code, bespoke CI/CD pipelines, and copy-pasted SQL.
What Terraform did for infrastructure, FLUID Forge does for data products.
# 1. Install the CLI
pip install fluid-forge
# 2. Validate your data product contract
fluid validate contract.fluid.yaml
# 3. See exactly what will happen
fluid plan contract.fluid.yaml
# 4. Deploy infrastructure, logic, and governance β instantly
fluid apply contract.fluid.yamlThat's it. You just deployed a versioned, governed, and orchestrated Data Product from a single YAML file.
Want to move from local to Google Cloud?
pip install "fluid-forge[gcp]"β changeplatform: localtoplatform: gcpβ runfluid apply. Done.
Choose your platform below for step-by-step instructions.
| Requirement | Version |
|---|---|
| Python | 3.9 or higher |
| pip | Latest recommended |
| Git | Any recent version |
π macOS
# Install Xcode Command Line Tools (includes Git and make)
xcode-select --install
# Or install Python & Git via Homebrew (recommended)
brew install python gitpython3 --version # Should print Python 3.9+git clone https://github.com/Agentics-Rising/forge-cli.git
cd forge-cli
# Create a virtual environment (recommended)
python3 -m venv .venv
source .venv/bin/activate
# Install in editable mode with the local provider
pip install --upgrade pip wheel
pip install -e ".[local]"fluid --version
fluid validate examples/01-hello-world/contract.fluid.yamlTip: You can also run the automated setup script:
chmod +x setup.sh && ./setup.sh
π§ Ubuntu / Debian Linux
sudo apt update
sudo apt install -y python3 python3-venv python3-pip git build-essentialpython3 --version # Should print Python 3.9+git clone https://github.com/Agentics-Rising/forge-cli.git
cd forge-cli
# Create a virtual environment (recommended)
python3 -m venv .venv
source .venv/bin/activate
# Install in editable mode with the local provider
pip install --upgrade pip wheel
pip install -e ".[local]"fluid --version
fluid validate examples/01-hello-world/contract.fluid.yamlTip: You can also run the automated setup script:
chmod +x setup.sh && ./setup.sh
πͺ Windows
Download and install Python 3.9+ from python.org.
Important: Check "Add Python to PATH" during installation.
Download and install Git from git-scm.com, or install via a package manager:
# Via winget
winget install Git.Git
# Or via Chocolatey
choco install gitpython --version # Should print Python 3.9+
git --versionPowerShell:
git clone https://github.com/Agentics-Rising/forge-cli.git
cd forge-cli
# Create a virtual environment (recommended)
python -m venv .venv
.venv\Scripts\Activate.ps1
# Install in editable mode with the local provider
pip install --upgrade pip wheel
pip install -e ".[local]"Command Prompt (cmd):
git clone https://github.com/Agentics-Rising/forge-cli.git
cd forge-cli
python -m venv .venv
.venv\Scripts\activate.bat
pip install --upgrade pip wheel
pip install -e ".[local]"fluid --version
fluid validate examples\01-hello-world\contract.fluid.yamlTip: You can also run the automated setup script:
- PowerShell:
.\setup.ps1- Command Prompt:
setup.bat
Once the base install is working, add cloud providers as needed:
pip install -e ".[gcp]" # + Google Cloud (BigQuery, GCS, Composer)
pip install -e ".[snowflake]" # + Snowflake
pip install -e ".[all]" # Everything (all providers + dev tools)Everything starts with contract.fluid.yaml β the single source of truth for your data product's entire lifecycle.
fluidVersion: "0.7.1"
kind: DataProduct
id: example.customer_360
name: Customer 360
domain: analytics
metadata:
layer: Gold
owner:
team: data-platform
email: platform@example.com
# 1. THE LOGIC β How is it built?
builds:
- id: transform_customer
pattern: embedded-logic
engine: sql
properties:
sql: |
SELECT user_id, email, LTV
FROM raw.users JOIN raw.orders USING (user_id)
# 2. THE INTERFACE β What does it output?
exposes:
- exposeId: customer_profiles
kind: table
binding:
platform: snowflake # β Change to 'gcp' or 'aws' instantly
format: snowflake_table
location:
database: PROD
schema: GOLD
table: CUST_360
contract:
schema:
- name: email
type: string
sensitivity: pii # β Triggers auto-masking/encryption
# 3. THE GOVERNANCE β Who (or what) can access it?
accessPolicy:
grants:
- principal: "group:marketing@example.com"
permissions: ["read"]
agentPolicy: # β Agentic Era Governance
allowedModels: ["gpt-4", "claude-3"]
allowedUseCases: ["analysis", "summarization"]Providers are the bridge between your declarative contract and your target execution environment.
| Provider | Target Ecosystem | Superpowers |
|---|---|---|
| π» local | DuckDB, Local FS | Zero-config. Runs anywhere. Perfect for dev/test. |
| βοΈ gcp | Google Cloud | BigQuery, GCS, Composer (Airflow), Dataform, IAM. |
| π©οΈ aws | Amazon Web Services | S3, Glue, Athena, Redshift, MWAA, IAM. |
| βοΈ snowflake | Snowflake | Databases, schemas, streams, tasks, RBAC, sharing. |
Export-only providers for open data standards: odps, odcs, datamesh-manager.
FLUID Forge is modular. Install only what you need.
pip install fluid-forge # Minimal β CLI + Local/DuckDB provider
pip install "fluid-forge[gcp]" # + Google Cloud
pip install "fluid-forge[aws]" # + AWS
pip install "fluid-forge[snowflake]" # + Snowflake
pip install "fluid-forge[all]" # Everythingπ‘ Tip: We recommend pipx for an isolated global install:
pipx install "fluid-forge[all]"
FLUID Forge is designed to feel as natural as git or terraform.
fluid init # Scaffold a new Data Product contract
fluid validate contract.fluid.yaml # Validate schema, dependencies, syntax
fluid plan contract.fluid.yaml # Generate a deterministic execution plan
fluid apply contract.fluid.yaml # Execute the plan against your target provider
fluid verify contract.fluid.yaml # Post-deployment data quality & compliance checksfluid forge # π€ Interactive, AI-powered project creation
fluid generate-airflow contract.fluid.yaml # Compile contract β native Airflow DAG
fluid generate-pipeline contract.fluid.yaml # Scaffold transformation codefluid policy-compile contract.fluid.yaml # Translate policies β native IAM
fluid contract-tests contract.fluid.yaml # Run assertion suitesfluid graph contract.fluid.yaml # Graphviz DAG of internal lineage
fluid docs contract.fluid.yaml # Auto-generate documentation from contractDon't start from scratch. fluid init ships with battle-tested enterprise patterns:
fluid init --template customer-360| Template | What You Get |
|---|---|
hello-world |
The basics β start here |
incremental-processing |
Append/Merge load patterns |
multi-source |
Complex DAG dependency orchestration |
policy-examples |
Advanced RBAC and AI agent governance |
FLUID Forge is community-driven. We want your ideas, providers, and pull requests!
- Fork the repo
- Run
make setupfor a full dev environment - Check out CONTRIBUTING.md for style guides and architecture overview
Please read our Code of Conduct before participating.
To report security vulnerabilities, see SECURITY.md.
Apache License 2.0 Β· Copyright 2024β2026 Agentics Transformation Pty Ltd
Built for the future of data. Built for the Agentic Era.
Documentation Β· FLUID Specification Β· The Book Β· PyPI Β· Issues
πΏπ¦ Proudly developed by dustlabs.co.za