Real-World AI Hosting Case Studies
The differences between hosting models become clearer when we examine how organizations use them in real environments. The following case studies illustrate why businesses select local hosting, managed open-source infrastructure, or proprietary cloud AI services.
Note: The use cases below come from publicly available customer stories and vendor case studies. Readers should assess each architecture against their own security, compliance, performance, and cost requirements.
Use Case : Self-Hosted Open-Source AI for a Private Business Assistant
Business requirement
A private AI assistant was created for organizations that wanted employees to use a ChatGPT-style interface without sending confidential conversations or internal documents to an external AI provider.
The intended workloads included:
- Internal document questions
- Business strategy discussions
- Private knowledge retrieval
- Customer-support assistance
- Sensitive employee conversations
The main concerns were data privacy, unpredictable usage charges, and reliance on third-party AI APIs.
Hosting decision
The solution used a self-hosted AI stack deployed on a dedicated Linux virtual private server.
Its principal components included:
- Ollama for serving open-source models
- Llama and Mistral variants as language models
- Open WebUI as the user interface
- Docker for containerized deployment
- Nginx and TLS for secure web access
- Authentication and restricted account registration
- Host-level security controls
According to the published implementation, prompts and responses stayed on the dedicated server rather than being transmitted to a third-party language-model API. The deployment replaced per-message charges with fixed infrastructure costs.
Reported outcome
The deployment delivered a private AI chat service that was available continuously behind HTTPS and user authentication. The same infrastructure could also be reused for internal knowledge search, document question answering, and other private AI features.
Why self-hosting was appropriate
Self-hosting matched this use case because control over business data was more important than access to the largest proprietary model. The workload could run on smaller open-source models, and the operator was willing to manage the server, security, containers, and model updates.
Key lesson
Self-hosting is particularly effective when the use case is narrow, privacy-sensitive, and sufficiently predictable. It is less attractive when the organization does not have the expertise to secure, monitor, and maintain the environment.
| Case-study factor | Assessment |
|---|---|
| Primary objective | Private AI conversations and fixed infrastructure costs |
| Hosting model | Self-hosted open-source AI |
| Model approach | Llama and Mistral variants served through Ollama |
| Main benefit | Prompts and responses remain on controlled infrastructure |
| Main trade-off | The operator is responsible for security and maintenance |
| Best fit | Private assistants, internal document search, offline or controlled environments |
Use case: Atos Uses Managed Open-Source Hosting
Business requirement
Atos, a global digital-transformation, cybersecurity, and cloud-services company, needed a repeatable way for teams in Europe and the United States to deploy a broad set of applications and infrastructure services.
Its environment included more than AI models. The company needed to support:
- Front-end and back-end applications
- CI/CD delivery from GitHub and GitLab
- PostgreSQL and ClickHouse databases
- Superset for business intelligence
- Keycloak for identity management
- Monitoring and infrastructure tools
- AI development environments and AI coding tools
Managing every component separately could increase deployment complexity and place additional demands on internal operations teams.
Hosting decision
Atos selected Elestio as a managed platform for deploying and operating these services.
According to the published customer story, Atos has used Elestio for more than five years and has expanded its footprint over time. Teams use the platform for services ranging from application delivery and databases to analytics, identity, infrastructure tooling, and AI development environments.
Elestio’s broader service includes managed setup, configuration, encryption, backups, updates, and monitoring for its open-source catalogue. The platform also offers deployment across supported cloud providers and on-premises environments.
Reported outcome
The platform gave Atos teams a consistent method for deploying services across Europe and the United States. The customer story highlights the company’s expanding use of Elestio, including several additional services introduced within a relatively short period.
Rather than building a separate operational process for every database, development tool, or AI environment, teams could use a common managed platform.
Why managed open-source hosting was appropriate
Atos needed flexibility across many technologies and geographies, but it also benefited from a standardized management layer. Full self-hosting would have provided maximum control, but it would also have increased the work required for deployment, patching, monitoring, backups, and lifecycle management.
A proprietary AI API alone would not have addressed the wider requirement because Atos needed databases, identity services, analytics, infrastructure tools, and AI-development environments as part of the same operational portfolio.
Key lesson
Managed open-source hosting is valuable when an organization wants to standardize how open-source services are deployed without transferring every workload to a closed software-as-a-service platform.
| Case-study factor | Assessment |
|---|---|
| Organization | Atos |
| Primary objective | Standardize deployment of applications, infrastructure, data, and AI environments |
| Hosting model | Managed open-source hosting |
| Platform | Elestio |
| Geographic scope | Europe and the United States |
| Main benefit | A consistent deployment and management approach |
| Main trade-off | Continued dependency on an external management platform |
| Best fit | Multi-team organizations using several open-source technologies |
Use case: Rezcomm Runs an Open-Source Data Platform on Elestio
Business requirement
Rezcomm operates a travel and e-commerce platform in the United Kingdom and the United States. Its technology requirements included databases, business intelligence, analytics, identity management, and AI workflows.
The company wanted the freedom to experiment with different open-source technologies while maintaining a consistent deployment process.
Hosting decision
Rezcomm chose Elestio to run its open-source data platform. According to Elestio’s published customer overview, the deployment brings databases, analytics, identity, business intelligence, and AI workflows together under one managed platform.
The case-study summary also identifies GDPR and PCI-related requirements as important considerations and describes a pricing structure that supports experimentation.
Business value
Combining multiple open-source services under one management platform can reduce the fragmentation created by operating each component independently. It can also give development teams greater freedom to test new services without designing a complete operations model for every experiment.
Why managed hosting was appropriate
Rezcomm’s requirement involved an interconnected data platform rather than a standalone language model. Managed open-source hosting provided a middle path between operating the entire stack independently and replacing it with multiple proprietary software services.
Key lesson
The managed open-source approach is not limited to hosting an AI model. It can support the databases, analytics platforms, workflow engines, identity systems, and monitoring tools that surround a production AI application.
| Case-study factor | Assessment |
|---|---|
| Organization | Rezcomm |
| Industry | Travel and e-commerce |
| Hosting model | Managed open-source hosting |
| Workload | Data, analytics, identity, BI, and AI workflows |
| Main benefit | One deployment method for a broad open-source stack |
| Main trade-off | Dependence on the managed platform’s supported configurations |
| Best fit | Organizations building an integrated data and AI platform |
Use Case : Almirall Uses a Cloud AI Service for Pharmaceutical Research
Business requirement
Almirall, a global pharmaceutical company focused on medical dermatology, had accumulated more than 50 years of research and development information.
Its scientists needed to search approximately 400,000 documents across three languages. Traditional processes required researchers to spend hours or days locating relevant information, and some existing research risked being overlooked or duplicated.
Hosting decision
Almirall created a custom research assistant using:
- Azure OpenAI models
- Azure AI Search
- Azure Databricks
- A tailored interface for scientific users
The solution allowed scientists to search historical research information using natural-language questions. It also helped automate routine information-retrieval tasks.
Reported outcome
Microsoft’s customer story states that scientists could access information in seconds rather than spending hours or days searching for it. The assistant covered more than five decades of R&D information contained in roughly 400,000 documents.
The system helped Almirall make institutional knowledge more accessible, reduce duplicated research effort, and support shorter research cycles.
Why cloud AI was appropriate
This was a complex multilingual knowledge-retrieval problem that needed capable language models, enterprise search, data engineering, and integration services. Using managed Azure services reduced the need for Almirall to build and operate every layer internally.
The business value was driven by faster access to research, not simply by minimizing the cost of each model request.
Key lesson
Cloud AI services are an attractive option when an organization needs to combine advanced models with established cloud search, analytics, security, and data services. They are particularly useful when speed of delivery and model capability outweigh the benefits of managing an open-source model directly.
| Case-study factor | Assessment |
|---|---|
| Organization | Almirall |
| Industry | Pharmaceutical research |
| Primary objective | Make decades of R&D knowledge searchable |
| Hosting model | Cloud AI service |
| Technology | Azure OpenAI, Azure AI Search, and Azure Databricks |
| Scale | Approximately 400,000 documents across three languages |
| Reported value | Information retrieved in seconds rather than hours or days |
| Main trade-off | Dependency on the cloud provider’s platform and commercial terms |
Use case : Air India Uses Cloud AI for Customer Service
Business requirement
Air India wanted to improve its virtual assistant and provide passengers with more effective natural-language support.
Airline customer service requires access to several types of information, including:
- Flight bookings
- Baggage information
- Customer accounts
- Travel policies
- Service procedures
A conventional chatbot may struggle to interpret complex questions and provide useful responses across these different information sources.
Hosting decision
Air India updated the natural-language processing engine behind its virtual assistant using newer GPT models through Azure OpenAI Service.
Microsoft’s reference architecture for this type of airline solution combines Azure OpenAI with retrieval-augmented generation, Azure AI Search, Azure Cosmos DB, and cloud-hosted application components. The approach allows customers and support agents to ask questions in natural language while grounding responses in airline information.
Why cloud AI was appropriate
Passenger-service demand may vary significantly by time, season, route disruption, or unexpected events. Cloud infrastructure is generally better positioned to accommodate variable demand than a fixed local deployment.
The cloud approach also gives the organization access to updated language models without operating model-serving infrastructure directly.
Key lesson
Cloud AI services are well suited to customer-facing applications where demand can fluctuate and rapid access to capable natural-language models is important. However, the business must still implement reliable data retrieval, escalation to human agents, privacy controls, and monitoring.
| Case-study factor | Assessment |
|---|---|
| Organization | Air India |
| Industry | Aviation |
| Primary objective | Improve a customer-service virtual assistant |
| Hosting model | Cloud AI service |
| Technology | GPT models through Azure OpenAI Service |
| Main benefit | Advanced natural-language capability without self-managing the model |
| Main trade-off | Ongoing API and cloud-service dependency |
| Best fit | Customer service with variable usage and large knowledge sources |
What These Case Studies Tell Us
The case studies demonstrate that hosting decisions are usually driven by business constraints, not by model popularity.
| Business situation | Most suitable model | Example |
|---|---|---|
| Confidential conversations must remain on controlled infrastructure | Self-hosted open source | Private AI assistant using Ollama and open-source models |
| Many open-source services must be managed consistently | Managed open-source hosting | Atos on Elestio |
| An integrated data and AI platform needs operational simplicity | Managed open-source hosting | Rezcomm on Elestio |
| Large multilingual knowledge collections require advanced search and reasoning | Cloud AI service | Almirall on Azure |
| Customer-facing demand may change rapidly | Cloud AI service | Air India virtual assistant |
A clear pattern emerges:
- Self-hosted AI is strongest when privacy, offline operation, customization, or fixed high-volume processing is the primary concern.
- Managed open-source hosting is strongest when a business wants control and portability but does not want to operate the full stack.
- Cloud AI services are strongest when rapid implementation, elastic capacity, and access to advanced models are the main priorities.
The application’s risk level also matters. A marketing assistant, an internal research tool, and a customer-facing financial system should not automatically use the same architecture.
A Practical Example of a Hybrid Architecture
An organization can also combine all three hosting models.
Consider a financial-services company processing customer documents:
- A self-hosted model identifies personal and confidential information inside the company’s private environment.
- A managed open-source platform operates the document database, vector store, workflow engine, and monitoring tools.
- A cloud AI service performs advanced reasoning on sanitized content when the local model cannot complete the task reliably.
- High-risk outputs are sent to a qualified employee for review before any action is taken.
This design allows the business to use each model where it contributes the most value. Sensitive information remains controlled, routine work uses predictable infrastructure, and advanced cloud models are used selectively.
The final architecture should therefore be based on workload classification, rather than selecting one hosting model for the entire organization.
Updated Final Recommendation
Start by classifying each proposed AI workload according to:
- Data sensitivity
- Regulatory restrictions
- Usage volume
- Latency requirements
- Required model quality
- Customization needs
- Availability requirements
- Internal operational expertise
Then select the hosting approach at the workload level.
A cloud AI service may be the right choice for an initial prototype. As usage grows, predictable parts of the workload may move to managed or self-hosted open-source models. Highly sensitive processes may remain private from the beginning.
The most sustainable strategy is often a hybrid, model-independent architecture that allows the organization to change models or providers without rebuilding the entire application.
.png)
