France · 2027 planning guide

Private LLM hosting in France for GDPR-bound buyers

French buyers want EU processing, a clean CNIL story and a contract that survives a public-sector or regulated review. No Plugsky region is live in France. Frankfurt is the nearest live EU region, and private VPC, on-premises and air-gapped deployments are contract-only.

Short answer. No Plugsky region is live in France. The nearest live region is eu-central-1 in Frankfurt, inside the EU, so inference stays in the EU but the processor chain and any subprocessor access still need documentation. Private VPC, on-premises and air-gapped deployments are contract-only. Plugsky does not claim a French data centre, office, SecNumCloud qualification or residency guarantee.

2027 planning guide — evidence checked 20 November 2026.

Availability at a glance

France is an EU market without a French Plugsky region. That is a different proposition from Germany, and the page should not blur the two. The table separates the nearest live region from the contract-only routes.

Table 1. Plugsky availability for French buyers, checked 20 November 2026.
OptionWhat is availableStatusBuyer note
Live region in FranceNonenot claimedNo French region is live.
Nearest regioneu-central-1, FrankfurtnearestClosest live region; inside the EU, outside France.
Private VPCDedicated endpoint in a live region; location agreed in writingcontractScope, network boundary and price are agreed in writing.
On-premisesPlugsky runtime in your facilitycontractHardware, updates and support are part of the order.
Air-gappedNo outbound connectivitycontractUpdate and support paths are designed into the contract.
French residency guaranteeOnly what the DPA and order form statecontractFrankfurt is not a French location; no blanket guarantee is made.
French office or data centreNone claimednot claimedNo office, subsidiary or owned facility in France 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 Frankfurt changes, and what it does not

Private LLM hosting means running inference under a contract that fixes the processing location, access and deletion terms. It is not a synonym for a local data centre.

Frankfurt is in the EU, so a French controller is not sending personal data to a third country for the inference itself. That removes one layer of paperwork: no EU standard contractual clauses are needed for a purely intra-EU transfer. It does not remove the Article 28 processor agreement, the record of processing or the need for a DPIA on a high-risk use case.

It also does not make the service French. Support access, logging, billing and subprocessors can sit outside France, and some may sit outside the EU. Ask for the subprocessor list and the transfer analysis, and read them with the DPA. The data residency guide explains why a processing region is not the same as a legal guarantee.

For workloads that cannot accept an EU-but-not-French location, 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.

French framework: GDPR, CNIL and the AI Act

This is a buyer's map, not legal advice. Verify with counsel before relying on it.

GDPR and French data protection law

The GDPR applies directly in France, and the Loi Informatique et Libertés, law 78-17 of 6 January 1978 as amended, adds national provisions. The CNIL is the supervisory authority. For an API buyer the familiar articles apply: 28 on processors, 32 on security, 35 on impact assessments and 44 to 49 on transfers.

French procurement reviews tend to focus on practical accountability: records, retention, information and security. A vendor questionnaire that answers those points is more useful than a certification logo. Ask for the DPA, the subprocessor list and the deletion terms, and keep the answers with your records.

CNIL AI guidance

The CNIL has published AI recommendations and guidance on generative AI, covering purpose, data minimisation, transparency, human oversight and the reuse of data for model training. They are guidance, not a certification scheme. The CNIL does not approve vendors, and no CNIL approval is claimed here.

Use the recommendations as a checklist for your own use case. If the API processes personal data, ask whether prompts or outputs are used for training, how long they are retained and how access is logged. The answers belong in the DPA and the product documentation, not in a sales deck.

The EU AI Act and French procurement

The AI Act, Regulation (EU) 2024/1689, applies in France like anywhere else in the EU. General-purpose model obligations have applied since 2 August 2025. The original timetable sets most Annex III high-risk duties from 2 August 2026, but that timetable has been the subject of amendment proposals, so confirm the current text and your role.

French public and regulated buyers may also ask about SecNumCloud, the ANSSI qualification for cloud services. Plugsky does not claim SecNumCloud. If a tender makes it mandatory, resolve that gate before a pilot; if the buyer accepts an alternative, document the risk decision. Do not let a slide imply a qualification that does not exist.

A procurement path for French buyers

French reviews often combine legal, security and business continuity in one committee. A sequence that works:

  1. Map the data and the role: controller, processor or joint controller, and whether personal data is in prompts or outputs.
  2. Request the DPA, subprocessor list and security package. Check whether support access sits outside the EU.
  3. Run a DPIA if the use case is high risk, and document the human review step.
  4. Check sector gates: SecNumCloud for some public buyers, financial outsourcing rules, health-data rules.
  5. Choose the deployment and test it. Shared EU region is fastest; private VPC, on-premises and air-gapped are contract-only.

