Fluid Forge
Contract-first data products, from local DuckDB to multi-cloud delivery.
Local First
Install the CLI, scaffold a project, validate it, and run it locally before you touch cloud credentials.
Contract-Driven
Use one FLUID contract to describe the data product, then plan, test, verify, and publish from the same source of truth.
Promoted CLI Surface
These docs track the current `fluid --help` experience so new users are not sent down stale or deprecated command paths.
AI-Optional
Start with `fluid init` for a quickstart or use `fluid forge` when you want AI-assisted scaffolding and discovery.
Multi-Target Delivery
Build locally with DuckDB, then target GCP, AWS, Snowflake, or standards/export flows when you are ready.
Compatibility Aware
Legacy commands still exist in the docs where they matter, but primary pages lead with the current recommended workflow.
Fluid Forge is for data engineers who want to write a data product contract once and deploy it anywhere. Build and test locally with DuckDB, then push the same contract to BigQuery, Athena, or Snowflake — no pipeline glue code to maintain.
Start with the current workflow
pip install data-product-forge
fluid version
fluid doctor
fluid init my-project --quickstart
cd my-project
fluid validate contract.fluid.yaml
fluid plan contract.fluid.yaml
fluid apply contract.fluid.yaml --yes
This docs site currently tracks:
- CLI release
0.7.9 - Scaffolded contract examples using
fluidVersion: 0.7.2
fluid version and fluidVersion are different things. The first is the CLI release you installed. The second is the schema version inside a contract.
Optional AI-assisted scaffolding
fluid forge
fluid forge --domain retail
fluid forge --llm-provider openai --llm-model gpt-4o-mini
Use fluid forge when you want discovery, memory, and LLM-guided scaffolding. Use fluid init when you want the fastest deterministic quickstart.
Promoted command groups
| Group | Commands |
|---|---|
| Core Workflow | init, forge, validate, plan, apply |
| Generate | generate transformation, generate schedule, generate ci, generate standard |
| Integrations | publish, market, import |
| Quality & Governance | policy-check, diff, test, verify |
| Utilities | config, split, bundle, auth, doctor, providers, version |
Where to go next
- Getting Started for the local-first path
- CLI Reference for the promoted command surface
- Providers for platform-specific guidance
- Walkthroughs for end-to-end examples
Compatibility note: fluid generate-airflow is still available, but primary docs now lead with fluid generate schedule --scheduler airflow.
Need help?
- Questions or ideas? Start a GitHub Discussion — we read every one.
- Bug or unexpected behavior? Open an issue with what you ran and what you saw.
- Want to contribute? See the contributing guide — we welcome doc fixes, examples, and providers.