Alpha
All entriesContact
Inference provider

Sakura Internet AI Engine

HQ
Japan
Serves
12 open model families
Pricing
per-token
API
OpenAI-compatible

Inference here is partly owned. Sakura's terms commit in writing not to use inputs, not to give them to model providers and not to train on them, which is a real baseline. They do not promise zero retention, do not fix the data location, and come with no SLA or DPA. Ownership would move to substantial if Sakura wrote Japan-only processing and a bounded retention period into the terms, published a processing agreement, and confirmed AI Engine inside its ISMS scope.

Do you really own it?
Partial
none·limited·partial·substantial·full
Analytical input: AOI D · 48/100
The four ownership factors

Floor-weighted, not averaged. Nothing is weak, but use & modify and data control are only moderate, so it misses the bar for substantial - strong on both use & modify and data control - and lands at partial.

1

Use and modify freelyCan you use it freely and leave without lock-in?

Moderate

Mostly Apache-2.0 and MIT models behind OpenAI and Anthropic compatible APIs, but no fine-tuning on the shared service, two closed models with no-fine-tune and no-distillation terms, a military-use ban (Art. 12(1)(vi)), and a dedicated option for Japanese corporations only (Private Edition Art. 3).

How this scores (AOI sub-dimensions)
Transparency & lock-in3/5how portable it is and how easily you can leaveOpenAI-compatible and Anthropic-compatible APIs over mostly open models with published licences, a manual that says all models are hosted by Sakura, no minimum term and a self-serve exit, plus a Private Edition dedicated option.
Cost3/5how the pricing model compares and how predictable it isClear public per-token and per-unit prices in yen, tax included, with a free allowance and no minimum term.
2

TransparencyAre the binding terms published, legible and independently checkable?

Moderate

Three binding terms documents are published, but they are Japanese only, there is no DPA or sub-processor list, certification scopes do not name AI Engine, and marketing claims (ZDR, Japan-only) are stronger than the terms.

How this scores
Not a scored AOI dimension. For a hosted provider, transparency is whether the binding terms are published, legible and were actually read - the read/unverified evidence below, not a certification. A strong rating here must trace to a retrieved binding document.
3

ReliabilityDoes it stay up and stay secure?

Moderate

Production service with a company-level security programme, but no SLA, most models in preview that can end without notice, and no AI Engine status history (manual 01-basics; terms Art. 11 of Private Edition).

