Migration plan

Articles

10 November 2026

Migrating Prompts Written for Claude to an Open-Weight Model

Keep your Claude prompt text as it is. Change three things in the request: remove any reply you pre-start for the model (a prefill), allow enough tokens for the model's reasoning, and check the answer format in your code. To try it on our API, change the base URL.

23 October 2026

Routing between open-source and proprietary models in one application

Put one small function in front of your model calls. It reads each request and picks a model by your rule, such as task type or personal data in the text. Open models are served behind APIs that speak the same format as OpenAI's, so both sides use the same client code.

23 October 2026

Migrate an LLM workload from a US inference provider to the EU

Move one workload at a time, starting with a list of your app's model requests and the personal data they carry. Pick an open model we serve, then change three settings in your OpenAI client: the address, the key and the model name. Update your data processing paperwork and test on real traffic before you switch over.

9 October 2026

What Switching Inference Providers Actually Costs

Estimate a provider switch across evaluation, prompt changes, integration, parallel traffic and review work. The extra API bill depends on the new provider’s rates and actual mirrored tokens.

21 August 2026

OpenAI Compatible APIs: What Breaks When Switching Models

Switching inference endpoints is a one-line code change, but prompt behavior rarely transfers perfectly

18 September 2026

Switching the OpenAI SDK to an Open-Model Endpoint

Changing the base URL in the OpenAI SDK takes a minute, but a true migration requires checking five critical behavioural differences underneath the compatible interface. This guide covers how to repoint the SDK and verify structured output, tool calls, and ignored parameters.

20 April 2026

OpenAI Compatible API Self Hosted: A Guide for EU AI Teams

Relying on proprietary US-based APIs creates significant risks for European AI teams, from GDPR non-compliance to unsustainable scaling costs. By adopting a self-hosted, OpenAI-compatible architecture, you can maintain full control over your data residency while moving to per-second and per-token pricing you can model directly against your own traffic.

Your next workload starts here