Alpha
Contact
Implement · Nebius (Token Factory)

Can you run it?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 64.4/100

This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

API integration

Nebius Token Factory is called with the standard OpenAI client libraries. The quickstart points the OpenAI SDK at https://api.tokenfactory.nebius.com/v1/.

Authentication & account setup

Public docs confirm API-key-based access via the OpenAI-compatible client libraries. Org/project key-scoping granularity is not documented, so confirm the exact setup in the Nebius console.

Region & ZDR configuration

A dedicated endpoint takes its region from the templates API at deployment. The Token Factory data-plane page documents base URLs for eu-north1 (Finland), eu-west1 (France) and us-central1, and the DPA pins dedicated endpoints to that region. Public endpoints show Region "Global" and the processing location can change without notice, so a region-specific base URL may stop working. Zero Data Retention is enabled per organisation in account settings, with a documented speed trade-off, and it also opts you out of Speculative Decoding. It is off by default.

Rate limits, tiers & quotas

Limits are dynamic and visible only in the console. The docs give an illustrative baseline of 60 requests and 400,000 tokens per minute. The limit rises by 20 percent when average use over a rolling 15-minute window reaches 80 percent, falls by a third at 50 percent or less, and is capped at 4x the base allocation, beyond which an Enterprise plan is required. Over the limit the API returns HTTP 429, though requests may still be served at lower priority (header x-ratelimit-over-limit: yes). Busy endpoints return HTTP 529. Dedicated endpoints have no rate limits.

Portability & exit

The DPA commits to deleting or returning Customer Personal Data on termination, at the customer's choice. An OpenAI-compatible API over a predominantly open-weight catalogue keeps served checkpoints portable. Serverless models are removed on dated notices with no automatic rerouting, and dedicated endpoints for removed models stay available. Nebius can delete fine-tuned and distilled models on three days' notice (Supplemental Terms 2.10).

How this scores

The ownership factors this domain covers, drawn from the one entry record.

3

ReliabilityDoes it stay up and stay secure?

Moderate

No inference SLA exists, and Supplemental Terms 7.4 says so expressly (no service level commitments, uptime guarantees or credits unless agreed in writing). Self-service dedicated endpoints carry no formal SLA and release capacity on any stop or incident. The status page shows a Token Factory component per region and two resolved Token Factory incidents in its 14-day window.

How this scores (AOI sub-dimensions)
Reliability3/5whether it stays up, with an SLA and status historyToken Factory has no inference SLA, and Supplemental Terms 7.4 (effective 2026-10-22) excludes one: Nebius "does not provide any service level commitments, uptime guarantees, or associated compensation for the Token Factory Service".
Security3/5the controls protecting your traffic and dataThe trust centre documents customer workload isolation (VPC, InfiniBand and Kubernetes), TLS in transit, storage encryption by default (with named exceptions), least-privilege access with MFA, vulnerability management and regular security assessments, a structured incident-response plan and a secure SDLC.
Compliance5/5which independent certifications and attestations it holdsTwo independent artefacts support a 5.
4

Doesn't extract your dataDo the binding terms keep your data and IP yours?

Weak

The binding Supplemental Terms (5.1(b), effective 2026-10-22) let Nebius use Input and Output by default to train smaller Speculative Decoding models, with an opt-out by onboarding form or email, and reserve absolute discretion to delete them without notice (5.3). Zero Data Retention exists only as an account-level opt-in. The Legal Quick Guide contradicts this in plain English; the contract governs.

How this scores (AOI sub-dimensions)
Data governance2/5retention, training-on-inputs and data ownershipSupplemental Terms 5.1(b) and 5.4 (effective 2026-10-22; Sec 7 of the legacy Terms) let Nebius use Input and Output by default to "train smaller Models used for Speculative Decoding" under a royalty-free, transferable, sub-licensable, worldwide licence.
Residency3/5where your data is processed and storedHeld at 3 (EU region for at least some workloads); 4 needs pinning for the main workloads.
What this means for adoptionData control is limited by default. The binding Token Factory Supplemental Terms (5.1(b), effective 2026-10-22) allow Nebius to train its smaller Speculative Decoding models on your Inputs and Outputs unless you opt out. The Legal Quick Guide tells readers that content is not used to train any model. Compliance is a strength, evidenced by a public Deloitte SOC 3 report and an SII-QCD ISO 27001 certificate. Two EU data-plane regions (Finland, France) are documented, but public endpoints are unpinned and the standard terms carry no inference SLA. For sensitive data, enable Zero Data Retention (it also stops Speculative Decoding) and use a dedicated endpoint in an EU region for residency.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Terms of serviceread2026-11-19
Nebius Token Factory Supplemental Terms (publication and effective date 2026-10-22), incorporated into the Nebius Services Agreement.
Terms of serviceread2026-11-19
Legacy Nebius Token Factory Terms of Service (publication date 2026-08-20).
Documentationread2026-11-19
Nebius Legal Quick Guide (non-binding; states that the Terms, DPA and Privacy Policy prevail).
Terms of serviceread2026-11-19
Nebius Services Agreement (effective 2026-10-22).
Data Processing Addendumread2026-11-19
Nebius Data Processing Addendum (effective 2026-11-18).
Subprocessorsread2026-11-19
Nebius Token Factory sub-processor list (effective 2026-09-23): 23 table rows and 20 distinct entities in three groups.
Securityread2026-11-19
Nebius Trust Center (static pages) lists SOC 2 Type II with HIPAA (report under NDA; auditor Deloitte; scope includes AI Cloud, AI Studio (now Token Factory) and Tracto AI), SOC 3 (public).
Third-party analysisread2026-11-19
Public SOC 3 report for Nebius BV, 'Security, Availability and Confidentiality + HIPAA Mapping', period April 01, 2025 to July 31, 2025, independent service auditor's report dated October 19, 2025 (Deloitte, per the trust-centre page and the report footer).
Third-party analysisread2026-11-19
ISO/IEC 27001:2022 certificate no.
Documentationread2026-11-19
Nebius AI Cloud regions documentation.
Slaread2026-11-19
Nebius SLA pages.
Slaread2026-11-19
Nebius public status page (status.nebius.com): All Systems Operational.
Documentationread2026-11-19
Nebius Token Factory model catalogue and per-model pages (rendered in a browser without login; curl gets HTTP 403 from a Cloudflare challenge).
Documentationread2026-11-19
Nebius Token Factory Model Deprecations notices.
Documentationread2026-11-19
Nebius Token Factory docs.
Documentationread2026-11-19
Nebius dedicated-endpoint billing-policy docs: 'A dedicated endpoint is considered active, accessible, and billable when at least one replica is running'; no charge when zero replicas run; 'Charges may vary depending on your custom contract or work order'.
Documentationread2026-11-19
Nebius Token Factory product page and quickstart: serverless inference 'through a familiar API' and dedicated endpoints 'on isolated capacity' with 'regional placement'.