Germany · 2027 planning guide

Private LLM hosting in Germany for regulated buyers

German buyers need an EU processing location, a signed data processing agreement and evidence they can defend to a supervisory authority. Plugsky serves Germany from its live Frankfurt region; private VPC, on-premises and air-gapped deployments are contract-only.

Short answer. Germany is served by Plugsky's live eu-central-1 region in Frankfurt. Private VPC, on-premises and air-gapped deployments are contract-only: they are scoped and priced under a signed agreement and are not available from the checkout. Plugsky does not claim a German office, a second German region, ISO 27001 certification or a blanket guarantee that data never leaves Germany.

2027 planning guide — evidence checked 20 November 2026.

Availability at a glance

Frankfurt is the live EU region and the only region Plugsky claims for Germany; the nearest region and the live region are the same.

Table 1. Plugsky availability for German buyers, checked 20 November 2026.
OptionWhat is availableStatusBuyer note
Live regioneu-central-1, FrankfurtliveServes German workloads today; not a German legal entity.
Nearest regionFrankfurt; same as the live regionnearestNo closer live region is claimed.
Private VPCDedicated endpoint in the EU regioncontractNetwork boundary, egress and price are agreed in writing.
On-premisesPlugsky runtime in your facilitycontractHardware, updates and support are part of the order.
Air-gappedDeployment with no outbound connectivitycontractThe update and support path is designed into the contract.
Residency commitmentOnly what the DPA and order form statecontractA web page cannot create a residency guarantee.
German office or owned siteNone claimednot claimedNo office, subsidiary or owned data centre in Germany 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.

What the Frankfurt region does and does not mean

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.

eu-central-1 is Plugsky's EU region label, mapped to Frankfurt. Requests assigned there are processed in the EU, with GDPR processor terms behind them. For many buyers that is the central fact: no US transfer is needed for inference.

It does not follow that Plugsky is a German company, that every engineer is in Germany, or that every subprocessor sits in the EU. Support, logging and billing can cross borders. The evidence is the DPA, the subprocessor list and the transfer analysis, not a flag on a marketing page. The data residency guide explains the difference between residency, sovereignty and a routing preference.

Nor is a workspace automatically pinned to Frankfurt. Put the serving region in the order form or DPA schedule and ask how it is monitored.

For more isolation, the private VPC option keeps traffic inside a network boundary you control. The air-gapped option removes outbound connectivity. Both are engineering projects with a commercial envelope, not toggles.

German framework: DSGVO, BSI and the EU AI Act

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

GDPR and DSGVO

The GDPR applies directly in Germany; the BDSG adds national detail. The operative articles are 28, 32, 35 and 44 to 49. Frankfurt inference avoids a third-country transfer, but support and subprocessors can still create one.

Ask for the Article 28 DPA, the subprocessor list and the transfer analysis. Ask whether a DPIA is needed and whether the vendor will complete a questionnaire rather than point at a badge. A bring-your-own-key design changes key custody only if the contract says so.

BSI and the C5 catalogue

The BSI is Germany's federal information security authority. Its C5 catalogue is the cloud assurance benchmark public-sector and financial buyers ask for; C5:2026 is the latest edition. C5 is not ISO 27001 or SOC 2.

Plugsky does not claim BSI C5 attestation. A SOC 2 Type II report and ISO 27001/27017/27018 certificates are available under NDA; confirm the scope, audit period and exceptions during vendor review. The security page is not itself an attestation. If your tender requires C5, say so early.

The EU AI Act

The AI Act, Regulation (EU) 2024/1689, applies in stages. General-purpose model duties 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 check the consolidated text.

Your duties depend on whether you are a deployer, a provider or both. If the API sits inside an HR, credit or safety decision, documentation, logging and human oversight are yours. Put the allocation into the contract. Plugsky does not certify your system's conformity.

A procurement path that survives legal review

German enterprise deals usually fail on evidence, not on model quality. A sequence that works:

  1. Classify the data: personal, confidential, regulated or public. Decide whether prompts and outputs are in scope.
  2. Request the DPA, subprocessor list and any SCCs. For Frankfurt processing, confirm which support paths sit outside the EEA.
  3. Run a DPIA if the use case is high risk. Describe retention, human review and the consequences of a wrong answer.
  4. Request the security package: SOC 2 report under NDA, incident process and SLA schedule. The 99.9% uptime target is a headline figure; plan terms and exclusions apply, and Hobby is not in the SLA table.
  5. Choose the deployment: shared EU region, private VPC, on-premises or air-gapped. The last three are contract-only and change the timeline.
  6. Write the AI Act role, audit rights and deletion duties into the agreement. Keep the security procurement checklist next to the contract.

Self-serve pricing is published. Enterprise and private deployment pricing is quoted because scope drives cost. The documentation covers the OpenAI-compatible endpoint, streaming, tools and embeddings if your engineers want to test first.

