Fluid Forge
Why Forge
Concepts
Get Started
  • Consume a Data Product
  • See it run
  • Demos
  • Local (DuckDB)
  • Source-Aligned (Postgres → DuckDB)
  • AI Forge + Data Models
  • MCP Output Port — Serve to AI Agents
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
  • 11-Stage Production Pipeline
  • Catalog Forge End-to-End
CLI Reference
  • Agent Policy (concept)
  • MCP Output Port — Serve to Agents
  • MCP deep-dive
  • AI-assisted authoring
  • LLM providers & backends
  • Overview
  • Quickstart
  • Examples
  • Your own CI
  • Your own scaffolding
  • Custom validator
  • Apply hook
  • Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
Why Forge
Concepts
Get Started
  • Consume a Data Product
  • See it run
  • Demos
  • Local (DuckDB)
  • Source-Aligned (Postgres → DuckDB)
  • AI Forge + Data Models
  • MCP Output Port — Serve to AI Agents
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
  • 11-Stage Production Pipeline
  • Catalog Forge End-to-End
CLI Reference
  • Agent Policy (concept)
  • MCP Output Port — Serve to Agents
  • MCP deep-dive
  • AI-assisted authoring
  • LLM providers & backends
  • Overview
  • Quickstart
  • Examples
  • Your own CI
  • Your own scaffolding
  • Custom validator
  • Apply hook
  • Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
  • Introduction

    • Home
    • Why Fluid Forge
    • Getting Started
    • Snowflake Quickstart
    • See it run
    • Forge Data Model
    • Vision & Roadmap
    • Playground
    • FAQ
  • Concepts

    • Concepts
    • Builds, Exposes, Bindings
    • What is a contract?
    • Quality, SLAs & Lineage
    • Governance & Policy
    • Agent Policy (LLM/AI governance)
    • Providers vs Platforms
    • Fluid Forge vs alternatives
  • Data Products

    • Consume a Data Product
    • Product Types — SDP, ADP, CDP
  • Walkthroughs

    • Walkthrough: Local Development
    • Source-Aligned: Postgres → DuckDB → Parquet
    • AI Forge And Data-Model Journeys
    • Walkthrough: MCP Output Port
    • 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
    • The 11-Stage Pipeline
    • End-to-End Walkthrough: Catalog → Contract → Transformation
  • CLI Reference

    • CLI Reference
    • Core workflow

      • fluid init
      • fluid demo
      • fluid forge
      • fluid validate
      • fluid plan
      • fluid apply
      • fluid diff
      • fluid status
    • Build & ship

      • fluid bundle
      • fluid generate
      • fluid generate artifacts
      • fluid validate-artifacts
      • fluid verify-signature
      • fluid generate iac
      • fluid generate-airflow
      • fluid generate-pipeline
      • fluid viz-graph
      • fluid publish
      • fluid ship
      • fluid rollback
      • fluid schedule-sync
    • AI & Agents

      • fluid ai
      • fluid agents
      • fluid mcp
      • fluid memory
      • fluid stats
      • fluid skills
    • Quality & governance

      • fluid test
      • fluid verify
      • fluid contract-tests
      • fluid contract-validation
      • fluid policy
      • fluid policy check
      • fluid policy compile
      • fluid policy apply
    • Standards & interoperability

      • fluid odps
      • fluid odps-bitol
      • fluid odcs
      • fluid export
      • fluid export-odps
      • fluid exporters
      • fluid import
      • fluid market
      • fluid datamesh-manager
    • Project & workspace

      • fluid product-new
      • fluid product-add
      • fluid workspace
      • fluid contract
      • fluid split
      • fluid config
      • fluid providers
      • fluid plugins
      • fluid provider-init
      • fluid auth
      • fluid secrets
      • fluid ide
      • fluid scaffold-ci
      • fluid scaffold-composer
      • fluid scaffold-ide
      • fluid docs
      • fluid runs
      • fluid retention
      • fluid describe
      • fluid doctor
      • fluid roadmap
      • fluid version
    • Catalog adapters

      • Source Catalog Integration (V1.5)
      • Publishing to a Catalog — Overview
      • BigQuery Catalog
      • Snowflake Horizon Catalog
      • Databricks Unity Catalog
      • Google Dataplex Catalog
      • AWS Glue Data Catalog
      • DataHub Catalog
      • Data Mesh Manager Catalog
      • OpenMetadata Catalog
    • CLI by task

      • CLI by task
      • Add quality rules
      • Add agent governance
      • Debug a failed pipeline run
      • Switch clouds with one line
  • Recipes

    • Recipes
    • Recipe — add a quality rule
    • Recipe — switch clouds with one line
    • Recipe — tag PII in your schema
    • Write a contract that consumes another contract
    • Generate per-environment overlays
  • SDK & Plugins

    • SDK & Plugins
    • Quickstart — your first plugin
    • Examples

      • Runnable examples
      • Example: hello-scaffold — the minimal viable plugin
      • Example: gitlab-ci-scaffold — generate a complete CI project
      • Example: steward-validator — a custom governance rule
      • Example: prod-key-guard — apply-time invariant check
    • Journeys

      • Journeys
      • Your own CI/CD

        • You have your own CI/CD setup, no problem
        • GitLab CI — the bundle template
        • GitHub Actions — the bundle template
        • Jenkins — the bundle template
        • CircleCI — the bundle template
      • You have a strict project layout, no problem
      • You have governance rules, no problem
      • You want a check at apply time, no problem
    • Reference

      • Reference
      • Roles reference
      • Entry points reference
      • Trust model
      • Packaging
      • Companion packages
  • Providers

    • Providers
    • Provider Architecture
    • GCP Provider
    • AWS Provider
    • Snowflake Provider
    • Local Provider
    • Creating Custom Providers
    • Provider Roadmap
  • AI & Agents

    • MCP Server
    • Built-in And Custom Forge Guidance
    • Forge Discovery Guide
    • Forge Memory Guide
    • Authoring Forge Tools
    • Guided fluid forge UX
    • LLM Providers
    • LiteLLM Backend
    • Capability Warnings
    • Cost Tracking
    • FLUID Forge Contract GPT Packet
    • Agentic Primitives
  • Operate & Deploy

    • Airflow Integration
    • Blueprints
    • Source-Aligned Acquisition
  • Govern & Secure

    • Governance, Compliance & the Business Case
    • Governance & Compliance
    • Network Safety
    • Credential Resolver — Security Model
  • Configuration & Reference

    • Environment Variables
    • Typed Errors
    • Typed CLI Errors
    • API Stability — fluid_build.api
  • Architecture & Releases

    • V1.5 Catalog Integration — Architecture Deep-Dive
    • V1.5 + V2 Hardening — Release Notes
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge Docs Baseline: CLI 0.9.0
    • Fluid Forge Docs Baseline: CLI 0.8.11
    • Fluid Forge Docs Baseline: CLI 0.8.10
    • Fluid Forge Docs Baseline: CLI 0.8.9
    • Fluid Forge Docs Baseline: CLI 0.8.8
    • Fluid Forge Docs Baseline: CLI 0.8.7
    • Fluid Forge Docs Baseline: CLI 0.8.6
    • Fluid Forge Docs Baseline: CLI 0.8.5
    • Fluid Forge Docs Baseline: CLI 0.8.4
    • Fluid Forge Docs Baseline: CLI 0.8.3
    • Fluid Forge Docs Baseline: CLI 0.8.0
    • Fluid Forge Docs Baseline: CLI 0.7.11
    • Fluid Forge Docs Baseline: CLI 0.7.9
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

