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.
API integration
The base URL is https://api.ai.sakura.ad.jp. The API reference (v1.0.1) documents OpenAI-compatible /v1/chat/completions, /v1/responses, /v1/embeddings, /v1/audio/transcriptions and /v1/audio/speech, and an Anthropic-compatible /v1/messages.
The product page says only one preview model is available on the Messages API and names it as Kimi-K2.6, while the price list and manual list Kimi-K2.7-Code. Check the console for what is live.
Compatibility is partial. Usable chat parameters are model, messages, max_tokens, temperature, stream, tools, tool_choice, response_format, reasoning_effort and chat_template_kwargs. Others (top_p, top_k, stop, seed, n, logprobs, max_completion_tokens) are silently ignored. A request is cut off after about 5 minutes. The Responses API has no image input or multi-turn yet. Reasoning tokens count against max_tokens.
Authentication and account setup
Access needs a Sakura member ID (phone-number verification) and a Sakura Cloud project with a registered credit card. Account tokens are then issued in the AI Engine console. Tokens may not be shared or lent (article 11).
The contract, notices and support are in Japanese (basic terms articles 3 and 4). Closed models (PLaMo, cotomi) need a corporate account and an application that the model provider approves in about 7 business days. Private Edition is by order form and bank transfer, for Japanese corporations only.
Region and residency configuration
There is no region parameter, no ZDR switch and no data-location setting to configure. Retention and location are whatever the terms and documentation say.
A private route is documented: enable a service endpoint gateway on the Sakura Cloud switch and tick api.ai.sakura.ad.jp. Service policies can restrict who in an organisation creates resources. For Private Edition, closed-network connection is not included unless it is written in the order form (article 2(4)).
Portability and exit
There is no minimum term and cancellation is by notice (articles 7 and 8), but the plan cannot be cancelled until every account token and every RAG document is deleted. Documents can be listed, fetched and deleted through the API.
The open models served can be run elsewhere, and the OpenAI-compatible surface makes a swap simple. The two closed models run only on Sakura. Private Edition has a two-month or one-year initial term with no cancellation inside it, and the shared AI Engine contract cannot be cancelled while it runs (article 5). On termination Sakura deletes the customer's model and related data within a reasonable period, with backups and legally retained data removed in turn (article 9(5)).
The ownership factors this domain covers, drawn from the one entry record.
3
ReliabilityDoes it stay up and stay secure?
ModerateProduction 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.
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
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.