Ethical Stack.

Alibaba Cloud Model Studio

Regional developer platform for Qwen and third-party model inference, fine-tuning, and application building.

Score calculation

(3 + 7 + 2 + 6 + 7) ÷ 5 = 5.0

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

Full scoring method ↗
Setup details

Alibaba Cloud Model Studio API; region, model, account type and optional log configuration determine handling.

What fits your needs

Alibaba Model Studio API; regions and endpoints differ, and optional logging changes data retention.

Regional service

Documentation lists supported regions, model inference, fine-tuning, and API surfaces.

See the evidence
Tradeoffs to expect

Account configuration

Audit metadata logs are default; complete prompt/response logs require manual enabling and can be delivered to SLS.

See the evidence

Regional processing boundary

Each region has its own API key and model list; the access region determines data storage, while workspace scope determines where inference runs.

See the evidence
How to switch

Select region and endpoint

Choose the account region and its corresponding API endpoint before creating production credentials.

See the evidence
Practical questions

Logging and model terms

Confirm account region, workspace inference scope, model ID, live price, and whether full inference logging is enabled.

See the evidence

Energy practices

3/10↑

For the Alibaba Cloud Model Studio API; account region, workspace and selected model determine service route boundary, public documentation establishes the service or route but not its request-level physical footprint. Model Studio documents model selection and region/workspace-specific endpoints. These are route and workload choices, not measured resource reductions. Electricity sourcing is not mapped to this route.

See the evidence

This practices/transparency assessment covers the Alibaba Cloud Model Studio API; account region, workspace and selected model determine service route boundary. The sources establish how the service or endpoint is exposed and provide the request controls described in the demand component; they do not give a measured per-request energy, emissions or water value. The disclosure point reflects the stated operating boundary, not a product footprint, and company-wide electricity reporting is not attributed to this route.

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

The reviewed sources don’t confirm request-level electricity, emissions or water; the actual serving facility and its power mix are also not mapped to Alibaba Cloud Model Studio API; account region, workspace and selected model determine service route.

Reporting1/3
The reviewed documentation defines the Alibaba Cloud Model Studio API; account region, workspace and selected model determine service route boundary. It gives an operating-scope description, not a dated quantitative energy, carbon or water report for this route.
Electricity sourcing0/3
No reviewed source maps Alibaba Cloud Model Studio API; account region, workspace and selected model determine service route to a disclosed electricity mix or time-and-location-matched clean-power supply. The route's actual electricity use and emissions therefore remain unestablished.
Resource controls1/3
Model Studio documents model selection and region/workspace-specific endpoints. These are route and workload choices, not measured resource reductions.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

Model Studio offers multiple Qwen and third-party models; customer prompt data policy and training-data rights of each selected model are distinct questions.

See the evidence

User prompts, model-improvement settings, and the original training data are different evidence questions. The reviewed product documentation does not identify a fixed model version and complete training-data rights record for Alibaba Cloud Model Studio API; region, model, account type and optional log configuration determine handling., so this assessment remains unscored.

Exact model selection, release version, source inventory, permissions, post-training data, and creator-remedy scope remain unresolved.

Your data & privacy

7/10↑

Alibaba states Model Studio does not use customer business data to improve models without explicit consent. Default audit logs retain request metadata but not prompt/response content; inference logs with full content require manual enablement.

See the evidence

The platform publishes a default distinction between metadata-only audit logs and opt-in inference logs, and says customer business data is not used for model improvement without explicit consent. Regional endpoints, configured logs, and model-specific terms still matter to an actual deployment.

No numerical score assigned because the reviewed evidence doesn’t confirm the route-specific controls needed for one.

Log delivery, customer-managed retention, endpoint region, feature-specific terms, and whether an account has enabled full inference logging need confirmation.

Openness

2/10↑

This is a hosted service with a public interface but no documented self-hostable product runtime or weights in the reviewed sources.

See the evidence

The service provides a hosted product or API interface, while the reviewed product material does not expose the serving implementation and current model weights for independent deployment. This rates this service scope, not separately released model weights.

The score reflects service-level inspectability and control, not usefulness or model quality.

SDKs, APIs, or model families may have separate licenses and do not make this service itself self-hostable.

Worker protections

6/10↑

Alibaba publishes group workforce indicators, an Employee Rights Code, employee reporting channels and compliance processes; these describe Alibaba employees, not the AI data-labeling supply chain.

See the evidence

Alibaba’s ESG employee-development pages report workforce composition and employee participation indicators, while its integrity and governance pages describe code compliance, reporting channels, compliance processes, and board oversight. These are concrete group-level employee systems, but public detail on annotation, evaluation, content moderation, and infrastructure contractor conditions or outcomes remains limited. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 2 pay & conditions + 2 worker voice & remedy + 1 evidence & follow-through = 6/10. This grades documented worker safeguards, not a measured rate of mistreatment.

The reviewed pages don’t show AI-data subcontractor coverage, worker-level wage/hour outcomes, case counts or remediation outcomes for labor reports, or independent labor-audit results.

Pay & conditions2/3
Company ESG disclosures report workforce composition and employee participation indicators and describe employee-rights standards; this is concrete employee evidence but does not demonstrate coverage of AI data work or contractors.
Worker voice & remedy2/3
Alibaba describes employee reporting and escalation channels, privacy/non-retaliation protections, and dedicated compliance processes; public labor-specific case outcomes were not located.
Evidence & follow-through1/3
Governance materials describe compliance training and audit/control processes, but the reviewed public disclosures do not provide independent worker-level labor assurance or remediation results.
Workers rubric ↗

Military ties

7/10Not established↑

Qwen3.8’s released model licenses don’t spell out a military-use ban. Alibaba publishes stronger rules for its separate QwenWork hosted service; no Qwen3.8 military contract was established.

See the evidence

The Qwen3.8-27B release uses Apache 2.0, while the larger Qwen3.8 release has its own license. Neither reviewed release license carries the QwenWork hosted-service military restrictions. QwenWork prohibits specified weapons and military end uses and permits service enforcement, but that separate contract doesn’t spell out controls on downloaded Qwen3.8 weights. No Alibaba military contract or Qwen3.8 deployment was established in this bounded source review. 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 (1 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.

The reviewed QwenWork contract doesn’t show an Alibaba defense relationship or a companywide model restriction. Self-hosted Qwen3.8-27B and Qwen3.8-Max use separate licenses; undisclosed contracts, deployments, and enforcement outcomes remain unknown.

Use restrictions0/4
The reviewed Qwen3.8 release licenses do not impose a specific military-purpose ban. Restrictions in the separate QwenWork customer contract are not applied to these weights.
Enforcement & oversight0/3
Hosted-service suspension rights don’t show monitoring or enforcement over downloaded Qwen3.8 copies. No release-specific military oversight was established.
Relationship disclosure1/2
Alibaba publishes the release licenses and a separate hosted military-use policy, making the scope distinction inspectable. No military customer or deployment record is established.

The QwenWork hosted-service terms include product-specific use safeguards, but no Alibaba defense contract or military deployment was established in reviewed materials. Its Qwen3.8 model repositories have distinct licenses, so the QwenWork safeguards are not attributed to self-hosted weights or treated as evidence of a military relationship.

Military rubric ↗

BDS targets

Not listed↑

We did not find Alibaba Cloud / Qwen team among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

See the evidence

Alibaba Cloud / Qwen team is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Running downloaded weights locally is a different decision from paying the developer or a cloud host; check the host as well. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

More from Alibaba

All sources

Side by side