LiteLLM Backend

LiteLLM is the canonical LLM backend on v0.10.0 — every LLM call from fluid forge, fluid ai, and the copilot routes through it. LiteLLM replaced ~1,300 lines of per-provider wire-format code with one unified API; no extra install step, no toggle.

Where this fits

LiteLLM is wired into core data-product-forge (litellm >= 1.83.7, < 2 is a hard dependency). The historical "opt-in extra" framing from pre-0.8.0 docs is no longer accurate — the dispatcher always goes through LiteLLM. The companion LLM Providers page covers which provider env vars to set; this page covers the routing-layer specifics.

Built-in providers

The dispatcher resolves --llm-provider <name> against this provider map (fluid_build/cli/forge_copilot_llm_litellm.py):

Provider keyLiteLLM providerDefault model
openaiopenaigpt-4.1-mini
anthropicanthropicclaude-haiku-4-5
claude (alias for anthropic)anthropicclaude-haiku-4-5
geminigeminigemini-2.5-flash
google (alias for gemini)geminigemini-2.5-flash
bedrockbedrockanthropic.claude-3-5-sonnet-20240620-v1:0
vertex / vertex_aivertex_aigemini-2.5-flash
ollamaollama (localhost-only)gemma3:4b

Beyond these built-ins, LiteLLM exposes 100+ providers through its catalog — point --llm-model (or FLUID_LLM_MODEL) at any model the LiteLLM docs list and the dispatcher routes the call.

