# Open AI

## Kurzbeschreibung
**OpenAI **offers a broad range of models via the API for text generation, reasoning, coding, tool use, structured outputs, and document-centric workflows. 


According to the official model overview, the current models support text and image input, text output, multilingual capabilities, and vision; they are available through the Responses API and client SDKs. For complex tasks, OpenAI generally recommends gpt-5.4; for lower latency and costs, OpenAI points to gpt-5.4-mini and gpt-5.4-nano

## Claim
LLM “Access our frontier models and APIs.”

## Geeignet für
- API Integration
- Automation / Workflows
- Education
- Data Analysis
- Data Extraction / Document Analysis
- Customer Service & Chatbots
- Programming / Software Development
- Research
- Writing & Editing
- Texts / Content
- Translations
- Knowledge Management / Internal Search

## Kernfunktionen
- Image generation
- Embeddings
- Function calls
- AI agents
- LLM API
- Multimodal AI
- Programming
- Reasoning model
- Voice output
- Language model
- Text generation
- Transcription
- Video generation

## Preismodell
- **free:** There is a free usage tier in the API rate limit system for users in permitted geographies
- **other:** **Token-based API usage** Billing by model, input/output tokens, cached input, audio/image/tool usage, and other usage-dependent factors.


**Batch / Flex / Priority / Scale Tier** Options for cost and latency management for larger or predictable workloads.


**Fine-Tuning / Evals / Tools / Agents** Additional API features for customization, evaluation, agents, web search, File Search, Code Interpreter, Realtime, and structured outputs.


**Data Residency / ZDR / EKM** Enterprise-grade data controls with regional storage/processing, Zero Data Retention or Modified Abuse Monitoring, and external key management.

## DSGVO und Datenschutz
**Gesamteinschätzung:** Conditional

**On-Prem / local hosting: indirect / not available**


The website does not document any on-premise, self-hosting, or locally self-operated model option for the OpenAI API. Instead, it documents a hosted API service.


**Private Cloud / data center: partial**


Data residency controls per project are documented, including a European region with regional storage and regional processing for supported services. However, a dedicated private cloud or single-tenant environment is not explicitly described on the website.


**EU SaaS / Managed: covered**


The website documents an OpenAI-operated SaaS/API option with EU data residency for 'Europe (EEA + Switzerland)' via 'eu.api.openai.com'. For supported services, regional storage and regional processing are specified, though only under conditions such as approval and additional controls.


**Hybrid: partial**


The website mentions local execution in individual contexts, such as 'Skills' in local execution alongside hosted container-based execution. This describes a technical mixed path for partial components, but not a fully documented general hybrid operating model for the entire core solution.


**DPA / DPA: unclear**


I could not find a DPA or a corresponding agreement on the specified domain. Not specified on the website.


**No training: covered**


In the data controls table, 'Data used for training' is listed as 'No' for the listed API endpoints in each case. In addition, 'Zero Data Retention' and 'Modified Abuse Monitoring' are described, which can further restrict abuse logging, subject to approval and conditions.


**Open source / transparency path: partial**


There is a documented transparency path through open-source Codex components on GitHub, including Codex CLI, Codex SDK, Codex App Server, Skills, and the 'Universal cloud environment'. At the same time, according to the website, central parts such as 'IDE extension' and 'Codex web' are not open source; a self-hostable end-to-end path for the OpenAI API is not documented.


**Data processing**


The website describes the OpenAI API as a hosted service. For many endpoints, it is documented that API data is not used for training. By default, depending on the endpoint, there are retention periods for abuse monitoring and in some cases application state; for '/v1/responses', a 30-day application-state storage period is described by default, unless restricted by appropriate controls. For European data residency, the website names the region 'Europe (EEA + Switzerland)' with regional storage and, for many supported services, also regional processing. At the same time, according to the website, data residency does not include 'system data', certain functions have limitations, and data sent to third parties such as remote MCP servers is subject to their own policies.


