Skip to content

Integration / Sovereign cloud

OVHcloud, routed by jurisdiction.

Use OVHcloud AI Endpoints, served from Gravelines in France, as an EU-headquartered inference target behind YTT Secunet's policy engine and receipts.

OVHcloud logo

OVHcloud

Sovereign cloud

Regions documented
2
Setup steps
5

How YTT Secunet works with OVHcloud

OVHcloud is a French cloud provider headquartered in Roubaix. Its AI Endpoints service offers a catalogue of open-weight models through an OpenAI-compatible API, and OVHcloud's documentation states that the AI Endpoints infrastructure is located in Gravelines, France, follows European data protection rules, and that data is not stored or shared during or after model use. Authenticated access uses an API key tied to a Public Cloud project, with per-project, per-model rate limits; anonymous access exists for testing at much lower limits and should never carry production data.

YTT Secunet registers AI Endpoints as an EU endpoint with facility Gravelines and routes OpenAI-format requests to it under your policy packs. Teams typically use it in two ways: as the primary for workloads where an EU-headquartered provider is a procurement requirement, and as the in-jurisdiction failover for US-parented EU deployments. Because rate limits are per model and per project, YTT Secunet spreads load across several OVHcloud projects when you register more than one, before it considers failover to another provider.

For organisations that need more isolation than a shared service, OVHcloud also sells private cloud and bare metal offerings on which you can run vLLM or another runtime yourself; some of OVHcloud's private cloud offerings carry the French SecNumCloud qualification, so check whether the qualification covers the exact product you buy. YTT Secunet treats such deployments as Self-hosted runtime endpoints and records the facility you declare.

OVHcloud regions and jurisdictions

Region or deploymentLocationJurisdiction
AI EndpointsGravelines, FranceEU / European Union
Self-hosted runtime on OVHcloud Public CloudCustomer project, Gravelines or StrasbourgEU / European Union

Connect OVHcloud: setup steps

  1. 01

    Create an OVHcloud Public Cloud project and generate an AI Endpoints access key; never route production data through anonymous access.

  2. 02

    Check the AI Endpoints catalogue for the models you need and note their names and per-model rate limits.

  3. 03

    Register the OpenAI-compatible base URL shown in the AI Endpoints catalogue as a YTT Secunet endpoint with jurisdiction EU and facility Gravelines.

  4. 04

    Optionally register several projects' keys so YTT Secunet can balance across per-project rate limits.

  5. 05

    Attach the endpoint to your EU policy packs and point your SDK at https://eu.yttsecunet.com/v1.

Configuration

yamlOVHcloud through YTT Secunet
endpoints:
  - id: ovh-ai-endpoints-gra
    provider: openai-compatible
    upstream: https://oai.endpoints.kepler.ai.cloud.ovh.net/v1
    jurisdiction: EU
    facility: gravelines
    credentials:
      - vault://ovh/project-a
      - vault://ovh/project-b
    balance: per-key-round-robin

routes:
  - policy: eu-gdpr-strict
    primary: ovh-ai-endpoints-gra
    failover: [scw-genapi-par]

Policy notes

  • Requests without an authenticated key are refused by YTT Secunet, so anonymous access cannot be used by mistake.
  • Endpoints from OVHcloud are tagged EU-headquartered, which policies can require for public sector tenants.
  • Audio models published on separate OVHcloud endpoints are registered individually rather than assumed under the shared base URL.

OVHcloud questions

Is OVHcloud AI Endpoints SecNumCloud qualified?

Do not assume it. SecNumCloud applies to specific OVHcloud offerings. If your contract requires it, run your model on a qualified OVHcloud offering and register it in YTT Secunet as a self-hosted endpoint.

Can YTT Secunet fail over from OVHcloud to another provider?

Yes, to any endpoint the policy allows in the same jurisdiction, such as Scaleway in Paris or an Azure OpenAI Data Zone EU deployment. It never fails over to a region outside the jurisdiction.

What do receipts show for OVHcloud calls?

The resolved endpoint, facility Gravelines, model id, policy pack and version, the upstream TLS certificate thumbprint and a request hash, signed and included in the hourly Merkle tree.

Related integrations

Sovereign route ready

Stop risking 4% global turnover GDPR fines on AI inference.

Deploy sovereign, cryptographically proven AI routing in 15 minutes.