Quickstart

fluid forge --domain retail                                    # uses the configured default
fluid forge --llm-provider openai --llm-model gpt-4.1-mini
fluid forge --llm-provider bedrock --llm-model anthropic.claude-3-5-sonnet-20240620-v1:0
fluid forge --llm-provider vertex --llm-model gemini/gemini-2.5-pro

Per-call cost is attributed via LiteLLM's usage.cost field — accurate to the cent — and folded into .fluid/agents/<run-id>/cost.json. See fluid stats for the cross-run aggregator.

Configuration

Env varPurpose
FLUID_LLM_PROVIDERProvider key (openai / anthropic / gemini / bedrock / vertex / ollama, etc.). Honoured as the default when --llm-provider is not passed.
FLUID_LLM_MODELModel name. Use LiteLLM's model-name conventions (e.g. claude-haiku-4-5, gpt-4.1-mini, gemini/gemini-2.5-pro).
OPENAI_API_KEY / ANTHROPIC_API_KEY / GEMINI_API_KEYProvider keys. LiteLLM reads the same env-var names the underlying SDKs use.
AWS_* / AWS_PROFILEBedrock auth — standard AWS-CLI env vars.
GOOGLE_APPLICATION_CREDENTIALS / VERTEX_PROJECT / VERTEX_LOCATIONVertex AI auth.
FLUID_OLLAMA_MODELOverride the default Ollama model.
LITELLM_*Any LiteLLM-specific env var (LiteLLM reads these directly; Forge doesn't filter them).

See the canonical environment variables index for everything else.

Cost attribution

LiteLLM's usage.cost field is the authoritative per-call cost the LLM API itself reports, so the per-run cost.json and fluid stats reflect billing-grade figures:

# Internal — RunCostTracker.record_call accepts usd_override
tracker.record_call(
    provider="anthropic",
    model="claude-haiku-4-5",
    input_tokens=8420,
    output_tokens=1800,
    usd_override=0.0286,   # passed in from LiteLLM's reported cost
)

Runs from older releases that pre-date the LiteLLM unification still show the heuristic estimate until they age out of .fluid/agents/.

Capability warnings

The capability catalog at fluid_build/copilot/agents/capability_catalog.py covers the canonical provider/model combinations. The warnings reflect the underlying model regardless of LiteLLM's routing layer — claude-sonnet-4-6 warns identically whether reached via anthropic direct or via Bedrock.

If you point LiteLLM at a model the catalog doesn't know, the run-start banner says "model X is not in the capability catalog" and the run continues with conservative defaults. See Capability Warnings.

Caveats

  • Tool-use behaviour matches LiteLLM's wrapper. If you've been depending on a specific provider's exact tool-use response shape, surface mismatches will show up at the agent-layer error classifier — but the typed errors (RateLimitError, ContextOverflowError, etc. — see Typed Errors) handle both wire shapes.
  • Ollama is restricted to localhost (127.0.0.1 / ::1) by the SSRF guard. See network safety.

See also

  • LLM Providers — provider-specific env vars and auth modes
  • Capability Warnings — what the capability catalog enforces
  • Cost Tracking — how cost figures land in .fluid/agents/<run-id>/cost.json
  • fluid stats — aggregating cost across runs
  • Environment variables — canonical FLUID_* reference
Edit this page on GitHub
Last Updated: 6/27/26, 4:58 PM
Contributors: fas89, Claude Opus 4.7 (1M context)
Prev
LLM Providers
Next
Capability Warnings