# Inference hosting: GPU clouds and serverless APIs

[Skip to content](#lm-inhoud)Network/[NL](/en/inference-hosting-gpu-clouds)EN[Hubhub.llmnet.nlCompare models on task, language, cost and licence.](https://hub.llmnet.nl/en/)[Communitycommunity.llmnet.nlPrompt techniques, patterns and system prompts.](https://community.llmnet.nl/en/)[APIapi.llmnet.nlLLMs in production: rate limits, routing, structured output.](https://api.llmnet.nl/en/)[Consultancyconsultancy.llmnet.nlRolling out AI in an organisation, pilot to production.](https://consultancy.llmnet.nl/en/)[Newsnieuws.llmnet.nlAI developments, explained for the Netherlands.](https://nieuws.llmnet.nl/en/)[Benchmarkbenchmark.llmnet.nlMeasure AI quality yourself, on your own tasks.](https://benchmark.llmnet.nl/en/)[Careersvacatures.llmnet.nlAI roles, salaries and career paths in the Netherlands.](https://vacatures.llmnet.nl/en/)[Learnleren.llmnet.nlAI concepts in plain language, beginner to builder.](https://leren.llmnet.nl/en/)[Guidegids.llmnet.nlRun AI privately on your own Mac, PC, NAS or home server.](https://gids.llmnet.nl/en/)[Directorydirectory.llmnet.nlMapping the AI ecosystem: tools, models, companies.](https://directory.llmnet.nl/en/)[Radarradar.llmnet.nlSignals from X, research and communities for indie developers.](https://radar.llmnet.nl/en/)[Appsapps.llmnet.nlReviews of AI apps and open-source repos, with tips for builders.](https://apps.llmnet.nl/en/)[llmnet.nl — main site](https://llmnet.nl/en/)[](https://x.com/intent/post?url=https%3A%2F%2Fdirectory.llmnet.nl%2Fen%2Finference-hosting-gpu-clouds&text=Inference%20hosting%3A%20GPU%20clouds%20and%20serverless%20APIs)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fdirectory.llmnet.nl%2Fen%2Finference-hosting-gpu-clouds)[](https://www.reddit.com/submit?url=https%3A%2F%2Fdirectory.llmnet.nl%2Fen%2Finference-hosting-gpu-clouds&title=Inference%20hosting%3A%20GPU%20clouds%20and%20serverless%20APIs)[](#)[](https://x.com/intent/post?url=https%3A%2F%2Fdirectory.llmnet.nl%2Fen%2Finference-hosting-gpu-clouds&text=Inference%20hosting%3A%20GPU%20clouds%20and%20serverless%20APIs)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fdirectory.llmnet.nl%2Fen%2Finference-hosting-gpu-clouds)[](https://www.reddit.com/submit?url=https%3A%2F%2Fdirectory.llmnet.nl%2Fen%2Finference-hosting-gpu-clouds&title=Inference%20hosting%3A%20GPU%20clouds%20and%20serverless%20APIs)[](#)

 
 
# Inference hosting: GPU clouds and serverless LLM APIs

 By Ivo Donker — compiled with AI assistance (Claude & Gemini)

 Categories and examples checked on 2026-08-09
 

 
 When building AI applications, the center of gravity in software development shifts from training models to efficiently serving them. All categories and examples in this overview were checked on 2026-08-09. Inference hosting comprises the complete infrastructure layer that makes it possible to process prompts, run neural networks and return the generated tokens to the user in real time. Within the broader landscape, this category occupies a central position between application layers and data storage. Anyone wanting to understand where these hosting solutions fit within the overall AI stack can navigate through the complete [structure of the AI ecosystem](https://directory.llmnet.nl/en/ai-ecosysteem-categorieen) in which every infrastructure layer is clearly organized. To then weigh the right hosting model for a specific use case, the [interactive AI tool selector](https://directory.llmnet.nl/en/ai-tool-kiezer) provides a clear decision path based on latency, data residency and expected compute volumes.

 The inference hosting landscape can be broken down into three mainstream approaches: managed serverless API services, specialized GPU clouds, and custom containers on reserved compute. Each choice carries clear trade-offs between operational complexity, compute costs and control over data. This overview positions providers and technologies based on their category and architecture, independent of temporary brand promotion. This creates a neutral reference point for developers, architects and IT decision-makers.

 
## 1. The anatomy of inference hosting: GPU compute versus serverless APIs

 Inference is the process by which an already trained language model processes new input and generates tokens step by step. Unlike classic web applications, the compute load during inference is extremely intensive and mainly bound by the memory bandwidth and processing capacity of graphics processing units (GPUs) or specialized accelerators (NPUs and LPUs). To understand exactly how this hardware-level processing works, it helps to study the basic mechanisms of a prompt call; for that, read the in-depth explanation about [what happens under the hood during AI inference](https://leren.llmnet.nl/en/inference-uitgelegd). Managing this specific hardware requires advanced memory management, such as dynamically allocating KV caches (Key-Value caches) to retain earlier text context without exhausting video memory.

 The inference hosting market pits two main models against each other: the serverless abstraction layer and the direct GPU compute model. With serverless hosting, the customer buys a result per generated or processed token. The provider handles starting model instances, distributing load across clusters and the dynamic scaling process. With direct GPU compute, the customer rents virtual or physical machines with dedicated compute cards, with full management of the inference engine, the weights and the API routes resting with the end user. Between these extremes are hybrid forms such as managed container platforms that offer automatic scalability for custom-built model weights.

 
## 2. Serverless LLM APIs: Convenience, pay-per-token and multi-tenant architecture

 Serverless APIs for language models are the fastest way to integrate generative AI into applications. Providers in this category manage large-scale GPU clusters and make language models available through standardized endpoints. The user pays only for the processed input tokens and the generated output tokens. This model eliminates the need to invest in unused compute hardware during off-peak hours.

 In practice, serverless providers can be divided into two main types:

 
 
- Model-as-a-Service (MaaS) from model developers: APIs that provide direct access to proprietary models (such as OpenAI, Anthropic or Google Cloud Vertex AI). Here, the customer has no access to the model's underlying weights, but benefits from the highest performance per model class.
 
- Serverless operators of open-weight models: Platforms that host open-source models (such as Llama, Mistral or Qwen) on their own optimized infrastructure (examples include Together AI, Fireworks AI, Groq Cloud, Anyscale and Replicate).
 

 The strength of serverless hosting lies in its minimal operational burden. A development team doesn't need to set up Kubernetes clusters, update GPU drivers, or maintain complex inference servers. The main drawback of serverless multi-tenant platforms is the lack of guaranteed processing speed during peak hours. When thousands of users submit requests to the same API infrastructure simultaneously, queue time can increase substantially. In addition, processing privacy-sensitive company data through a shared multi-tenant environment raises additional governance and compliance issues.

 
## 3. Dedicated GPU clouds and containerized serving (vLLM, TGI, TensorRT-LLM)

 For organizations with strict requirements around data sovereignty, predictable latency or unique fine-tuned models, renting dedicated GPU capacity is often the preferred route. In this category, organizations rent specific GPU instances from major cloud providers (such as AWS, Google Cloud and Microsoft Azure) or from specialized GPU clouds (such as Lambda Labs, RunPod, CoreWeave and Hetzner). On these instances, the team runs its own container with an advanced inference engine.

 The choice of inference engine largely determines the eventual throughput and memory usage of the server. Three widely used open-source and proprietary engines dominate the market:

 
 
 
 Inference Engine | 
 Primary Focus | 
 Core Technology | 
 Typical Use Case | 
 

 
 
 
 
- vLLM
 
- High throughput, simple management
 
- PagedAttention for dynamic memory management
 
- Multi-user applications and general API hosting
 

 
 
- Text Generation Inference (TGI)
 
- Production readiness and safety
 
- Hugging Face integration, tensor parallelism
 
- Enterprise deployments of open models
 

 
 
- TensorRT-LLM
 
- Maximum hardware efficiency on NVIDIA
 
- Hardware-specific kernel optimization
 
- High-performance environments with low latency
 

 
 

 Those setting up dedicated GPUs can also combine the compute power with a local development environment or an on-premise test setup. For teams wanting to compare how these containerizable engines relate to desktop and edge solutions, the overview of [software for running LLMs locally](https://directory.llmnet.nl/en/lokale-llm-tools) provides a good starting point for hardware choices and local management.

 
## 4. Cold starts, TTFT and latency optimization in serverless compute

 Inference hosting has specific performance indicators that differ significantly from classic REST APIs. Where normal web servers focus on total response time, AI inference is evaluated across two separate phases: processing the input prompt and the subsequent generation of output tokens.

 The most important performance indicators are:

 
 
- Time to First Token (TTFT): The time that elapses between sending the prompt and receiving the very first generated character. This includes network time, any queue waiting time, and the compute time the GPU needs to process the entire prompt context at once (the prefill phase).
 
- Inter-Token Latency (ITL) / Time Per Output Token (TPOT): The average time the engine needs to generate each next token (the decode phase). This determines how fast the text 'streams' on the user's screen.
 
- Cold Start Latency: In serverless container environments that scale to zero, a model that may be tens of gigabytes in size must first be loaded from disk or network storage into the GPU's VRAM. This can lead to startup delays ranging from several seconds to even minutes.
 

 To work around slow TTFT and high cold starts, developers use techniques such as prompt caching, continuous batching and speculative decoding. Organizations also regularly deploy API aggregators to automatically distribute traffic across multiple compute clusters and backends. To see how intelligently switching between multiple provider endpoints works in practice to absorb outages and peak loads, we refer to the analysis on [the working principle of an LLM API aggregator](https://api.llmnet.nl/en/aggregator-uitleg).

 
## 5. Cost models compared: Per token, per GPU hour and reserved instances

 Financially managing inference hosting requires a thorough comparison of cost structures. Depending on scale and usage pattern, the most affordable option at low load can turn into the most expensive option at high, continuous volume.

 The three main cost models can be summarized as follows:

 
 
- Pay-per-token (Serverless): Ideal for fluctuating and unpredictable load. Costs scale exactly with the number of words processed. At low volumes, the initial investment is zero. At millions of requests per day, however, the marginal cost per token on serverless platforms becomes significantly higher than if the hardware were rented directly.
 
- Pay-per-GPU-hour (On-demand compute): Renting compute cards by the hour or second. This provides cost control under stable load, provided GPU utilization remains high. An idle GPU running 24/7 costs money regardless of the number of prompts processed.
 
- Reserved / Committed Use (Long-term contracts): Committing to GPU capacity for 1 to 3 years with a cloud provider. This yields discounts of 30% to 60% compared to on-demand prices, but requires an accurate estimate of long-term capacity needs.
 

 An in-depth breakdown of these financial trade-offs and calculation examples is included in the guide on [cost models compared per AI category](https://directory.llmnet.nl/en/wat-ai-tools-kosten-kostenmodellen-per-categorie-vergeleken), which extensively breaks down the balance between variable token consumption and fixed infrastructure costs.

 
## 6. Data residency, GDPR and EU sovereignty in GPU infrastructure

 A crucial aspect when selecting hosting infrastructure is the legal and geographic location of data processing. Under the General Data Protection Regulation (GDPR) and the European AI Act, organizations must be able to demonstrate precisely where personal data and confidential prompts are processed and stored.

 Many international serverless API providers process prompts by default in data centers in the United States or use global load balancing, where the exact country of processing can vary per request. In addition, some commercial platforms have terms of service stating that submitted data (unless explicitly opted out via enterprise clauses) may be used for retraining future models.

 This creates three strict conditions for European organizations:

 
 
- Sovereign EU data centers: Guaranteed inference processing within the European Economic Area (EEA) to prevent data transfer to third countries.
 
- Zero Data Retention (ZDR): Guarantees that submitted prompts and generated responses are immediately removed from the hosting server's volatile memory after the API call completes.
 
- Data Processing Agreements (DPA): Contractual agreements that explicitly exclude the use of customer data for model training or quality evaluations by third parties.
 

 For organizations for which data protection and local legislation are a hard requirement, the platform includes a specialized overview of [AI tools and hosting services with EU or Dutch hosting](https://directory.llmnet.nl/en/ai-tools-met-eu-of-nl-hosting-wat-er-is-en-waar-je-op-let), including points of attention regarding legal ownership rights and data location.

 
## 7. Observability and telemetry at the inference level

 Managing a production infrastructure for AI doesn't stop at setting up a GPU server or API integration. Because language models are stochastic in nature and hardware load can vary widely per request, continuous monitoring at the infrastructure level is essential.

 At the lowest layer of the infrastructure, hardware statistics are monitored, such as VRAM occupancy, GPU temperature, power consumption and PCIe bandwidth. At the application layer, the focus shifts to logging prompts, token consumption, processing times and content anomalies. To make the performance, costs and error margins of this hosting layer transparent, administrators use specialized monitoring software. For a complete overview of tools in this area, see the guide on [LLM observability tools for tracing and monitoring](https://directory.llmnet.nl/en/llm-observability-tools).

 
## 8. Selection criteria and decision-making framework by organization type

 Which inference hosting solution fits best depends on the organization's maturity level and profile. There is no universally superior solution; the optimal model is determined by the project's constraints.

 The decision-making framework below shows the typical preferred routes per type of organization:

 
 
- Startups and prototyping: Choose Serverless multi-tenant APIs. The focus is on rapid iteration, minimal fixed costs and zero infrastructure management. Only once a stable and high volume is reached does switching to your own compute become rational.
 
- Mid-sized SaaS companies with their own fine-tunes: Choose Serverless dedicated container hosting or managed GPU clouds (such as RunPod, Lambda or AWS SageMaker with vLLM). This offers the flexibility of a custom model architecture without the complexity of a physical data center.
 
- Enterprise & financial / medical sector: Choose Dedicated GPU instances within a private cloud VPC or on-premise GPU clusters. Here, data sovereignty, Zero Data Retention guarantees, and strict compliance with the GDPR and AI Act take priority over initial infrastructure costs.
 

 
## 9. Conclusion and future outlook

 Inference hosting has developed into a full-fledged and versatile pillar within AI infrastructure. Where the landscape in the early years was dominated by a limited number of brand-specific APIs, developers and organizations now have a broad spectrum of choices. From extremely fast serverless token APIs to fully controlled, dedicated GPU clusters in European data centers: a suitable architecture is available for every performance requirement, privacy profile and budget.

 In the coming years, the efficiency of inference hosting will further increase through breakthroughs in specialized hardware, better quantization techniques and smarter orchestration layers. Successfully deploying AI applications therefore remains dependent not only on the quality of the chosen model, but equally on the thoughtful selection and management of the underlying hosting infrastructure.

 

 
 Last check of categories and examples: 2026-08-09 | llmnet.nl — The independent knowledge network for AI and LLMs in the Netherlands