How this scores (AOI sub-dimensions)
Reliability2/5whether it stays up, with an SLA and status historyServing is in production, but AI Engine is expressly outside the SLA (manual), Private Edition is best effort unless an SLA is written, the Sakura Cloud status page has no AI Engine component, and no incident history is published.
Security2/5the controls protecting your traffic and dataTemporarily stored inputs and outputs are encrypted (Art.
Compliance2/5which independent certifications and attestations it holdsSakura holds ISO 27001, ISO 27017, ISO 27018, ISMAP and Privacy Mark at company level, which would meet a score of 3 for the company.
4

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

Moderate

Art. 10(2) bars use of inputs, third-party provision and AI training on them, but retention is 'in principle not stored' with an undefined encrypted exception, outputs and RAG documents are not covered, and Japan-only processing is not contractual.

How this scores (AOI sub-dimensions)
Data governance3/5retention, training-on-inputs and data ownershipContractual no training and no use or third-party provision of inputs (Art.
Residency2/5where your data is processed and storedProcessing in Japanese data centres is stated three times in Sakura's own pages, and the operator is a Japanese company under Japanese law with no US CLOUD Act exposure.

How the AOI score is computed

The seven dimensions above, each scored 0 to 5, weighted and summed to the 0 to 100 headline. The score is the analytical input behind the ownership verdict, not the verdict itself.

DimensionScoreWeightPoints
Data governance3/50.2414.4
Compliance2/50.187.2
Residency2/50.166.4
Security2/50.145.6
Reliability2/50.124.8
Transparency & lock-in3/50.106.0
Cost3/50.063.6
HeadlineD · 48/100
Dossier coverageAssess 58%Implement 56%Use 93%Support 50%How complete our four-domain documentation is, a measure of our coverage, not of the model. Each domain links to its page.

Sources

Every rating traces to a primary document. Read means the text was verified; unverified means it is known to exist but has not yet been read.

DocumentWhat it grounds
Terms of serviceread2026-11-19
Sakura AI Engine service terms (さくらの AI Engine サービス約款, in force 2025-09-24).
Terms of serviceread2026-11-19
Sakura AI Engine Private Edition service terms (in force 2026-11-02).
Terms of serviceread2026-11-19
Sakura basic terms (基本約款, applied 2023-10-02).
Privacy Policyread2026-11-19
Sakura personal information protection policy (revised 2024-09-02): Privacy Mark and JIS Q 15001 system; no third-party provision of personal information without consent except to bound contractors, to protect life or property, or where law requires.
Securityread2026-11-19
Sakura security page lists the following.
Securityread2026-11-19
Sakura cloud service information security policy (2018-07-01, revised 2025-01-24): full virtualisation isolates each customer-created server's memory and network interface; Sakura does not monitor, edit or disclose customer data without permission except as its terms provide; two-step authentication for the control panel.
Securityread2026-11-19
Sakura information security check sheet PDF (updated 2026-11-13): certificate expiry dates (ISMS 2027-04-12, PCI DSS 2027-03-14, Privacy Mark 2028-07-10), policies, access control, periodic vulnerability scanning, annual internal audits, outsourcing of billing, invoicing and customer support to unnamed contractors with periodic security checks.
Securityread2026-11-19
Sakura Cloud ISMAP scope page (2026-06-30): registered service is Sakura Cloud IaaS in Tokyo zones 1 and 2 and Ishikari zones 1 and 2 (servers, storage, network, appliances).
Third-party analysisread2026-11-19
Independent auditor's SOC 3 report on Sakura's Ishikari data centre housing, colocation and common services: security and availability criteria, period 2025-06-01 to 2026-05-31, unqualified opinion dated 2026-07-31.
Third-party analysisunverified2026-11-19
Sakura states a SOC 2 Type 2 report (Ishikari data centre) and a SOC 2 Type 1 report (Sakura Cloud) exist and are disclosed to customers and prospects on request.
Data Processing Addendumunverified2026-11-19
No data processing agreement, GDPR addendum, sub-processor list or data-location statement appears on the terms index, the AI Engine product pages or the manual.
Securityread2026-11-19
Sakura transparency report page: reports on legal and other requests cover Rental Server, VPS, Sakura Cloud, Dedicated Server PHY, Domain and Housing.
Documentationread2026-11-19
The Sakura Cloud manual page on AI Engine service basics (updated 2026-11-11) says the service is outside quality assurance (SLA).
Documentationread2026-11-19
Sakura Cloud manual, chat model specification (2026-11-18): context length, max output, vision, tool-call and reasoning support per model (4,096 up to 1,048,575 tokens); OpenAI-compatible parameters, unsupported parameters ignored; about 5 minutes per request; preview models can change or end without notice.
Documentationread2026-11-19
The Sakura Cloud manual operation guide (2026-11-11) and Tips (2026-05-14) cover the RAG API and vector store, transcription limits (30 minutes or 30 MB) and speech limits.
Documentationread2026-11-19
The Sakura Cloud manual closed-models page (2025-12-02) says PLaMo and cotomi need an application that the model provider approves (about 7 business days), are outside the free plan and are for corporate accounts only.
Documentationread2026-11-19
Sakura Cloud manual, licences of served models (2026-11-18): gpt-oss-120b, llm-jp-3.1, Qwen3 family, Gemma 4 and MedLLM under Apache-2.0; Phi-4, e5, Whisper, GLM-5.3-Flash and DeepSeek-V4.1-Flash under MIT; Kimi-K2.7-Code under Modified MIT; PLaMo and cotomi under proprietary end-user terms.
Licenceread2026-11-19
PLaMo licence agreement (closed model via Sakura): use only inside AI Engine, no fine-tuning or quantisation (Art.
Licenceread2026-11-19
cotomi v3 usage conditions (closed model via Sakura): internal business use only, no hosting or SaaS to third parties without consent (Art.
Vendor announcementread2026-11-19
The Sakura AI Engine product page says 'input data is not trained on or stored', 'ZDR (Zero Data Retention) compatible' and 'model execution and communication all completed in domestic cloud'.
Vendor announcementread2026-11-19
Sakura AI top page FAQ: 'model execution, communication and storage are all completed on cloud infrastructure in Japan' and 'can be operated under Japanese law'.
Vendor announcementread2026-11-19
Sakura AI Engine Private Edition page: dedicated environment, closed-network connection supported, ZDR, flat monthly fee per GPU by quote, bring-your-own or fine-tuned models.
Slaread2026-11-19
The Sakura Cloud service status page (status.cloud.sakura.ad.jp) lists Cloud API per zone (Tokyo 1 and 2, Ishikari 1 to 3), websites, DNS, GSLB and load balancer appliances.
Documentationread2026-11-19
Sakura Cloud incident and maintenance notice policy (2025-02-20): announcement channels and criteria for Sakura Cloud resource types.
Documentationread2026-11-19
Sakura Cloud support page (2026-09-29): standard support free on weekdays 10:00 to 18:00 JST by e-mail form or reserved call-back; premium paid support 24 hours, first reply within 2 hours for faults.