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
    • init Command
    • validate Command
    • plan Command
    • apply Command
    • verify Command
    • generate-airflow Command
  • 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 Agents
    • FLUID Forge Contract GPT Packet
    • Forge Copilot Discovery Guide
    • Forge Copilot Memory Guide
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

init Command

Create a new FLUID project with contracts, sample data, and a ready-to-run pipeline.

Syntax

fluid init [name] [options]

Options

Project Mode (mutually exclusive)

OptionDescription
--quickstartCreate a working example with sample data (recommended)
--scanImport an existing dbt or Terraform project
--wizardInteractive guided setup
--blankEmpty project skeleton
--template <name>Start from a named template (e.g. customer-360)

Additional Options

OptionDescriptionDefault
--provider <name>Target provider: local, gcp, aws, snowflake, azurelocal
--use-case <type>Project type: data-product, ai-agent, analytics, api—
--no-runDon't auto-execute the pipeline after creationfalse
--no-dagDon't auto-generate an Airflow DAGfalse
--dry-runPreview what would be created without writing filesfalse
--yes, -ySkip confirmation promptsfalse

What It Creates

fluid init my-project --quickstart creates the my-project/ directory for you and then copies the current quickstart scaffold into it. The default quickstart project looks like:

my-project/
├── README.md              # Template walkthrough and next steps
├── contract.fluid.yaml    # Data product contract
├── data/
│   ├── customers.csv
│   ├── interactions.csv
│   └── orders.csv
└── .fluid/
    └── db.duckdb          # Local DuckDB state created during init

Examples

Quickstart (Recommended)

fluid init bitcoin-tracker --quickstart

Creates the bitcoin-tracker/ directory and fills it with a fully working project you can run immediately:

cd bitcoin-tracker
fluid validate contract.fluid.yaml
fluid apply contract.fluid.yaml --yes

Scan Existing dbt Project

cd existing-dbt-project
fluid init --scan

Auto-detects dbt models and converts them into a FLUID contract.

GCP-Targeted Project

fluid init analytics --provider gcp --quickstart

Generates a contract configured for BigQuery deployment.

Blank Skeleton

fluid init my-project --blank

Creates a minimal project with an empty contract template.

Preview Mode

fluid init my-project --quickstart --dry-run

Shows what files and directories would be created, including the target project directory, without writing anything.

After Initialization

Once your project is created, follow the standard workflow:

# 1. Move into the project directory
cd my-project

# 2. Validate the contract
fluid validate contract.fluid.yaml

# 3. Deploy locally (or to cloud)
fluid apply contract.fluid.yaml --yes

See Also

  • Getting Started Guide — end-to-end first project walkthrough
  • validate command — validate your contract
  • apply command — deploy your project
Edit this page on GitHub
Last Updated: 4/4/26, 8:41 PM
Contributors: khanya_ai, fas89
Prev
CLI Reference
Next
validate Command