Predictable infrastructure pricing without hyperscaler complexity.

On Private AI Node and Mac Cloud plans, yes — the physical Apple Mac Studio (Apple M3 Ultra, 96 GB) is assigned to you alone. Managed AI API plans run on shared infrastructure with per-customer authentication, rate limits and isolation at the API layer.

Our current compute region is Georgia. Commercial operations, sales and customer communication are run from Germany / Europe. Georgia is outside the European Economic Area — see our Data Processing page for what that means for personal data.

On Private AI Nodes, yes — including fine-tuned variants of supported architectures — provided the model is technically compatible with Apple Silicon inference runtimes, fits in memory with your required context length, and you have the rights to deploy it. We check compatibility before deployment.

Yes, for supported API patterns. Our endpoints follow the OpenAI request and response format for chat completions, embeddings, audio transcription and model listing. Most applications switch by changing the base URL, the API key and the model name. Not every OpenAI parameter or endpoint is supported — see OpenAI compatibility in the docs.

No. Lirux does not train models on customer prompts, responses or files. We serve open-weight models; we do not build our own foundation models from customer data.

Monthly API plans can be cancelled at the end of any billing period. Dedicated nodes are offered on monthly or longer terms, with notice periods stated in your order. [POLICY: confirm minimum terms before launch]

Yes. Multi-node clusters, private networking, custom models, white-label endpoints and specific retention settings are designed with you. Request an architecture recommendation to start.

Private connectivity (for example a site-to-site VPN or WireGuard tunnel) is available on eligible Private AI Node and High Availability deployments. Contact us for deployment requirements.

Yes. European businesses may use infrastructure outside the EEA. Workloads involving personal data may require appropriate international-transfer safeguards and internal legal review. We support contractual and technical measures such as a Data Processing Agreement and Standard Contractual Clauses where applicable. Speak with us about your data classification before deployment.

When you send personal data to Lirux, you are typically the controller and we act as processor under a Data Processing Agreement. Because compute currently runs in Georgia (outside the EEA), a transfer mechanism such as Standard Contractual Clauses and a transfer impact assessment may be required. Our services are designed to support GDPR-conscious deployments, but customers remain responsible for determining the appropriate legal basis for their workloads. This is not legal advice.

An EU-based region is not available today. We are evaluating one. If EU data residency is a requirement for you, tell us — demand from customers directly informs our roadmap — and we will be transparent about timing.

Yes. Our Partner Program is built for software agencies: partner pricing, client-specific private nodes, custom endpoints and white-label architecture where technically available. Apply on the Partners page.