Drive

One API. Zero data leaving Europe.

Polarise Drive is the fully managed inference platform for European developers and enterprises: OpenAI-compatible, consumption-priced.

  • Latest Models
  • Own Datacenters
  • No Cloud Act Exposure
EU flag
Operated in Europe Full sovereignty
DE flag
Made in Germany Infrastructure
Certified Compliant

Fully managed AI inference

Drive sits on top of Polarise's own stack: GPUs, platform and datacenter are ours. OpenAI-compatible API to frontier open-source models on sovereign EU infrastructure.

Polarise Drive platform overview
ISO/IEC 27001 Certified
ISO/IEC 9001 Certified
EN 50600 Certified
BSI C5 In preparation
SOC 2 Type I In preparation
SOC 2 Type II In preparation

Supported models

Access the latest open-source models through a single API.

Always on the latest model

Every model family has a stable :latest alias. When we upgrade a family — say from GLM 5.2 to GLM 5.3 — the alias automatically bumps to the new version, and the previous one is deprecated.

Works with any stack

The tools you already use connect with a base URL and an API key. Same clients, same code, sovereign European models behind them.

*Every client that speaks the OpenAI API.

opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "model": "polarise/glm-5.3",
  "provider": {
    "polarise": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Polarise Drive",
      "options": {
        "baseURL": "https://api.model-gateway.polarise.app/v1",
        "apiKey": "{env:POLARISE_API_KEY}"
      },
      "models": {
        "glm-5.3": { "name": "GLM 5.3" }
      }
    }
  }
}
main.py
import os

from langchain_openai import ChatOpenAI

llm = ChatOpenAI(
    model="glm-5.3",
    base_url="https://api.model-gateway.polarise.app/v1",
    api_key=os.environ["POLARISE_API_KEY"],
)
~/.openclaw/openclaw.json
{
  "agents": {
    "defaults": {
      "model": { "primary": "polarise/glm-5.3" }
    }
  },
  "models": {
    "mode": "merge",
    "providers": {
      "polarise": {
        "baseUrl": "https://api.model-gateway.polarise.app/v1",
        "apiKey": "${POLARISE_API_KEY}",
        "api": "openai-completions",
        "models": [{ "id": "glm-5.3", "name": "GLM 5.3 (Drive)" }]
      }
    }
  }
}
~/.hermes/config.yaml
model:
  default: glm-5.3
  provider: custom
  base_url: https://api.model-gateway.polarise.app/v1
  api_key: ${POLARISE_API_KEY}

This is Drive

ISO/IEC 27001 Certified
ISO/IEC 9001 Certified
EN 50600 Certified
BSI C5 In preparation
SOC 2 Type I In preparation
SOC 2 Type II In preparation

Setup in minutes

Create an API key in the portal, set your limits, and you are ready to call the API within minutes.

Quick create · Budget caps · Rate limits & quotas · Model restrictions · Fine-grained permissions

The Drive roadmap

The Model Gateway is production-ready today. Everything after it ships incrementally on the same OpenAI-compatible API: no go-live dates, no rewrites, no lock-in.

One platform, growing with you

Online

A single OpenAI-compatible endpoint for every hosted model: streaming, structured JSON outputs, native function calling, KV-cache pricing. Requested models typically go live within two weeks, and model routing plus external provider integration keep widening the catalog without a line of your code changing.

From API to agents

Planned

European teams should build on agent infrastructure, not just on models. The Gateway grows into exactly that, anchored in open standards like MCP and hosted in our European datacenters.

Agent Engine

MCP connectors · agent orchestration · GitOps workflows · retrieval with a managed vector store · secure code sandbox

Marketplace

third-party apps · reference apps

Get started with Polarise Drive

Request early access and tell us about your workload.

Frequently Asked Questions

Answers to common questions about Polarise Drive.

We are currently in a controlled rollout phase. To ensure consistently stable latencies and sufficient capacity, we grant access selectively to selected partners first. After registration via the form, we review your usage profile and enable access step by step. Production-ready workloads are the stated goal of our rollout, not the exception.
Yes. We operate exclusively our own data centres in Europe and do not use any rented or outsourced third-party capacity. Your data never leaves the EU, and there is no dependency on external cloud providers.
We provide a continuously growing selection of open-source models through a unified API. Deploying your own fine-tunes or custom checkpoints is planned for a later expansion stage and is currently in development. We are happy to inform interested partners as soon as initial capacity is available for this.
Capacity is not allocated manually but provided via automated autoscaling on our own infrastructure. Since we own the entire stack, from rack to API, we can scale capacity immediately, regardless of a third-party provider’s availability or pricing.
Components such as RAG pipelines, MCP integration, and function-calling and agent support are in active development and will be gradually enabled for partners. If this is relevant to your use case, we recommend noting it in the "Expected Usage" field of the form to support prioritisation.