Choose language
  • NL
  • Current language: EN
Get in touch

Insights

Build or buy: assembling the AI stack without locking yourself in

· Architecture

Build or buy: assembling the AI stack without locking yourself in

The build-or-buy conversation is almost always held too early, and about the wrong thing. Too early, because the question cannot be answered until you know which layer you mean. About the wrong thing, because "AI" is not a purchase — it is a stack of seven independent choices.

That last point is where the money is. The layers below can be chosen separately. Nothing obliges you to take your compute from the same supplier as your models, or your observability from the same supplier as your orchestration. The most expensive mistake we see in mid-sized organisations is not buying the wrong thing; it is buying one suite because it was one conversation.

The seven layers

Each layer has its own market, its own switching cost and its own rate of change. That last one decides whether building is sensible more often than anything else: in a layer that shifts every quarter, building means rebuilding.

  • Compute — where the GPUs are and who runs them
  • Model serving — how a model becomes reachable as an API
  • Training and fine-tuning — adapting an existing model to your work
  • Data and vectors — where your knowledge lives and how it is searched
  • Orchestration and agents — what happens in what order
  • Observability and evaluation — whether it works, and whether it keeps working
  • Governance and guardrails — what the system may not do, and how you show it

The landscape

Below are twenty solutions per layer that a mid-sized European organisation will realistically encounter, plus the self-build option in every layer. It is deliberately not a ranking: no market-share figure is published for most of these companies, and ordering them as though one existed would be inventing the most authoritative-looking number on the page.

140 of 140 solutions

