Ethical Stack.

Liquid RIPL

An enterprise inference engine for running Liquid models on NVIDIA GPUs in latency-sensitive applications.

Score calculation

(3 + 8 + 2 + 2 + 2) ÷ 5 = 3.4

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

Full scoring method ↗
Setup details

Enterprise deployment of the RIPL engine in a customer-selected environment. It is not a self-service public model API.

What fits your needs

Enterprise deployment of the RIPL engine in a customer-selected environment. It is not a self-service public model API.

What it does

An enterprise inference engine for running Liquid models on NVIDIA GPUs in latency-sensitive applications.

See the evidence
Tradeoffs to expect

Hardware and formats

RIPL is an enterprise engine, not a token-billed public endpoint; confirm deployment, support and retention in the agreement.

See the evidence
How to switch

Get started

Contact Liquid for an enterprise deployment and benchmark your own workload.

See the evidence
Practical questions

Data path

Local mode keeps model computation on your hardware; remote tools or backends can send data elsewhere.

See the evidence

Use limitations

A third-party model, backend or service keeps its own terms and safeguards.

See the evidence

Energy practices

3/10↑

Local deployment and smaller models give you useful controls; clean-electricity evidence is missing.

See the evidence

This rating credits documented practices, not assumed energy savings. RIPL documents GPU deployment and workload-specific inference benchmarks. Latency and parameter count are not electricity measurements.

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

Comparable task-level electricity, water, training footprint and independently verified clean-power sourcing are not published for this choice.

Reporting1/3
The documented route identifies where inference can run, without an audited environmental footprint.
Electricity sourcing0/3
No attributable electricity procurement or hourly clean-power evidence was found in the cited material.
Resource controls1/3
Workload-specific deployment is documented, without a measured power reduction.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

Training-data rights depend on the model you run.

See the evidence

This service or engine can run different Liquid models. A single training-data rating would hide those differences. Check the chosen model’s profile and any base model it builds on; local processing and enterprise no-training terms concern new inputs, not permission for the original training data.

The selected model, checkpoint and any customer fine-tuning data determine the training-rights assessment.

Your data & privacy

8/10↑

Running locally can keep prompts on your own hardware; your app and tools still control other data paths.

See the evidence

RIPL is offered for enterprise deployment, and Liquid’s custom-deployment pricing page says customer data stays in the customer environment and is not used for training. Confirm that boundary in your agreement; a managed remote installation may differ.

8/10 credits a documented local data path with configuration and audit limits.

No independent network audit is claimed. App backups, runtime telemetry, tools and hosting setup can create other copies.

Openness

2/10↑

The service is proprietary; some related models and developer tools are published.

See the evidence

The reviewed official sources do not offer the complete application or serving engine under an open-source license. Liquid’s published weights, MIT-licensed Finetune tools and Apache-licensed Pipette clients are separate artifacts and do not make this service open.

2/10 credits limited public technical documentation; the application/engine itself remains proprietary.

Complete production source and independently reproducible service behavior are not publicly supplied.

Worker protections

2/10↑

Liquid publishes hiring and wellbeing commitments, but little evidence about its wider AI workforce.

See the evidence

Its careers page commits to equal opportunity and interview accommodations; company values mention wellbeing. These earn limited policy credit. The reviewed sources provide no contractor pay standards, protected grievance channel or independent evidence covering annotation, moderation and other AI supply-chain work. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

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

Contractor conditions, worker representation, grievance outcomes and independent workforce audits remain undisclosed.

Pay & conditions1/3
Public equal-opportunity and accommodation commitments provide basic policy evidence.
Worker voice & remedy0/3
No worker grievance or representation safeguard was found in the reviewed public material.
Evidence & follow-through0/3
No independent worker-level implementation review was supplied in these sources.
Workers rubric ↗

Military ties

2/10Operational military support↑

Liquid actively offers tactical AI for threat detection, ISR and uncrewed systems.

See the evidence

Liquid’s defense page markets on-device models for combat-relevant intelligence and autonomous systems. We treat that operational offering as direct military enablement under the rubric, which caps the score at 2. Its general service terms prohibit unlawful harm and permit suspension, but do not rule out defense use. This is evidence of an offering, not proof that any particular checkpoint has been deployed by a named military customer. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 1 use restrictions + 1 enforcement & oversight + 1 relationship disclosure = 4, capped at 2/10. Known defense ties lower this rating; safeguards can improve it within the relationship’s cap.

Named defense contracts, actual deployments, customer screening and independent oversight are not disclosed on the reviewed page.

Use restrictions1/4
General prohibitions cover unlawful harm; no blanket restriction on operational military use is stated.
Enforcement & oversight1/3
Terms allow suspension for violations, without a disclosed military-use review process.
Relationship disclosure1/2
The defense offering is public, but customers, contract scope and deployments are not named.

The vendor explicitly offers tactical threat detection, ISR, dismounted-team decision support and onboard perception for autonomous uncrewed systems; this is operational military enablement, without a claim of a named contract. The relationship limits this grade to 2/10.

Military rubric ↗

BDS targets

Not listed↑

Liquid AI is not named in the checked BNC boycott and technology target lists.

See the evidence

The BNC consumer guide and No Tech campaign page do not name Liquid AI as a boycott or pressure target. This is a limited campaign-list finding; it is not an endorsement or a wider assessment of every supplier or customer. The defense offering is assessed separately in military ties. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

The checked lists do not identify every commercial relationship or local campaign.

More from Liquid AI

All sources

Side by side