Fluid ForgeFluid Forge
Home
Get Started
  • Local (DuckDB)
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
CLI Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
GitHub
Home
Get Started
  • Local (DuckDB)
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
CLI Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
GitHub
  • Introduction

    • /
    • Getting Started
    • Snowflake Quickstart
    • Vision & Roadmap
  • Walkthroughs

    • Walkthrough: Local Development
    • Walkthrough: Deploy to Google Cloud Platform
    • Walkthrough: Snowflake Team Collaboration
    • Declarative Airflow DAG Generation - The FLUID Way
    • Generating Orchestration Code from Contracts
    • Jenkins CI/CD for FLUID Data Products
    • Universal Pipeline
  • CLI Reference

    • CLI Reference
    • fluid init
    • fluid forge
    • fluid status
    • fluid validate
    • fluid plan
    • fluid apply
    • fluid generate
    • fluid publish
    • fluid market
    • fluid import
    • fluid policy-check
    • fluid diff
    • fluid test
    • fluid verify
    • fluid config
    • fluid split
    • fluid bundle
    • fluid auth
    • fluid doctor
    • fluid providers
    • fluid version
  • Providers

    • Providers
    • Provider Architecture
    • GCP Provider
    • AWS Provider
    • Snowflake Provider
    • Local Provider
    • Creating Custom Providers
    • Provider Roadmap
  • Advanced

    • Blueprints
    • Governance & Compliance
    • Airflow Integration
    • Built-in And Custom Forge Guidance
    • FLUID Forge Contract GPT Packet
    • Forge Discovery Guide
    • Forge Memory Guide
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge Docs Baseline: CLI 0.7.9
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

Getting Started

Run your first data product locally in a few minutes, then move to cloud targets when you are ready.

What this guide assumes

  • Python 3.9+
  • pip
  • No cloud credentials required for the local-first path

Install the CLI

pip install data-product-forge

Check the installed CLI and basic system health:

fluid version
fluid doctor

This docs set tracks CLI release 0.7.9.

Stuck on install? Jump to Troubleshooting further down, or open an issue — happy to help.

Understand the version numbers

You will see two different version concepts in the docs:

  • fluid version reports the installed CLI release, such as 0.7.9
  • fluidVersion inside contract.fluid.yaml selects the contract schema version, such as 0.7.2

Current scaffolds in forge-cli emit fluidVersion: 0.7.2.

Quickstart with fluid init

Create a local project:

fluid init my-project --quickstart
cd my-project

Then run the core workflow:

fluid validate contract.fluid.yaml
fluid plan contract.fluid.yaml
fluid apply contract.fluid.yaml --yes

What the quickstart gives you

The generated project includes a working contract plus local assets so you can validate and apply immediately. The exact scaffold evolves over time, but the important files are:

my-project/
├── README.md
├── contract.fluid.yaml
├── data/
└── .fluid/

Optional AI-assisted path with fluid forge

If you want the CLI to discover local context and scaffold with LLM help, use fluid forge instead of fluid init:

fluid forge
fluid forge --domain finance
fluid forge --llm-provider openai --llm-model gpt-4o-mini

Use fluid init for the fastest deterministic quickstart. Use fluid forge when you want discovery, memory, or domain-guided scaffolding.

Promoted next commands

fluid test contract.fluid.yaml
fluid verify contract.fluid.yaml
fluid generate schedule --scheduler airflow
fluid publish contract.fluid.yaml

Compatibility note: fluid generate-airflow still exists, but the promoted orchestration path is fluid generate schedule --scheduler airflow.

Move to providers later

When you are ready to target a provider:

  • GCP guide
  • AWS guide
  • Snowflake quickstart
  • Provider overview

Troubleshooting

fluid: command not found

Try the module entry point:

python -m fluid_build.cli --help

Local quickstart dependencies look incomplete

Run:

fluid doctor --verbose

Unsure what to use next

Use the CLI help pages:

fluid --help
fluid <command> -h

Next steps

  • CLI Reference
  • Local walkthrough
  • Vision

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
Edit this page on GitHub
Last Updated: 4/16/26, 11:38 AM
Contributors: Jeff Watson, jeffwatson-ai
Prev
/
Next
Snowflake Quickstart