The security procurement guide lists the documents. Self-serve pricing is published on the pricing page; private deployment is quoted because scope drives cost. Engineers can test the OpenAI-compatible endpoint through the documentation before legal review closes.

Where the French demand is

Three cities carry most of the conversations. No Plugsky office is claimed in any of them.

Paris: finance, luxury, public sector and media

Paris concentrates banking, insurance, luxury groups, media and much of the public sector. Buyers are used to formal tenders and will ask for the DPA, the subprocessor list and a security pack before a technical workshop. Tenders may also ask for a French-language contract and a named security contact, so confirm what the buyer requires. Frankfurt is close enough that latency rarely decides the deal; the transfer and qualification questions do. The next step is a written architecture review with legal and security in the room, including whether SecNumCloud is a hard gate.

Lyon: health, biotech and industrial software

Lyon combines healthcare and biotech with industrial software, chemicals and logistics. Health-adjacent projects bring strict data classification and a strong interest in where processing happens. Regional procurement is less centralised than Paris, so the business unit often controls the first pilot budget. A shared EU region can work for de-identified or low-risk data; identified patient data usually needs a DPIA and a narrower deployment. Start with one document or coding workflow, measure quality and latency, and keep the key-management question on the agenda.

Marseille: logistics, port operations and energy

Marseille is a Mediterranean logistics, shipping and energy hub with aerospace and public-sector employers nearby. Workflows are document-heavy and operational: customs, freight, maintenance and supplier correspondence. Public-sector, port-authority and energy buyers may add a security questionnaire of their own, so keep the answers with the procurement file. The technical constraint is integration with port and enterprise systems, not distance to Frankfurt. A narrow pilot on one document type, with p95 latency measured from your own network, is a better first step than a broad platform rollout.

Local search phrases to validate

These are research candidates for French-language demand, not approved copy. No volume or ranking is claimed.

Table 2. French phrases to test with a native reviewer.
PhraseEnglish glossLikely intent
hébergement LLM privéprivate LLM hostingCommercial research
hébergement IA souverainesovereign AI hostingSovereignty-led
API IA RGPDGDPR AI APICompliance-led
LLM en FranceLLM in FranceLocation-led
IA privée entrepriseprivate AI for businessEnterprise research
API OpenAI FranceOpenAI API FranceMigration-led
souveraineté numérique IAdigital sovereignty and AIPolicy-led
hébergement modèle IAAI model hostingInfrastructure-led

Validate with a native reviewer; not published as localized copy.

What we did not verify

  • No French customer, reference or case study is claimed.
  • No French office, subsidiary or facility is claimed in Paris, Lyon or Marseille; local staffing is not confirmed.
  • No French region is live, and no French data centre is claimed. Frankfurt is in the EU, not France.
  • No SecNumCloud qualification, ISO 27001 certification or SOC 2 attestation. SOC 2 is described as readiness or in progress.
  • No CNIL approval or certification. The CNIL does not certify AI vendors.
  • No measured latency from French 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 France?

No. No Plugsky region is live in France. The nearest live region is eu-central-1 in Frankfurt, and private VPC, on-premises and air-gapped deployments are contract-only.

Is Frankfurt acceptable under the GDPR for French data?

Processing inside the EU avoids a third-country transfer for the inference itself, but you still need an Article 28 processor agreement, a record of processing and a DPIA where the use case is high risk. Subprocessors and support access can create other transfer questions. Counsel must confirm your position.

Is Plugsky CNIL-certified?

The CNIL does not certify AI vendors, and no CNIL approval is claimed. The CNIL publishes AI recommendations and enforcement guidance. Plugsky offers GDPR processor terms, and you should assess them against those recommendations.

Is Plugsky SecNumCloud qualified?

No. SecNumCloud is an ANSSI qualification, and Plugsky does not claim it. If a French tender requires SecNumCloud, treat that as a qualification gate to resolve 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 France?

No. No French region is live, so there is no French processing location to guarantee. Residency is only what the signed DPA and order form state, and Frankfurt is an EU location rather than a French one.

How should we test latency from France?

Run a pilot from your Paris, Lyon or Marseille network against the Frankfurt region and measure p50 and p95 for your own prompts. No French latency benchmark is published, and this page makes no millisecond claim.

Sources

Last checked 20 November 2026.

For the wider product picture, see sovereign AI. For the API surface, read the docs.

Separate the EU question from the France question

Frankfurt can be the right processing location. It is not a French one. Decide that honestly before the pilot.

Request architecture review