Inference runs on Entrim-operated infrastructure in Slovenia, EU.
Inference data is processed and retained in line with GDPR-ready practices.
Customer prompts and outputs are never used to train or fine-tune models.
Data-processing terms are available for legal, privacy, and procurement review.
A limited set of operational data needed to operate the service:
Operational metadata does not include prompt or output content. Temporary prompt caching expires automatically.
Where your data is processed matters. Who controls the service matters too.
Choosing an EU region doesn’t always mean choosing a European provider. Entrim operates its own datacenter and GPU infrastructure in Slovenia, EU.
Entrim
Clear data-processing terms, with Zero Data Retention available for stricter retention requirements.
Security spans access, traffic, monitoring, tenant isolation, abuse prevention, and fraud detection.
Compliance is treated as an ongoing operational discipline, not just a certification milestone.
Operational ownership gives Entrim tighter control over how inference is operated and delivered.
Code examples
curl -X POST "https://api.entrim.ai/v1/chat/completions" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer $ENTRIM_API_KEY" \ -d '{ "model": "your-model-name", "messages": [ { "role": "user", "content": "Why do they call it a building if it is already built?" } ] }'Change the base URL
Point your existing OpenAI-compatible SDK at the Entrim API endpoint.
Use your Entrim API key
Generate a key in the dashboard and drop it into your client config.
Select your model
Pick an open-source model from the library and start testing.