Where the German demand is

Four cities account for most of the serious conversations, for different reasons. No Plugsky office is claimed in any of them.

Frankfurt: banking, insurance and cloud procurement

Frankfurt is the banking and insurance centre, with asset managers, supervisors and the European Central Bank nearby. Buyers here are sophisticated: they arrive with C5 questions, outsourcing registers and DORA obligations. The advantage is that inference stays in the same region they already treat as their EU anchor, so latency is a domestic question rather than a cross-border one. The next step is a written architecture review that names the serving region, the subprocessor list and the DPA schedule before a pilot starts.

Berlin: startups, public digital units and health

Berlin mixes venture-backed software companies, public-sector digital units, health providers and media. Procurement splits sharply: a startup can test the API this week, while a public body needs a tender, a DPIA and a security pack. Budget cycles run on annual tenders, so a pack prepared early is an advantage. The city's data protection authority is active, so claims are read closely. Start with the self-serve API and the security questionnaire, then decide whether the workload needs a private VPC or can stay on the shared EU region.

Munich: automotive, machinery and insurance

Munich's economy runs on automotive, machinery, aerospace and insurance. AI projects usually touch engineering documents, supplier data or employee-facing tools, which brings the works council into the room early. Procurement often sits with a central IT and legal team rather than the business unit. Latency to Frankfurt is a short domestic hop; the harder work is the data classification and the works agreement. A joint architecture session with legal, security and the works council is a better first step than a model benchmark, and it surfaces the contract questions before the pilot.

Hamburg: logistics, media and aviation

Hamburg is a port and logistics city with media, aviation and renewable-energy companies alongside it. Document-heavy workflows are common: bills of lading, customs paperwork, maintenance records and customer service. Port and media groups also run large shared-service centres. The technical constraint is usually integration with operational systems, not distance to Frankfurt. Run a narrow pilot on one document type, measure p95 latency from your own network, and keep the private VPC option open if supplier access rules make a shared endpoint uncomfortable.

Local search phrases to validate

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

Table 2. German phrases to test with a native reviewer.
PhraseEnglish glossLikely intent
private LLM hostingprivate LLM hostingCommercial research
LLM hosting DeutschlandLLM hosting GermanyLocal vendor search
DSGVO-konforme KI APIGDPR-compliant AI APICompliance-led
KI API FrankfurtAI API FrankfurtRegion-led
private KI Infrastrukturprivate AI infrastructureEnterprise architecture
LLM on premise Deutschlandon-premises LLM GermanyDeployment-led
EU AI Act konforme KIEU AI Act compliant AIGovernance-led
souveräne KI APIsovereign AI APISovereignty-led

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

What we did not verify

  • No German customer, reference or case study is claimed.
  • No German office, subsidiary or facility is claimed in Frankfurt, Berlin, Munich or Hamburg; local staffing is not confirmed.
  • No BSI C5 attestation, ISO 27001 certification or SOC 2 attestation. SOC 2 is described as readiness or in progress; request the report under NDA and check the period.
  • No measured latency from German networks and no benchmark against other providers.
  • No guarantee that every subprocessor or support engineer is in Germany. Check the current list.
  • No AI Act conformity assessment for your system, and no legal opinion on your role.
  • No validated search volume or native review for the German phrases above.

Frequently asked questions

Is there a Plugsky data centre in Germany?

Plugsky's live EU region is eu-central-1 in Frankfurt. No owned German data centre, Berlin or Munich facility, or German subsidiary is claimed. Ask for the serving region and subprocessor list in writing.

Does Plugsky guarantee that data stays in Germany?

No blanket guarantee is made. Frankfurt processing keeps inference in the EU region, but support access, logging and subprocessors can involve other locations. Only signed terms create a residency commitment.

Can we get a GDPR data processing agreement and SCCs?

Plugsky offers GDPR Article 28 terms and EU standard contractual clauses. The DPA is available on paid plans; bespoke addenda are discussed on Enterprise. Ask for the current version before signature.

Is Plugsky BSI C5 or ISO 27001 certified?

No BSI C5 or ISO 27001 certification is claimed. Plugsky describes SOC 2 as readiness or in progress. Request the SOC 2 report under NDA and verify the period.

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, not through the self-checkout.

Does the EU AI Act apply to a company that only buys an API?

It can. Duties depend on your role and use case. General-purpose model obligations have applied since 2 August 2025, and the original timetable sets most high-risk duties from 2 August 2026. Confirm the current text and your role with counsel.

How should we test latency from Germany?

Run a pilot from your own network against Frankfurt and measure p50 and p95 for your prompts. No German 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.

Bring the German deployment question to a written review

Name the region, the data classes and the contract route before a pilot. That is faster than discovering the gap in procurement.

Request architecture review