Radius
Early-alpha configurable AI gateway for Pi with organization-level controls and upstream model routing.
Score calculation
(3 + 3 + 4 + 1 + 7) ÷ 5 = 3.6
5 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Radius is an early-alpha configurable AI gateway for Pi, not a model. The selected gateway policy routes requests to an upstream model and provider.
What fits your needs
Radius is an early-alpha configurable AI gateway for Pi, not a model. The selected gateway policy routes requests to an upstream model and provider.
Route through a gateway
Radius adds a configurable model/provider gateway and organization controls to Pi.
Treat gateway and model separately
The chosen upstream model remains responsible for its own training and provider terms.
Tradeoffs to expect
Early alpha
Pi’s provider guide explicitly identifies Radius as early alpha.
See the evidence
Retention terms unclear
Public materials reviewed do not specify detailed retention and location terms.
See the evidence
How to switch
Select upstream route
Use available Radius provider controls to change or inspect an upstream route.
Practical questions
Confirm current data terms
Check gateway retention, service location and provider contracts before routing sensitive code.
See the evidence
Inspect current model route
Use Pi’s Radius controls to review the current upstream route.
Radius is a model gateway; no energy or electricity reporting is available in the reviewed docs.
See the evidence
The provider/model route changes the inference destination. Radius documentation doesn’t confirm per-task consumption, facility electricity or resource controls.
1 + 1 reporting + 0 electricity + 1 controls = 3/10. This grades documented practices and transparency.
Upstream provider, model, region, energy, water and electricity mix are not established.
- Reporting1/3
- Gateway and route are documented without energy accounting.
- Electricity sourcing0/3
- No upstream clean-power or electricity mix is disclosed.
- Resource controls1/3
- Organization controls and routing are available, but energy controls or measured savings are not documented.
Water disclosure
Water reporting has not been assessed for this choice.
Radius is a gateway, not a trained model; training-data rights depend on the upstream route.
See the evidence
Pi describes Radius as a configurable gateway to upstream models. Gateway policy doesn’t settle rights in model training material.
Exact model, provider, version, base training data and route terms must be resolved per request.
Radius routes prompts through an early-alpha gateway; its public docs do not fully specify retention, provider contracts or hosting locations.
See the evidence
Pi documents Radius as a configurable gateway with organization controls and analytics. Both the gateway and upstream model provider are in the data path; detailed retention and location terms were not established in reviewed materials.
Prompt retention, gateway logging, service locations and provider contracts remain unclear in public documentation.
Radius is a managed early-alpha gateway for Pi, not a model release.
See the evidence
Pi documents a Radius provider integration and hosted gateway service; the package exposes integration code but upstream models and gateway service are separate.
Production readiness, service implementation and detailed operator controls are limited or unspecified while the service is early alpha.
Earendil Works has no workforce disclosures covering the AI supply chain in the reviewed public sources.
See the evidence
The reviewed public sources do not describe employee conditions, worker voice, or contractor protections for Earendil Works. Missing disclosure is an evidence gap, not proof of mistreatment. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
1 + 0 + 0 + 0 = 1/10. Documented worker protections; missing disclosure is an evidence gap.
Contractor conditions, data annotation and moderation, worker representation, remedies and independent review remain unknown.
- Pay & conditions0/3
- No worker conditions policy or implementation evidence was found in reviewed sources.
- Worker voice & remedy0/3
- No worker voice, representation or grievance safeguard was found in reviewed sources.
- Evidence & follow-through0/3
- No independent worker-level evidence was found in reviewed sources.
No military relationship was established from the reviewed public sources for Earendil Works; the score reflects uncertainty.
See the evidence
The sources reviewed did not establish a military contract or operational defense offering for Earendil Works. The method starts at 7 when a military relationship is not established; missing disclosure is not proof that none exists. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
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.
This bounded review cannot rule out unreported customers, indirect use, subcontracting or future work.
- Use restrictions0/4
- No public military-use restriction was found in the reviewed sources.
- Enforcement & oversight0/3
- No independently evidenced military-use oversight was found.
- Relationship disclosure0/2
- No military customer or relationship disclosure was identified.
No military relationship for Earendil Works was established in the reviewed sources; this is not proof that none exists.
Military rubric ↗Earendil Works was not named on the two BNC campaign pages checked. This limited list check is not an endorsement.
See the evidence
The BNC selects specific company targets; Earendil Works was not named in the official priority guide or No Tech campaign when checked. This is not a nationality-based assessment or proof that the company has no other relevant relationships. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
This covers only the BNC corporate guide and No Tech page. Other BDS campaigns, local calls, ownership changes, contractors and business relationships are outside the check.
All sources
- Pi provider documentation including Radius ↗
- Pi Radius package and gateway documentation ↗
- Pi model selection and local routes ↗
- BNC official boycott and pressure guide ↗
- BNC official No Tech campaign ↗
- Pi agent architecture and sessions ↗
- Pi security guidance ↗
- Earendil Works Pi repository and MIT license ↗