Nebius

HostedGPU cloud

The Ultimate AI Cloud — Build and scale AI faster on a cloud engineered from silicon to API.

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: —
Usage; on-demand and dynamic preemptible spot; commitments up to 35% discount
Free tier: No
No card required.
Isolation: Virtual machine
hypervisor, or nothing at all
Regions: 10
Finland · Madrid, Spain · France · France · Israel · Kansas City, Missouri, US +4
Capabilities: 28 / 61
3 partial · 30 fail · 0 not assessed
Agent readiness: 11/11 · 9/11
read · drive, pre-login surface

Advertised for

AI training, fine tuning, data processing, batch/real time inference, interactive notebooks; VMs and managed Kubernetes/Soperator.

Built for

Developers, then technical

· REST/gRPC API, CLI, Terraform and Go/Python/JavaScript SDKs
· GPU-hour and infrastructure consumption pricing; operator-controlled VMs, Kubernetes and Soperator

01 Pricing Usage; on-demand and dynamic preemptible spot; commitments up to 35% discount

Tier	EntryUsage — on-demand GPU compute
Price	H100 $4.50 / H200 $5.40 / B200 $8.50 / B300 $9.50 per GPU-hour; dynamic spot available
Includes	Managed Kubernetes and Soperator software free; infrastructure consumption billed
GPU hours overage	$4.5/h
Storage overage	$0.0147/GB

GPU-hour; CPU instance-hour; storage GiB-month·Card required: No·nebius.com

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

Desktop public pages combine oversized navy sans-serif headlines, lime branding and luminous abstract imagery with polished business layouts; documentation switches to a charcoal header and pale-blue, card-based service directory.

Corporate

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Virtual machinehypervisor, or nothing at all

Persistence

Persistent VM disks/shared FS/object storage; Devlab workspace persists stop/restart; endpoint disk removed on stop/delete.

Snapshots / forks

Yes

Resources & limits

Storage

Not documented

Limits & quotas

VM, storage and InfiniBand quotas count throughout VM lifecycle, even while stopped; increase requests depend on tenant capacity.

GPU

Yes

Access

Deploy interface

dashboardclisdkapicontainer-imagetemplate

SDK languages

GoPythonjavascript/typescript

Network & secrets

Egress controls

pass

Secrets

SecretStash (formerly MysteryBox) + KMS

Bring your own cloud

Placement & use

Jurisdiction

Nine public region IDs in Finland, Spain, France, Israel, US and UK; one private Iceland region for existing deployments.

Advertised workloads

AI training, fine-tuning, data processing, batch/real-time inference, interactive notebooks; VMs and managed Kubernetes/Soperator.

04 Capabilities 28 pass · 3 partial · 30 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 7/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Partially supported

GPU computeGPU-backed instances available.

Supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 5/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Not supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 6/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Not supported

Private container registryHosted private image registry.

Supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 1/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Not supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Partially supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 2/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 1/6

Scheduled tasksCron / scheduled job primitive.

Partially supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 6/9

Built-in authPlatform-provided authentication / IAM for workloads.

Supported

SSO / SAMLEnterprise single sign-on.

Supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

7 full · 4 partial · 100% of applicable checks

llms.txt
Supported
“https://nebius.com/llms.txt — Substantive apex directory plus extensive docs index; full credit under rubric v3. Confidence: high.”
llms-full.txt
Supported
“https://docs.nebius.com/llms-full.txt — Complete 4.6MB documentation corpus fetched; bounded title/source index retained. Confidence: high.”
robots.txt AI policy
Partially supported
“https://nebius.com/robots.txt — User-agent * Allow /; no explicit major-AI-UA directives. Confidence: high.”
JSON-LD
Partially supported
“https://nebius.com/ — Corporation, WebSite and WebPage JSON-LD; no Product/SoftwareApplication offers. Confidence: high.”
Sitemap
Supported
“https://nebius.com/server-sitemap.xml — Nontrivial URL sitemap; sitemap index also points to docs sitemap. Confidence: high.”
Meta tags
Supported
“https://nebius.com/ — The Ultimate AI Cloud; descriptive title, description and OG metadata. Confidence: high.”
Markdown negotiation
Supported
“https://docs.nebius.com/overview/regions — Accept: text/markdown serves raw markdown from docs page; apex remains HTML. Confidence: high.”
Content efficiency
Partially supported
“https://nebius.com/ — Landing raw HTML 402909 bytes, script/style excluded, tags stripped and entities unescaped, whitespace normalized: readable text ratio 4.872%; partial per rubric. Recommendation text saying before normalization is a wording error: measurement is after normalization. Confidence: medium.”
Docs discoverable
Supported
“https://nebius.com/ — Developers navigation and Tech docs links to docs.nebius.com. Confidence: high.”
Machine-readable pricing
Supported
“https://nebius.com/prices — Structured GPU/CPU/storage rate tables. Confidence: high.”
No anti-bot wall
Partially supported
“https://api.nebius.cloud/openapi.json — Plain OpenAPI GET returned 403 error code 1010, recovered through foxcrawl 200. Other sampled public pages fetched cleanly. Confidence: high.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

