Short answer. No Plugsky region is live in Japan. The nearest live region is ap-southeast-1 in Singapore, so Japanese personal data would leave Japan unless you choose a contract-only private VPC, on-premises or air-gapped deployment. Plugsky does not claim a Japanese data centre, office, ISMAP registration or residency guarantee.
2027 planning guide — evidence checked 20 November 2026.
Availability at a glance
Japan is an APAC market served from outside the country. That is the first thing a procurement team needs to know, because it changes the APPI analysis and the latency plan. The table separates the nearest live region from the contract-only routes.
| Option | What is available | Status | Buyer note |
|---|---|---|---|
| Live region in Japan | None | not claimed | No Japanese region is live. |
| Nearest region | ap-southeast-1, Singapore | nearest | Closest live region; a cross-border transfer from Japan. |
| Private VPC | Dedicated endpoint in a live region; location agreed in writing | contract | Scope, network boundary and price are agreed in writing. |
| On-premises | Plugsky runtime in your facility | contract | Hardware, updates and support are part of the order. |
| Air-gapped | No outbound connectivity | contract | Update and support paths are designed into the contract. |
| Japanese residency guarantee | Only what the DPA and order form state | contract | Singapore is not Japan; no blanket guarantee is made. |
| Japanese office or data centre | None claimed | not claimed | No office, subsidiary or owned facility in Japan is claimed. |
Status key. live means production traffic today; nearest means the closest live region, not a local presence; contract means a signed order; not claimed means no claim is made. No local row is marked live because no local region is live.
What Singapore means for a Japanese data transfer
An enterprise LLM API means a contracted inference endpoint with defined processing location, access controls and deletion terms. It is not a synonym for a local data centre.
Singapore is a live APAC region, but it is not Japan. A Japanese controller that sends personal data there is making a cross-border transfer under the APPI. The transfer needs a lawful route: consent, a destination the Personal Information Protection Commission treats as adequate, or another permitted mechanism. The EU and the UK are covered by adequacy; if Singapore is not covered for your data, plan for consent or a contractual route.
That is a legal question before it is an engineering one. Ask for the DPA, the subprocessor list and the transfer terms, then map them onto your own notices and consent language. The data residency guide explains why a processing region is not the same as a residency guarantee.
If the transfer is unacceptable, the contract routes are the answer: a private VPC in a boundary you control, an on-premises deployment in your own facility, or an air-gapped installation with no outbound connectivity. All three are scoped and priced under contract.
Japanese framework: APPI, ISMAP and METI/MIC guidance
This is a buyer's map, not legal advice. Verify with counsel before relying on it.
APPI and the PPC
The Act on the Protection of Personal Information was enacted in 2003 and substantially amended in 2020 and 2022. The PPC supervises it and publishes guidelines and English reference materials. The APPI covers personal information, pseudonymised information and sensitive personal information, and it separates domestic use from cross-border transfer.
For an API buyer the practical questions are: what personal information is in the prompt, is it sensitive, who is the handling operator, where is it stored and who can access it. A vendor questionnaire and a DPA answer those questions. A badge does not.
ISMAP
ISMAP is the Japanese government's cloud security assessment and registration programme. Many public-sector procurements treat registration as a gate, and vendors often need to be listed before a tender can proceed. Plugsky does not claim ISMAP registration.
If your buyer is a ministry, agency or public body, resolve the ISMAP question before a technical pilot. If the buyer is a private company, ISMAP may still appear as a supplier requirement. Treat it as a qualification gate, not a marketing line.
METI and MIC AI Guidelines
METI and MIC published the AI Guidelines for Business in April 2024 and have updated them since. They are non-binding soft law, aimed at helping companies govern AI risk, transparency and human oversight. They are not a certification and do not create a safe harbour.
Use them as a checklist in vendor review. If your use case affects people, document the risk assessment, the human review step and the incident path. Plugsky can supply technical information, but the assessment remains yours.
A procurement path for Japanese buyers
Japanese enterprise reviews often run through a systems integrator, with legal and security in parallel. A sequence that works:
- Map the data and the transfer. Decide whether personal information leaves Japan and on what route.
- Request the DPA, subprocessor list and transfer terms. Check whether Singapore is acceptable for your data subjects.
- Check the qualification gates: ISMAP for public procurement, sector rules for finance and health.
- Choose the deployment. Shared Singapore region is fastest; private VPC, on-premises and air-gapped are contract-only.
- Pilot one workflow from Tokyo or Osaka and measure p95 latency before scaling.
The security procurement guide lists the documents. Self-serve pricing is published on the pricing page; private deployment is quoted. Engineers can test the OpenAI-compatible endpoint through the documentation.
Where the Japanese demand is
Two cities account for most of the conversations. No Plugsky office is claimed in either.
Tokyo: finance, manufacturing headquarters and government
Tokyo concentrates financial services, manufacturing headquarters, media, technology and the central government. Buyers are rigorous about vendor stability and often route procurement through a systems integrator. APPI transfer terms and ISMAP eligibility come up earlier than model benchmarks. A Japanese-language contract and a local support contact are common expectations, and neither is claimed here, so confirm what the buyer will accept. The next step is a written architecture review that names the Singapore region, the transfer route and the qualification gates, with your SIer and counsel in the room.
Osaka: manufacturing, pharmaceuticals and logistics
Osaka and the Kansai region combine manufacturing, pharmaceuticals, chemicals and logistics. Workflows are document-heavy and operational: quality records, supplier documents, maintenance and customer service. Kansai buyers often start with a department-level pilot before a group-wide rollout, and they expect the pilot to be measured against a defined baseline. Cross-border latency to Singapore is the main technical constraint, so measure p95 from your own network before committing. Start with one bounded document workflow, keep sensitive personal information out of the pilot where possible, and expand only after quality and latency are proven.
Local search phrases to validate
These are research candidates for Japanese-language demand, not approved copy. No volume or ranking is claimed.
| Phrase | English gloss | Likely intent |
|---|---|---|
| 国内LLM API | domestic LLM API | Data-location-led |
| プライベートAI 構築 | private AI deployment | Enterprise build |
| LLM オンプレミス | on-premises LLM | Infrastructure-led |
| 生成AI API 企業 | generative AI API for enterprises | B2B research |
| 機密情報 生成AI | confidential data and generative AI | Security-led |
| APPI 対応 生成AI | APPI-compliant generative AI | Compliance-led |
| ISMAP 生成AI | ISMAP generative AI | Public-sector procurement |
| 低遅延 LLM API | low-latency LLM API | Performance-led |
Validate with a native reviewer; not published as localized copy.
What we did not verify
- No Japanese customer, reference or case study is claimed.
- No Japanese office, subsidiary or facility is claimed in Tokyo or Osaka; local staffing is not confirmed.
- No Japanese region is live, and no Japanese data centre is claimed. Singapore is not Japan.
- No ISMAP registration, ISO 27001 certification or SOC 2 attestation. SOC 2 is described as readiness or in progress.
- No Japanese-language support, contract or user interface verified. Localization is pending.
- No measured latency from Japanese networks and no benchmark against other providers.
- No validated search volume or native review for the phrases above.
Frequently asked questions
Is there a Plugsky region in Japan?
No. No Plugsky region is live in Japan. The nearest live region is ap-southeast-1 in Singapore, and private VPC, on-premises and air-gapped deployments are contract-only.
Does APPI allow personal data to be sent to Singapore?
It depends on the transfer route. APPI requires a lawful basis for cross-border transfer, and the PPC maintains a list of destinations it treats as adequate. The EU and UK are covered by adequacy; if Singapore is not covered for your data, you need consent or another permitted route. Counsel must confirm.
Is Plugsky ISMAP registered?
No. ISMAP registration is not claimed. ISMAP is the Japanese government cloud security assessment programme, and many public-sector procurements treat it as a gate. If your tender requires ISMAP, resolve that before a technical pilot.
Which deployments are contract-only?
Private VPC, on-premises and air-gapped deployments are contract-only. They are scoped, priced and supported under a signed agreement, and they are not available from the self-serve checkout.
Does Plugsky guarantee that data stays in Japan?
No. No Japanese region is live, so there is no Japanese processing location to guarantee. Residency is only what the signed DPA and order form state, and Singapore is not Japan.
Are the METI and MIC AI Guidelines mandatory?
The AI Guidelines for Business are non-binding soft law. They set expectations for governance, risk assessment and transparency, and buyers often use them in vendor review. They are not a certification and do not replace your own assessment.
How should we test latency from Japan?
Run a pilot from your Tokyo or Osaka network against the Singapore region and measure p50 and p95 for your own prompts. Cross-border latency is the main constraint. No Japanese latency benchmark is published, and this page makes no millisecond claim.
Sources
Last checked 20 November 2026.
- Personal Information Protection Commission, laws and policies — checked 20 November 2026.
- Act on the Protection of Personal Information, English translation — checked 20 November 2026.
- ISMAP, Japanese government cloud security assessment — checked 20 November 2026.
- METI and MIC, AI Guidelines for Business Ver 1.0 — checked 20 November 2026.
For the wider product picture, see sovereign AI. For key custody, read the BYOK page.
Resolve the transfer and ISMAP questions first
Then decide whether Singapore is acceptable or whether the workload needs a contract-only deployment.
Request architecture review