Going Swiss-Sovereign: Infomaniak AI, Jelastic Pitfalls, and How We Shipped Production on a VPS with Traefik

I've been building swisscontract.ai — a contract analyser that runs on Swiss servers and uses Swiss AI. The pitch: your employment contract text never leaves Switzerland. This week I actually delivered on that promise. It took two days, three infrastructure switches, and a surprising number of npm bugs. Here's the full story. The Goal: Swiss-Sovereign AI The app was running on Vercel with Claude. Great for quality, but "Swiss-sovereign" means data stays in Switzerland. Infomaniak — a Geneva-based cloud provider — offers an AI API backed by open models in their Swiss datacenters. I wanted to test the models and swap the hosting at the same time. Testing the Models I tested 5 Infomaniak AI models against a real Swiss employment contract: Model Time Valid JSON Accuracy qwen3 23.9s ✅ Good moonshotai/Kimi-K2.5 26.1s ✅ Best llama3 15.7s ✅ Decent mistral3 8.2s ❌ (markdown) Good swiss-ai/Apertus-70B 26.5s ❌ (markdown) Good Key finding : Infomaniak's v2 API doesn't support response_format: { ty