9/11

8 full · 1 partial · 82% of applicable checks

Public API
Supported
“https://docs.nebius.com/rest-api/index.md — Documented REST and gRPC APIs. Confidence: high.”
OpenAPI spec
Supported
“https://docs.nebius.com/rest-api/reference.md — Valid browser-fetched OpenAPI 3.0.3 with 443 paths; bounded parsed extract retained. Confidence: high.”
MCP server
Supported
“https://raw.githubusercontent.com/nebius/mcp-server/refs/heads/main/README.md — Remote documentation MCP and uvx-installable official beta CLI-operations MCP. Confidence: high.”
SDK packages
Supported
“https://docs.nebius.com/sdk/index.md — Go, Python, JavaScript official SDKs. Confidence: high.”
Auth documented
Supported
“https://docs.nebius.com/rest-api/authentication.md — Bearer tokens, 12-hour user token lifetime, service-account authorized-key/JWT instructions. Confidence: high.”
Self-serve credentials
Supported
“https://docs.nebius.com/rest-api/authentication.md — After human account/billing bootstrap, CLI programmatic key upload and JWT-to-token issuance documented; no anonymous self-registration claim. Confidence: medium.”
Webhooks
Not supported
“https://docs.nebius.com/llms-full.txt — No webhook hits in complete documentation corpus. Confidence: high.”
CLI tool
Supported
“https://docs.nebius.com/cli/index.md — Official CLI. Confidence: high.”
Error model
Supported
“https://docs.nebius.com/rest-api/errors.md — JSON code/message body and detailed gRPC/HTTP status mapping. Confidence: high.”
Rate limits documented
Not supported
“https://docs.nebius.com/rest-api/errors.md — 429 describes resource quota exhaustion, not documented API request rates/response headers; corpus search only incidental limits. Confidence: medium.”
Agent config files
Partially supported
“https://docs.nebius.com/docs-ai.md — Documented MCP file configurations for VS Code/Cursor; linked agents.md is proposed and 404; no multiple config/skill discovery surfaces. Confidence: high.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 2

GitHub Copilot GitHub
Supported
“Using VSCode Copilot: ensure Copilot extension installed; add server; open Chat panel and select Agent mode.”
Source github.com
Cursor Anysphere
Supported
“Cursor and other clients: documented mcpServers configuration using https://docs.nebius.com/mcp. Documentation search only, not cloud operations.”
Source docs.nebius.com

Plausible compatibility 15

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

Aider
Amp
Antigravity
Claude Code
Codex CLI
Devin
Droid
Gemini CLI
Goose
Hermes Agent
Kilo Code
Kiro CLI
OpenCode
Pi
Qwen Code

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 14

