Business Entity
Orq.ai is incorporated and headquartered in Amsterdam, Netherlands, within the European Union. The company was founded in 2022.Investors
Orq.ai is backed by European and European-aligned investors. Seed round (2025): Led by seed + speed Ventures and Galion exe, with participation from Curiosity VC, Spacetime, XO Ventures, xdeck ventures, Waves Capital, and GoldenEggCheck. Pre-seed: Led by Curiosity VC and Spacetime (Adriaan Mol), with angels including Arjé Cahn (Bloomreach) and Koen Köppen (Mollie, Klarna).Infrastructure
All data stored within the Orq.ai platform resides in data centers located in the European Union, running on Google Cloud Platform.VPC Deployment
Deploy into your own VPC on AWS or Azure.
Trust Center
Real-time security and compliance status.
AI Gateway
The AI Gateway is an EU-hosted gateway that routes traffic across 500+ models from all major providers through a single endpoint. Your application sends requests to one Orq.ai endpoint; no direct connections to individual provider APIs are required from your side. This centralises data flow through EU infrastructure regardless of which underlying model handles the request.AI Gateway
Configure and route across models from a single EU-hosted endpoint.
Model Inference
The AI Gateway includes a Location filter to restrict the model pool to providers that run inference in a specific region. Set the filter to Europe to see only European-hosted models. Many providers offer European inference endpoints. Use the Location filter to find them rather than relying on a static list.Zero Data Retention
A ZDR-capable model is one whose provider guarantees no retention of request data after the call completes. The model catalog records that guarantee. The ZDR filter is off by default. Turn it on under Access on the Models page to narrow the list to ZDR-capable models. The filter narrows the model list in the console. Routing decides which provider runs a request, and fallbacks and routing rules can move a call to another model. To enforce ZDR on API traffic, name a ZDR-capable model in the request and keep fallbacks and routing rules within the same set:security parameter, and Data retention sets the period by plan.
No Training on Your Data
No data that flows through Orq.ai is ever used to train or fine-tune any models by Orq.ai. Provider-side training policies vary. Most providers allow training to be disabled; this must be configured directly in the provider’s platform. See Data Compliance for details on how Orq.ai handles data at the platform level.Trust Center
Full data handling policy and real-time compliance status.
PII Anonymization
Orq.ai provides three layers of PII control: Input masking: Flag input variables as PII. The value is sent to the model but never stored or shown in logs or traces within Orq.ai. To stop the provider retaining the value after the call, combine input masking with a ZDR-compliant provider from the Zero Data Retention filter. Output masking: Mask entire model responses. Tokens are exchanged with the model but the content is never stored or displayed within Orq.ai. PII Anonymization evaluator: Verify that PII has been correctly removed or anonymized in model outputs. Useful in healthcare, legal, and financial contexts.Data Compliance
Configure input masking, output masking, and data retention.