Bria Fibo 2.0 (8B, NC): a self-hosted bulk leg for Bubble catalogs alongside BIAIG—license boundaries and fallback routing
HF Fibo 2.0 weights are CC BY-NC 4.0; a commercial Bubble catalog needs Bria Cloud or a paid self-host license. How to keep bulk throughput as a fallback next to BIAIG—not as an NC primary without legal review.
Why now
Bria Fibo 2.0 landed in the digest: open weights (~8B), unified generation and editing (Fibo-2.0-dev, Fibo-2.0-edit-turbo on Hugging Face, diffusers BriaFibo2Pipeline). My backlog already has ComfyUI/Qwen and Diffusers self-hosted legs—Fibo adds a distinct license and compliance angle for production catalogs, not a benchmark story. A closer look: ComfyUI 0.40 and Qwen-Image 2.1.
Primary vs reserve capacity
In a typical stack, BIAIG (your internal name for the commercial hosted path—Bria Cloud / Image Generation API in public docs: async generation, C2PA, indemnity language) stays my default route for catalog traffic. Same topic: Qwen-Image-2.1 before 28.09 UTC+8: freeze.
Fibo as a bulk leg makes sense for extra throughput (high-volume gen + edit). I wire it as fallback or a licensed capacity pool, not “HF download → production” until legal confirms the tier.
The hard boundary: HF weights ≠ commercial catalog
Public HF checkpoints are under CC BY-NC 4.0: rights for non-commercial use only (CC defines non-commercial as not primarily for commercial advantage or monetary compensation). HF gating asks intended use and points to a separate commercial agreement with Bria.
Bubble catalog implication (paid SKUs, merchant-facing assets): any route that serves customer output from HF-downloaded NC weights is not a safe primary without a Bria commercial or self-hosted license that explicitly covers that deployment.
I do not conflate README marketing (“enterprise-grade”) with the NC license section—training-data messaging is not the same as your right to run the model commercially in a catalog.
Legitimate production bulk paths
- Bria Cloud API (Fibo v2) — documented commercial surface; contrast with raw NC weights (indemnity/C2PA in vendor docs).
- Paid self-host Fibo 2 — per-model subscription; one license covers generation and editing; ~26 GB weights from Bria’s CDN (not HF);
BRIA_API_TOKEN, runtime license checks, Console metering (self-hosted tag; overage billed, not hard-blocked—use caps and alerts). - Enterprise — when you need SLA/indemnity/resell language or exceed self-serve revenue gates (docs mention card checkout under $10M revenue; larger operators go sales-led).
Self-host is not fully offline: the official pipeline uses Google Vertex AI for prompt expansion (VGL); the HF/diffusers path uses bria-vgl + Gemini. Fallback uptime depends on GCP/Google APIs, not only GPUs.
Attribution Agent on self-hosted/enterprise sends irreversible output embeddings (not images) to Bria; docs say do not disable it or licensing coverage may break—review against catalog privacy commitments.
Fallback routing (methodology)
| Leg | Catalog role |
|---|---|
| BIAIG / Bria Cloud | Primary production |
| Licensed self-host Fibo 2 | Bulk, burst, DR after entitlement confirmed |
| HF NC + ComfyUI/Diffusers | R&D, staging, feature-flagged; not merchant-facing without license |
Fail closed: lapsed self-host license stops new runs after restart—fallback must not silently continue on NC weights on a commercial path.
Feature flags: NC HF only in non-commercial or pre-legal environments; production catalog → cloud and/or licensed self-host.
Align outbound allowlists with Bria best practices (engine, weights CDN, attribution, Vertex/Gemini). On LicenseError, switch legs and alert—do not retry on NC.
How this differs from your Qwen articles
Qwen-Image 2.1 uses the Qwen Research License (non-commercial use of materials; commercial license separate); public debate on output rights shows research/NC licenses need review before catalog wiring. Swapping Qwen for Fibo does not remove legal work—it changes vendor and license text. This piece emphasizes dual routing and compliance, not “#1 editing” (vendor claim on Artificial Analysis—optional context only). Same topic: Qwen-Image-2.1 open source: RGBA, 10.
Fine-tuning
Fine-tunes on Fibo-2.0-dev under NC produce Adapted Material still constrained by NC—commercial catalog fine-tunes likely need a commercial agreement even when base inference is licensed.
Open questions (legal/ops, not code guesses)
- What BIAIG maps to in your repo (public Bria docs use Cloud/Fibo API, not that acronym).
- Whether catalog “commercial use” includes reselling generated assets to merchants vs internal ops only.
- Whether emergency failover to NC HF during a licensed outage still counts as commercial inference (undocumented by Bria).
- Air-gapped deployments: attribution plus VGL dependencies.
- ComfyUI nodes on HF weights—same NC boundary (likely yes).
- Upcoming Product Shot LoRA—terms at launch for e-commerce workloads.
Sources (Scout packet)
Hugging Face briaai/Fibo-2.0-dev, Fibo-2.0-edit-turbo; docs.bria.ai (Fibo 2, self-hosted, deployment options, best practices, image generation); CC BY-NC 4.0 legal code; Qwen-Image 2.1 LICENSE and HF discussion on commercial outputs—for parallel compliance context.
Internal editorial draft. Not for external publication.