ISO/IEC 27001
certifiedhosted
“ in ISO/IEC 27001 Nebius is certified for compliance with ISO/IEC 27001:2022, a globally recognized standard for information security management. This certification, conducted by an independent external third-party auditor, demonstrates our commitment to maintaining robust security practices across all levels of our organization. At the core of this certification is our Information Security Management System (ISMS), which defines how Nebius continuously manages information security in a comprehensive and systematic way. This certification demonstrates that Nebius has implemented comprehensive measures to protect personal data, comply with global privacy regulations and uphold the highest standards of trust and accountability. To meet the requirements of ISO/IEC 27001:2022, Nebius: Conducts regular, systematic evaluations of information security risks, considering evolving threats, vulnerabilities and business impacts. These risk-based approach guides our decision-making and ensure proactive risk mitigation. Implements a comprehensive set of security controls and documented customized procedures, aligned our technical architecture, operational needs and customer expectations. Maintains an overarching management framework to ensure these controls remain effectiv”
Source nebius.com
ISO/IEC 27701
certifiedhosted
“ in ISO/IEC 27701 Nebius is certified for compliance with ISO/IEC 27701:2019, the international standard for Privacy Information Management Systems (PIMS). This certification extends our ISO/IEC 27001 program with privacy-specific requirements and controls for managing personally identifiable information (PII). Nebius has been certified as both a PII controller and a PII processor, reflecting our responsibility to protect personal data across different service and operational contexts. This dual certification demonstrates that Nebius can securely manage its own data processing activities as a controller and also process customer data responsibly on their behalf as a processor. To meet the requirements of ISO/IEC 27701, Nebius: Extends its Information Security Management System (ISMS) into a Privacy Information Management System (PIMS). Applies privacy-specific controls to the collection, processing, storage, and deletion of PII. Defines clear responsibilities and accountability measures when acting as both a controller and a processor. Implements processes to support compliance with global privacy regulations, including the GDPR and similar frameworks. Ensures transparency, data subject rights support, and customer trust through independently audited privacy p”
Source nebius.com
SOC 2 Type II
certifiedhosted
“ in SOC 2 Type II SOC 2 Type II (Service and Organization Controls) is a reporting framework developed by the American Institute of Certified Public Accountants (AICPA) under the SSAE 18 standard. It evaluates how a service organization’s controls align with the Trust Services Criteria, which include security, availability and confidentiality. Access the report Nebius undergoes regular independent SOC 2 Type II audits covering its products, systems and infrastructure. These audits are conducted by an accredited third-party firm that evaluates the design and operational effectiveness of our controls over a defined audit period. The resulting SOC 2 Type II report provides an independent attestation of the controls Nebius has implemented to protect customer data. Customers can use the SOC 2 Type II report to better understand and assess the risks associated with using Nebius services during the covered audit period. You can also use SOC 3 report to get a summarized version of the SOC 2 Type II report. The report is available upon signing an NDA. Fill out this form to sign the NDA and access the report. HIPAA The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a U.S. federal law that establishes requirements for safeguarding the privacy and ”
Source nebius.com
CSA STAR
self-attestedhosted
“Log in CSA STAR Level 1 CSA STAR (Security, Trust, Assurance, and Risk) is a cloud security assurance program developed by the Cloud Security Alliance (CSA). It helps cloud providers demonstrate the security of their services through a standardized framework built on the Cloud Controls Matrix (CCM). CSA STAR gives customers a standardized way to evaluate a cloud provider’s security controls. By publishing our CSA STAR Level 1 assessment in the CSA STAR Registry, Nebius provides transparent, standardized information that supports customer security reviews and vendor due diligence. CSA STAR Level 1 is based on a self-assessment. Nebius completed the CSA Consensus Assessments Initiative Questionnaire (CAIQ), which maps our security controls against the CSA Cloud Controls Matrix (CCM). The completed assessment is published in the CSA STAR Registry . Questions and answers What is CSA STAR Level 1? CSA STAR stands for Security, Trust, Assurance, and Risk, a cloud assurance program created by the Cloud Security Alliance (CSA). It is designed to help cloud service providers demonstrate the security of their services and help customers assess cloud security risks. At Level 1, the provider completes the Consensus Assessments Initiative Questionnaire, which is based on t”
Source nebius.com
DORA
self-attestedhosted
“Nebius aligns with EU uniform ICT risk management requirements for the financial sector”
Source nebius.com
HIPAA
self-attestedhosted
“SOC 2 Type II With HIPAA”
Source nebius.com
ISO 22301
certifiedhosted
“ISO 22301 Nebius is certified for compliance with ISO 22301:2019, the international standard for Business Continuity Management Systems (BCMS). This certification demonstrates our ability to prepare for, respond to and recover from disruptive incidents while maintaining the continuity of critical services. At the core of ISO 22301 is the Business Continuity Management System (BCMS), which ensures that Nebius can anticipate risks, minimize the impact of incidents, and continue to deliver essential services to customers even under adverse conditions. To meet the requirements of ISO 22301, Nebius: Identifies potential threats and assesses their impact on business operations. Maintains tested plans for incident response, disaster recovery, and service continuity. Defines roles and responsibilities to ensure rapid and coordinated action during disruptions. Regularly tests, reviews, and improves continuity processes to remain resilient against evolving risks. This certification reinforces Nebius commitment to operational resilience, assuring customers that our AI cloud services remain available and reliable even in the face of unexpected events. pdf ISO 22301:2019 Questions and answers Why is ISO 22301 certification important? ISO 22301 provides a globally recognize”
Source nebius.com
ISO 27799
self-attestedhosted
“hy Nebius Developers Pricing Company Investors Contact sales Log in ISO/IEC 27799 ISO/IEC 27799 is an international standard that provides guidelines for managing information security in healthcare environments. It helps healthcare organizations and service providers apply the principles of ISO/IEC 27001 to systems that process personal health information (PHI). Nebius aligns with the guidance of ISO/IEC 27799 to support the confidentiality, integrity and availability of health data across its services. The standard offers a framework tailored to the specific risks and regulatory requirements associated with health informatics, bridging the gap between general information security practices and the unique needs of the healthcare sector. By following ISO/IEC 27799, Nebius strengthens its security controls for health-related data, supports compliance with applicable legal and regulatory obligations, and reinforces trust with customers, partners and healthcare stakeholders. pdf ISO 27799:2016 Questions and answers What is ISO/IEC 27799? ISO/IEC 27799 is a healthcare-specific security standard that provides guidance on protecting personal health information (PHI) in line with ISO/IEC 27001. It helps healthcare organizations implement information security best prac”
Source nebius.com
ISO/IEC 27018
self-attestedhosted
“ in ISO/IEC 27018 Nebius aligns with ISO/IEC 27018:2019, the internationally recognized standard for the protection of personal data in cloud computing. This standard provides guidelines based on ISO/IEC 27002 and ISO/IEC 29100, with a specific focus on safeguarding Personally Identifiable Information (PII) in public cloud environments. Following ISO/IEC 27018 demonstrates our commitment to protecting personal data entrusted to us, ensuring that it is handled responsibly and transparently in line with global best practices. To meet the requirements of ISO/IEC 27018, Nebius: Implements controls designed specifically to protect PII in cloud environments, ensuring confidentiality, integrity, and availability of personal data. Maintains strict processes for obtaining and documenting customer consent and for limiting data processing to agreed purposes. Provides transparency around where and how personal data is processed and ensures customer control over its use. Applies additional safeguards to support compliance with privacy regulations and reinforce trust in cloud services. Our adherence to ISO/IEC 27018 underlines Nebius role as a responsible cloud provider, enabling customers to use AI cloud services with confidence that their data is processed securely and in”
Source nebius.com
ISO/IEC 27032
self-attestedhosted
“ in ISO/IEC 27032 Nebius aligns with the guidelines of ISO/IEC 27032:2012, an international standard focused on cybersecurity — the protection of information, systems and digital interactions across the broader cyberspace. This standard provides a framework for managing cybersecurity risks that go beyond traditional information security, addressing threats that stem from interconnected systems and external environments. ISO/IEC 27032 complements our existing security management practices by enhancing our ability to detect, prevent and respond to cyber threats across networks, applications and services. It promotes coordinated efforts between stakeholders, including internal teams, partners and external entities, to ensure a resilient and trusted digital ecosystem. To align with the guidance of ISO/IEC 27032, Nebius: Identifies and assesses cybersecurity risks related to digital services, communication networks, and third-party dependencies. Strengthens defenses against threats such as malware, phishing and unauthorized access through layered technical and organizational measures. Establishes clear protocols for incident response, information sharing and stakeholder collaboration in the event of a cybersecurity incident. By incorporating ISO/IEC 27032 guidance ”
Source nebius.com
NIS 2
self-attestedhosted
“Nebius aligns its cybersecurity practices with European Union’s cybersecurity law”
Source nebius.com
SOC 3
certifiedhosted
“3 SOC 3 (Service and Organization Controls 3) is a high-level report that confirms Nebius’ compliance with the AICPA’s Trust Services Criteria. It is designed for broad distribution and offers a high-level summary of the same controls evaluated in the SOC 2 report. Our SOC 3 report reflects our ongoing commitment to transparency and trust. The report confirms that Nebius systems have been independently audited and meet rigorous standards for protecting customer data and ensuring reliable service. pdf SOC 3 Report Relevant to Security, Availability and Confidentiality + HIPAA Mapping Questions and answers Does SOC 3 include customer-specific data or findings? No, SOC 3 is a general-use report and does not include any customer-specific information or detailed audit results. What’s the difference between SOC 2 and SOC 3? SOC 2 is a detailed, confidential report intended for customers under NDA. SOC 3 is a summarized version of the same audit, designed for public consumption. Can SOC 3 report be shared with external parties? Yes, SOC 3 is meant to be publicly distributed and can be shared freely. What Nebius products are within the scope of the audit? The audit includes Nebiius AI Cloud, AI Studio (now Nebius Token Factory) and Tracto AI within its scope, confirmi”
Source nebius.com
CCPA
self-attestedhosted
“GDPR and CCPA-compliant policies and practices”
Source nebius.com
GDPR
self-attestedhosted
“GDPR and CCPA-compliant policies and practices”
Source nebius.com

Regions 10

Finlandeu-north1
Madrid, Spaineu-south1
Franceeu-west1
Franceeu-west2
Israelme-west1
Kansas City, Missouri, USus-central1
Woodbury, Minnesota, USus-north1
United Kingdomuk-south1
United Kingdomuk-south2
Iceland; only existing deploymentseu-north2

10 region IDs, not 6 datacenter locations. Service/GPU availability differs; preserve matrix evidence.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: Amsterdam, Netherlands
Founded: —
Team size: Not disclosed
Hiring: 381 open roles

Notable people

Arkady Volozh Founder, Chief Executive Officer, Board member

Activity

Last release: Q3 2026 release notes linked from homepage; continuous managed cloud; CLI/tunnels/observability component versions not cloud releases nebius.com
Last blog post: 2026-10-13: Open-source NVIDIA Run:ai available in Nebius Applications (rendered blog) nebius.com

Presence 8

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from nebius.com's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All GPU cloud products →