Ethical Stack.

Bria Fibo

Structured-prompt image generation and editing model available through Bria APIs and licensed deployments.

Score calculation

(2 + 5 + 6 + 6 + 1 + 7) ÷ 6 = 4.5

6 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Fibo 2 image-generation model and Bria Build/API routes; on-prem/local deployment applies only to the separately documented Fibo Lite or licensed self-hosted product, not automatically to Bria Cloud.

What fits your needs

Fibo 2 is accessed through Bria Build; deployments and data boundaries differ by cloud API versus licensed self-hosting.

Structured image prompting

Turns a short prompt into an editable, machine-readable visual JSON description, then generates an image from that structure.

See the evidence

Controlled iterations

Supports instruction-based refinement and style-reference variations; Bria returns the structured prompt for follow-up edits.

See the evidence
Tradeoffs to expect

Commercial setup

API use requires a Bria token; self-hosting requires a separate per-model license and customer GPU deployment.

See the evidence

Content responsibility

Bria’s guidelines bar infringement of privacy/publicity rights and impersonation; users remain responsible for rights in uploaded material.

See the evidence
How to switch

Choose deployment

Create an API token for Bria Build, or request the applicable self-host license and deploy the selected model package on your infrastructure.

See the evidence
Practical questions

Local route

Fibo Lite is Docker-ready for local deployment; Bria’s self-hosting overview lists Fibo 2 as a licensed model, so confirm the exact edition before routing sensitive files.

See the evidence

AI provenance

Bria says generated outputs carry attribution and C2PA provenance; metadata does not itself establish permission for source images or likenesses.

See the evidence

Age and consent

Bria says its training data excludes public figures and biometric data; API moderation is configurable, and the reviewed docs don’t show a per-upload likeness-consent check.

See the evidence

Energy practices

2/10↑

Bria documents cloud and customer-hosted routes, but no Fibo request energy or facility electricity figures.

See the evidence

The operational boundary depends on whether a customer calls Bria’s API or runs a licensed model package on its own infrastructure. No route-level energy report or electricity mix is supplied; the local route is not assumed to use less energy.

1 + 1 reporting + 0 electricity + 0 controls = 2/10. This grades documented practices and transparency.

GPU, region, facility electricity, and workload energy are not reported per Fibo generation.

Reporting1/3
Bria documents hosted API and licensed customer-GPU/on-prem deployment boundaries, but provides no task-level energy disclosure.
Electricity sourcing0/3
Customer-selected local infrastructure and Bria Cloud are not mapped to an applicable facility electricity mix in the reviewed sources.
Resource controls0/3
The sources document Fibo/Fibo Lite model options and API rate limits, but don’t confirm a resource-setting tied to reduced physical demand.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

5/10↑

Bria reports commercial agreements with 30+ training-data partners and attribution-based revenue share, but does not publish the named training data or a creator-level training remedy in the reviewed sources.

See the evidence

Bria says each training asset has an identifier linked to source, creator and license terms, and its attribution system matches outputs to licensed data for partner revenue share. The public materials do not expose the training data inventory or agreement terms for inspection, and compensation after use is not evidence of individual permission before use or an opt-out/removal route.

1 + 2 source transparency + 2 permission + 0 creator controls = 5/10, with the permission cap applied.

Publicly inspectable source inventory, license terms per source, creator permission/removal process, and independent validation remain unavailable in the reviewed sources.

Source transparency2/3
Bria states Fibo has over 100 million training images and calls its data licensed, but does not publish a named-source inventory in the reviewed materials.
Documented permission2/4
Bria says all pipeline assets come from commercial agreements with 30+ partners and are tracked to license terms, but the named source inventory and agreements are not inspectable in the cited public catalog.
Creator controls0/2
Bria documents output attribution and revenue sharing for partner-licensed works, but the reviewed sources don’t confirm a source creator's permission-before-use, removal request, or retraining remedy.
Data-rights rubric ↗

Your data & privacy

6/10↑

Bria offers hosted API generation and separately licensed self-hosting; route choice changes where uploaded images and prompts are processed.

See the evidence

The Bria API uses an account token and returns generated asset URLs; the self-hosted license runs selected model packages on customer GPUs. Fibo Lite is described as Docker-ready for local deployment, so the cloud route and local route have different data boundaries.

6/10 reflects a published local deployment route and a hosted API route, with endpoint-specific retention and deployment coverage still unclear.

The reviewed sources do not specify uniform retention across all Fibo endpoints or quantify whether every Fibo 2 feature is available in the self-hosted Lite build.

Openness

6/10↑

Fibo is downloadable through Bria under model-specific licensing; self-hosted commercial use requires a license.

See the evidence

Bria links a model download and documents self-hosted model installation, but licenses each model separately and says Fibo weights on Hugging Face are source-available for non-commercial use unless separately licensed. The permissive open-source claim does not extend to all commercial deployments.

6/10 reflects downloadable weights and self-hosting documentation, offset by model-specific commercial licensing rather than an unrestricted open license.

Exact terms vary by weight package, self-host license, deployment scale and API usage.

Worker protections

1/10↑

Fibo developer documentation and model pages identify licensed visual-model deployment and output provenance, but do not disclose employee or contractor workforce measures.

See the evidence

The reviewed Bria product, safety and self-host documentation addresses model licensing, deployment, moderation and attribution. It contains no pay, workplace-condition, worker-voice or contractor-protection reporting, so the labour score records a disclosure gap rather than an allegation.

1 + 0 + 0 + 0 = 1/10. Documented worker protections; missing disclosure is an evidence gap.

Employee, contractor, annotation and moderation workforce conditions for Bria remain unestablished in these public sources.

Pay & conditions0/3
Reviewed Bria sources do not disclose worker pay, employment conditions or contractor protections.
Worker voice & remedy0/3
The cited Bria materials do not identify worker-voice, grievance or remedy processes.
Evidence & follow-through0/3
No independent workforce assurance is published in the cited Bria sources.
Workers rubric ↗

Military ties

7/10Not established↑

No military relationship or product-specific military safeguards are established in the reviewed Bria sources.

See the evidence

The official sources reviewed for Bria Fibo describe its creative route, model access and user terms but don’t show defense work, a military customer, or binding operational restrictions. This product-level disclosure gap does not resolve unreviewed corporate or downstream relationships.

7 base + 0 safeguard adjustment = 7/10 (0 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.

Company-wide defense customers and downstream uses of Bria Fibo were not exhaustively established.

Use restrictions0/4
Reviewed Bria sources do not state a binding military-use restriction for this product route.
Enforcement & oversight0/3
No military-specific oversight or enforcement is documented in the cited Bria sources.
Relationship disclosure0/2
The reviewed Bria sources do not disclose a military relationship for this product or operator.

The cited Bria product and policy materials don’t show a military contract, customer or deployment; that limited finding is not proof no such relationship exists.

Military rubric ↗

BDS targets

Not listed↑

The company is not named in the two reviewed official BNC campaign sources.

See the evidence

This entry records only whether the named company appears in the BNC consumer guide or No Tech campaign. Not listed is a limited source check, not a finding of endorsement, compliance or absence of supplier and investment relationships.

The check does not cover every campaign, subsidiary, investor, supplier, local listing or future target change.

All sources

Side by side