**Conclusion**


For the EU/EEA area, based on the documented best-case option, OpenAI is not universally usable, but **conditionally** usable: positives include EU data residency, regional processing for many services, and documented no-training/retention controls. Negatives include the dependency on approval, the lack of concrete information on a DPA, missing subprocessors information on the domain, the lack of an on-prem option for the core API, as well as several functional limits and exceptions. For a European directory, 'conditional' is therefore the most defensible classification.


**Sources**


- [https://developers.openai.com/api/docs/guides/your-data](https://developers.openai.com/api/docs/guides/your-data)
- [https://developers.openai.com/api/docs/models/gpt-5.4](https://developers.openai.com/api/docs/models/gpt-5.4)
- [https://developers.openai.com/api/docs/models/gpt-5.5](https://developers.openai.com/api/docs/models/gpt-5.5)
- [https://developers.openai.com/codex/open-source](https://developers.openai.com/codex/open-source)
- [https://developers.openai.com/](https://developers.openai.com/)

For users in the European region, GDPR-compliant use is generally possible under the best available option documented on the website, but only under certain conditions. Positively, OpenAI describes EU data residency for 'Europe (EEA + Switzerland)' on its developer website, with regional storage and regional processing for supported services, and also documents project-specific data controls such as 'Zero Data Retention' and 'Modified Abuse Monitoring'. At the same time, according to the website, restrictions apply: data residency is eligibility-based, subject to additional requirements for non-US regions, does not apply to system data, and does not apply equally to all features.


**Positive**


The website documents EU data residency for 'Europe (EEA + Switzerland)' via 'eu.api.openai.com', regional storage and regional processing for many supported API services, as well as data controls according to which API content is not used for training according to the table. In addition, 'Zero Data Retention' and 'Modified Abuse Monitoring' are available as configurable controls following approval.


**Negative**


The website does not name a specific EU server location at country level or a particular data center. Data residency is not freely available by default, but only following review or approval. It expressly does not apply to 'system data', and certain features are restricted or cannot be used in a GDPR-compliant manner, such as notes regarding Realtime Tracing or certain storage-related or third-party-adjacent features. I was unable to find a Data Processing Agreement (DPA) or a list of subprocessors on the specified domain.


**Server location**


For data residency, the website names the region 'Europe (EEA + Switzerland)' with the endpoint 'eu.api.openai.com'. The website does not specify a particular country, server location, or data center within the EU/EEA.

## Hosting und Daten
- **On-Prem / lokales Hosting:** unknown
- **Private Cloud / Rechenzentrum:** teilweise / indirekt
- **EU SaaS / Managed:** abgedeckt
- **Hybrid:** teilweise / indirekt
- **AVV / DPA:** unknown
- **Kein Training auf Kundendaten:** abgedeckt
- **Open-Source / Transparenz-Pfad:** teilweise / indirekt

## Standort
**Land:** USA

**Taxonomie:** USA

OpenAI OpCo, LLC, 1455 3rd Street, San Francisco, CA 94158, USA

## Vorteile
- Very broad model coverage, from affordable to frontier.
- Strong suitability for coding, agents, tool calling, structured outputs, and long contexts.
- According to OpenAI, API/business data is not used for training on inputs/outputs by default.
- Data residency, Zero Data Retention, and DPA are

## Nachteile
- The portfolio is complex; model selection, pricing tiers, context limits, and tool costs require explanation.
- The most powerful models are significantly more expensive than Mini/Nano variants.
- Data protection and data residency options are not identical across all cases, but are sometimes tied to the organization type, endpoint, or enablement.
- Older model families that remain available increase operational complexity in selection and lifecycle management.

## Quellen
- Offizielle Website: https://developers.openai.com/api/docs/pricing

## Letzter Datenstand
2026-04-16

## Originalseite
https://kifox.ai/en/ki-tools/open-ai-en/