SolutionTypeWhere it fits
AWSComputeHyperscalerEC2 GPU instances and SageMaker. The default when the rest of the estate is already there.
Microsoft AzureComputeHyperscalerND-series GPUs and Azure ML. Usually chosen because the enterprise agreement already exists.
Google CloudComputeHyperscalerGPUs and TPUs behind Vertex AI. The only hyperscaler offering its own training silicon.
CoreWeaveComputeManagedKubernetes-native GPU cloud built for AI rather than adapted to it.
LambdaComputeManagedLong-running training clusters with persistent storage.
NebiusComputeManagedEuropean GPU capacity; relevant where data residency is a constraint.
RunPodComputeManagedPer-second GPU rental, community and secure tiers.
Vast.aiComputeManagedMarketplace pricing. Cheapest per hour, most variable in reliability.
ModalComputeManagedServerless GPU with a Python-native developer experience.
PaperspaceComputeManagedDigitalOcean's GPU platform; simple pricing, smaller catalogue.
ScalewayComputeManagedFrench provider with EU-only regions.
OVHcloudComputeManagedEuropean hosting at scale; strong on data-residency guarantees.
HetznerComputeManagedGerman provider. Very low cost, limited GPU catalogue.
Oracle Cloud InfrastructureComputeHyperscalerAggressive GPU pricing and large reserved capacity.
IBM CloudComputeHyperscalerRelevant mainly where watsonx is already in the estate.
CrusoeComputeManagedEnergy-first GPU cloud; competitive on cost per hour at scale.
Together AIComputeManagedCompute and inference in one contract.
SpheronComputeManagedAggregates bare-metal capacity across several providers.
NorthflankComputeManagedDeploys containers to GPUs without running Kubernetes yourself.
Own GPUs, on-premise or colocatedComputeSelf-buildLowest marginal cost at sustained high utilisation. Carries procurement lead times, power, cooling and a hardware refresh cycle. Rarely justified below continuous multi-GPU load.
OpenAI APIModel servingManagedThe broadest frontier catalogue and the most mature tooling around it.
Anthropic APIModel servingManagedFrontier models with a strong position on coding and long-document work.
Google Gemini APIModel servingManagedLong context and native multimodality; often the cheapest capable tier.
Azure OpenAI ServiceModel servingHyperscalerOpenAI models inside an Azure tenancy, with EU region options.
Amazon BedrockModel servingHyperscalerOne API across several model families, inside an AWS account.
Google Vertex AIModel servingHyperscalerGemini plus third-party models with enterprise controls.
Mistral AIModel servingManagedEuropean provider; relevant where EU processing is contractual rather than preferred.
CohereModel servingManagedEnterprise focus, strong retrieval and reranking models.
Together AIModel servingManagedLarge open-weights catalogue at low cost per token.
Fireworks AIModel servingManagedOptimised serving of open models; competitive on latency.
BasetenModel servingManagedBring your own model, deployed and scaled for you.
ReplicateModel servingManagedContainer-packaged models with per-second billing.
GroqModel servingManagedVery high output speed on a fixed model set.
CerebrasModel servingManagedWafer-scale inference; speed at the top of the market.
OpenRouterModel servingManagedOne key across many providers. Useful for comparison and failover.
Hugging Face Inference EndpointsModel servingManagedAny model on the Hub, deployed to a managed endpoint.
AnyscaleModel servingManagedRay-based serving for teams already using Ray.
vLLMModel servingOpen sourceThe de facto open serving engine. High throughput, you operate it.
OllamaModel servingOpen sourceLocal and small-scale serving; the fastest way to try an open model.
vLLM or TGI on your own GPUsModel servingSelf-buildFull control of model, version and data path, and the lowest cost per token at sustained volume. You own the uptime, the upgrades and the GPU capacity planning.
OpenAI fine-tuningTraining and fine-tuningManagedSupervised fine-tuning on hosted models. No infrastructure to run.
Azure AI FoundryTraining and fine-tuningHyperscalerFine-tuning and evaluation inside an Azure tenancy.
Vertex AI TrainingTraining and fine-tuningHyperscalerManaged training jobs with TPU or GPU backing.
Amazon SageMakerTraining and fine-tuningHyperscalerThe broadest managed training toolchain; steep learning curve.
Together AI fine-tuningTraining and fine-tuningManagedLoRA and full fine-tunes on open models, deployed on the same platform.
Fireworks fine-tuningTraining and fine-tuningManagedTuning paired directly with optimised serving.
PredibaseTraining and fine-tuningManagedFine-tuning aimed at small task-specific models rather than frontier ones.
Hugging Face AutoTrainTraining and fine-tuningManagedLow-code tuning on the Hub.
AxolotlTraining and fine-tuningOpen sourceThe most widely used open fine-tuning harness.
UnslothTraining and fine-tuningOpen sourceMemory-efficient tuning; makes single-GPU work feasible.
LLaMA-FactoryTraining and fine-tuningOpen sourceBroad model coverage with a usable interface.
Weights & BiasesTraining and fine-tuningManagedExperiment tracking. Not training itself, but what makes it repeatable.
Determined AITraining and fine-tuningOpen sourceCluster scheduling and hyperparameter search.
Ray TrainTraining and fine-tuningOpen sourceDistributed training for teams already running Ray.
Databricks Mosaic AITraining and fine-tuningManagedTraining tied to a lakehouse; strong where the data already lives there.
ModalTraining and fine-tuningManagedServerless training runs without a standing cluster.
Lightning AITraining and fine-tuningManagedStudio environments around PyTorch Lightning.
Nebius AI StudioTraining and fine-tuningManagedTuning on European infrastructure.
Google Colab EnterpriseTraining and fine-tuningHyperscalerNotebook-based experimentation with managed backends.
DeepSpeed or Ray on your own clusterTraining and fine-tuningSelf-buildNecessary for genuinely novel training work. For adapting an existing model to your data it is almost always more machinery than the problem needs.
pgvectorData and vectorsOpen sourceVector search inside the Postgres you already run. The right first answer for most mid-sized firms.
PineconeData and vectorsManagedZero-operations vector search with built-in embedding and reranking.
QdrantData and vectorsOpen sourceRust engine with fine-grained filtering and quantisation. Cloud or self-hosted.
WeaviateData and vectorsOpen sourceHybrid search and multi-tenancy; self-hosting expects Kubernetes.
MilvusData and vectorsOpen sourceBuilt for billion-scale collections.
ChromaData and vectorsOpen sourceThe quickest path from prototype to working retrieval.
LanceDBData and vectorsOpen sourceMultimodal and file-native; no server to run.
ElasticsearchData and vectorsManagedMature keyword search with vectors added. Strong hybrid retrieval.
OpenSearchData and vectorsOpen sourceThe open fork; the same hybrid strengths without the licence.
RedisData and vectorsManagedVector search alongside a cache you may already operate.
MongoDB Atlas Vector SearchData and vectorsManagedVectors beside documents in one database.
Azure AI SearchData and vectorsHyperscalerRetrieval with enterprise access controls built in.
Vertex AI Vector SearchData and vectorsHyperscalerGoogle's managed index; scales without tuning.
Amazon OpenSearch ServerlessData and vectorsHyperscalerManaged hybrid retrieval inside AWS.
Databricks Vector SearchData and vectorsManagedRetrieval governed by the same catalogue as the rest of the data.
Snowflake Cortex SearchData and vectorsManagedRetrieval where the warehouse already is.
VespaData and vectorsOpen sourceServing and ranking at very large scale; substantial operational weight.
TurbopufferData and vectorsManagedObject-storage-backed vectors; unusually low cost at rest.
SingleStoreData and vectorsManagedTransactional and vector workloads in one engine.
pgvector on your existing PostgresData and vectorsSelf-buildNo new vendor, no new backup regime, no new access model. The ceiling is real but most mid-sized corpora never reach it.
LangChainOrchestration and agentsOpen sourceThe largest ecosystem of connectors and the most examples to copy.
LangGraphOrchestration and agentsOpen sourceExplicit state machines for agents; far easier to reason about than free-form chains.
LlamaIndexOrchestration and agentsOpen sourceRetrieval-first framework with strong document handling.
Semantic KernelOrchestration and agentsOpen sourceMicrosoft's orchestration layer; natural fit alongside .NET.
HaystackOrchestration and agentsOpen sourceProduction-oriented pipelines from deepset.
CrewAIOrchestration and agentsOpen sourceRole-based multi-agent orchestration.
AutoGenOrchestration and agentsOpen sourceMicrosoft Research's multi-agent conversation framework.
Pydantic AIOrchestration and agentsOpen sourceTyped, validated agent definitions. Small surface, few surprises.
TemporalOrchestration and agentsOpen sourceDurable execution. The right answer when a workflow must survive a restart.
PrefectOrchestration and agentsOpen sourcePython-native workflow orchestration with a managed option.
Apache AirflowOrchestration and agentsOpen sourceScheduled pipelines; the incumbent in most data teams.
n8nOrchestration and agentsOpen sourceVisual automation, self-hostable. Popular in European mid-market.
MakeOrchestration and agentsManagedVisual automation with a large connector library.
ZapierOrchestration and agentsManagedThe lowest-effort route to connecting existing SaaS.
Microsoft Copilot StudioOrchestration and agentsManagedAgents inside Microsoft 365, governed by existing tenancy controls.
Google Agent BuilderOrchestration and agentsHyperscalerAgent construction and deployment on Vertex.
Amazon Bedrock AgentsOrchestration and agentsHyperscalerManaged agents with action groups inside AWS.
DifyOrchestration and agentsOpen sourceLow-code application builder over your own models.
FlowiseOrchestration and agentsOpen sourceVisual chain building on top of LangChain.
Direct API calls with your own state machineOrchestration and agentsSelf-buildFor a single well-understood workflow this is often less code than the framework, and it never breaks on a framework upgrade. It stops scaling once you have several agents sharing state.
LangfuseObservability and evaluationOpen sourceOpen, self-hostable tracing and prompt management. The common default.
LangSmithObservability and evaluationManagedThe smoothest path if you already build with LangChain or LangGraph.
BraintrustObservability and evaluationManagedEvaluation-first: experiments, scoring and review as the primary object.
Arize AXObservability and evaluationManagedProduction monitoring with drift detection.
Arize PhoenixObservability and evaluationOpen sourceNotebook-first tracing for experimentation.
LangWatchObservability and evaluationOpen sourceSelf-hosted tracing with online evaluation and guardrails together.
Weights & Biases WeaveObservability and evaluationManagedTracing and evals beside experiment tracking.
GalileoObservability and evaluationManagedFast inline scoring aimed at intercepting output in production.
Confident AI (DeepEval)Observability and evaluationOpen sourceA test-suite model for LLM behaviour; runs in CI.
TruLensObservability and evaluationOpen sourceFeedback functions for RAG quality.
HeliconeObservability and evaluationOpen sourceA proxy that gives logging and caching with a one-line change.
PromptLayerObservability and evaluationManagedPrompt versioning and comparison for non-engineers.
Datadog LLM ObservabilityObservability and evaluationManagedSensible where Datadog is already the monitoring system.
New Relic AI MonitoringObservability and evaluationManagedSame argument, different incumbent.
OpenTelemetry GenAIObservability and evaluationOpen sourceThe emerging standard. Vendor-neutral, and what keeps you portable.
WhyLabsObservability and evaluationManagedData and model drift monitoring.
TrueFoundryObservability and evaluationManagedServing and observability in one platform.
OpenlayerObservability and evaluationManagedTesting and monitoring with a strong evaluation story.
HumanloopObservability and evaluationManagedPrompt management with domain-expert review built in.
OpenTelemetry into your existing stackObservability and evaluationSelf-buildIf you already run Grafana or the ELK stack, emitting spans into it costs little and adds no vendor. You give up the LLM-specific evaluation features, which is the trade.
NVIDIA NeMo GuardrailsGovernance and guardrailsOpen sourceProgrammable conversational rails; topic and flow boundaries.
Guardrails AIGovernance and guardrailsOpen sourceInput and output validators with a shared library of checks.
Azure AI Content SafetyGovernance and guardrailsHyperscalerManaged content filtering with severity levels.
Amazon Bedrock GuardrailsGovernance and guardrailsHyperscalerPolicy enforcement applied across models in Bedrock.
Vertex AI safety filtersGovernance and guardrailsHyperscalerConfigurable safety thresholds on Google-served models.
LakeraGovernance and guardrailsManagedPrompt-injection and jailbreak defence.
Protect AIGovernance and guardrailsManagedModel and supply-chain security scanning. Now part of Palo Alto Networks.
Robust IntelligenceGovernance and guardrailsManagedAutomated red-teaming and runtime protection. Part of Cisco.
Credo AIGovernance and guardrailsManagedGovernance registry mapped to regulatory frameworks, including the EU AI Act.
Holistic AIGovernance and guardrailsManagedRisk assessment and compliance reporting.
IBM watsonx.governanceGovernance and guardrailsManagedModel inventory, risk and lifecycle documentation.
Fiddler AIGovernance and guardrailsManagedExplainability and monitoring for regulated use.
ArthurGovernance and guardrailsManagedPerformance and bias monitoring in production.
BifrostGovernance and guardrailsOpen sourceAn AI gateway that applies the same policy to every model call.
LLM GuardGovernance and guardrailsOpen sourceA practical scanner set for inputs and outputs.
Microsoft PresidioGovernance and guardrailsOpen sourcePersonal-data detection and redaction. Directly useful under the GDPR.
RebuffGovernance and guardrailsOpen sourcePrompt-injection detection.
VijilGovernance and guardrailsManagedAgent trust evaluation and certification.
TrustibleGovernance and guardrailsManagedAI Act obligation tracking and evidence collection.
Policy checks in your own gatewayGovernance and guardrailsSelf-buildYou already need a gateway for keys and rate limits; putting redaction and logging there keeps one enforcement point. What you do not get is a maintained attack library, which is the part that ages fastest.

What most organisations miss

Three things come up in nearly every conversation.

The first is that building rarely means building everything. In almost every layer the sensible self-build option is small and specific: pgvector in the Postgres you already run, or policy checks in the gateway where you already manage keys and rate limits. That is a different proposition from running your own inference platform.

The second is that switching cost only counts if you work it out in advance. Ask of every layer: what would it cost to leave this in eighteen months? If the answer is unknown, that is the answer.

The third is that the AI Act does not transfer with the purchase. For most applications you are the provider, whoever's model sits underneath. A supplier can give you documentation; it cannot take on your obligation.

The framework

Ten dimensions, applied per use case and per layer. They rarely all point the same way — which is what makes it useful, because where they diverge is where the tension is.

Request the scoring grid

The framework above is complete: all ten dimensions and what each one means. What sits behind this is the scoring grid — the weights, the five anchors per dimension, and the thresholds that separate building from buying.

You receive: the weighted scoring grid, anchors per dimension, thresholds and a worked example.

Where this usually lands

For mid-sized organisations this rarely ends at "build" and rarely at "buy". It ends at compose: buy the layer, own the part that is yours. That part is almost always the same — your data, your prompts, your evaluation set and your interface. It is precisely the part suppliers give away most easily and replace least well.