Fluid Forge
Declare a data product once in a contract. Build it on your laptop, deploy it to AWS, GCP or Snowflake, and verify that what landed matches what you declared.
Local first
Install with the local extra, then validate, plan, apply, verify and test a product on DuckDB before you touch a cloud credential.
One contract, one file or many
Write a product as one file, or as a root contract plus fragment files. validate, plan and apply resolve the fragments into one document.
Environments and two clouds
--env picks an overlay that patches the base contract. Since 0.17.0 one contract deploys to AWS and to GCP this way, with its retention, encryption and column restrictions mapped to each cloud's own resources.
Verify what landed
fluid verify reads the deployed target and compares it with the contract. With --strict, drift fails the build, so it can gate CI.
Sovereignty enforced
Pin a jurisdiction in the contract and the engine blocks a mismatched binding. An EU contract bound to us-east-1 fails "fluid validate" with exit 1.
Command Center
fluid publish sends a product to a FLUID Command Center catalog, and fluid apply reports its runs there once a credential is configured.
Fluid Forge is a command-line tool, fluid, for data engineers who build data products. You describe a product in a contract: its schema, how it is built, where it lands, its quality rules, who may read it and where it may live. The CLI validates the contract, plans and applies it to the platform the binding names, and checks the deployed result against it.
- The contract is the source of truth. The plan, the cloud resources, the access rules and the checks
fluid verifyruns are all derived from it. See What is a contract. - One contract, several places. An overlay per environment patches the binding, so the same contract runs in
devandprod, or on AWS and GCP. See Environments and overlays and Governance parity. - Checked before and after.
fluid validaterefuses a contract that breaks the schema or its own sovereignty pin;fluid testruns the data-quality rules;fluid verifycompares what landed with what was declared.
Where Forge does and does not fit next to dbt, Terraform, Airflow and Snowpark: Fluid Forge vs alternatives.
Run it
pip install "data-product-forge[local]"
mkdir fluid-quickstart && cd fluid-quickstart
fluid init my-first-product --blueprint fluid.starter
cd my-first-product
fluid validate contract.fluid.yaml
fluid plan contract.fluid.yaml
fluid apply contract.fluid.yaml --yes --mode amend-and-build
fluid verify contract.fluid.yaml --strict
cat runtime/out/my-first-product.csv
message,created_at
Hello from the my-first-product data product,2026-10-05 10:35:49.479853+02
Getting Started walks through each step with its output, then makes the product read a CSV and adds a data-quality rule. It explains why it uses the fluid.starter blueprint rather than fluid init --quickstart.
This site documents CLI 0.35.0, with contract schema 0.7.6 as the stable default and 0.7.7 as an opt-in preview. fluid version is the CLI release you installed; fluidVersion inside a contract is the schema version it is written against. Which version each scaffold writes is in Understand the version numbers.
Follow one product from laptop to production
The docs are ordered as the life of a data product. Each step links to the page that covers it:
- Install and build locally: Getting Started, then the local walkthrough.
- Understand the contract: What is a contract, Builds, exposes, bindings, and the contract reference.
- Split it into files: Contract fragments and
$ref. - Run it in each environment, and on two clouds: Workspaces, Environments and overlays, One contract, two clouds, OpenTofu state.
- Govern it: Governance and policy, Governance parity, Sovereignty, Agent policy.
- Ship it: The 11-stage pipeline, Declarative Airflow,
fluid publishand the Command Center. - Change it and upgrade: Change a live data product and Upgrading.
See it run
A 60-second walkthrough of the core move: one contract.fluid.yaml, built and tested locally on DuckDB, then pointed at BigQuery and Snowflake by changing its binding. In the sovereignty-platform-swap example the AWS, GCP and Snowflake contracts differ only inside binding; run diff on them to check.
Use ←/→ to step scenes, space to pause, r to restart. The reels were recorded on an earlier CLI; See it run has the full set and says what has changed since.
AI-assisted scaffolding
fluid forge
fluid forge --domain retail
(since 0.31.0, forge-cli #881) Removed: fluid forge --domain. Use fluid forge --context "<what the product is for>", or name the domain in the prompt.
fluid init scaffolds from a fixed template or blueprint. fluid forge drafts a contract from the files in your directory with the LLM provider you configure with fluid ai setup. An API-key provider needs pip install "data-product-forge[litellm]". (since 0.28.0, forge-cli #837) Without an API key, fluid forge --llm-provider claude-code uses your Claude Code login, and fluid forge --template starter uses no AI. To forge a data model from a business intent file and generate dbt from it:
fluid forge data-model from-intent --example retail > intent.yaml
fluid forge data-model from-intent intent.yaml -o customer_orders.fluid.yaml
fluid generate transformation customer_orders.fluid.yaml -o ./dbt_customer_orders --dbt-validate
See AI forge and data-model journeys.
Promoted command groups
These are the groups fluid --help prints on 0.29.0:
| Group | Commands |
|---|---|
| Core Workflow | init, forge, validate, plan, apply |
| Generate | generate transformation, generate schedule, generate ci, generate standard |
| Integrations | publish, market, import, mcp |
| Quality & Governance | policy-check, test |
| Safety & Supply Chain | rollback, verify-signature |
| Utilities | config, ai, split, auth, doctor, providers, exporters, version |
--help promotes a short surface. Commands such as bundle, diff, verify, runs, stats, ship and mission are registered and documented, and --help names the production path as bundle → validate → generate artifacts → diff → plan → apply → verify → publish. The CLI reference covers the commands. (since 0.31.0, forge-cli #881) fluid mission and fluid memory are removed.
Every release in one place
All releases lists every CLI version with what changed. Upgrading has the steps for each version you cross.
The vocabulary and the product types behind all of it: SDK & Plugins, Source-Aligned Acquisition, Product Types. ::::
Where to go next
- Getting Started: install and build your first product locally
- Tutorials: end-to-end builds, with what each one needs
- Recipes and CLI by task: one task on a contract you already have
- Concepts: the model, in reading order
- CLI reference and contract reference: commands, flags and fields
- Providers: what each platform supports
- Advanced: CI operation, security boundaries, the AI stack and runtime reference
- SDK & Plugins: extend the CLI with your own scaffolds, validators and apply hooks
Need help?
- Questions or ideas? Start a GitHub Discussion.
- Bug or unexpected behavior? Open an issue with what you ran and what you saw.
- Want to contribute? See the contributing guide: doc fixes, examples and providers are welcome.