WORKLOAD GUIDE

Run a chatbot or AI agent

Separate the model that produces answers from the application that handles users, tools and data. They can run on different services.

Four checks before you commit.

Start with your requirements. A memory figure alone does not prove a workload will run well.

Model access
Check that the service supports the model, context size and response format your application needs.
Application runtime
Your web app or agent may need its own hosting even when a provider runs the model.
Tools and permissions
Give an agent only the permissions its task needs. Review what it may send to external tools.
Real usage
Try realistic prompts, tool calls and concurrent requests before committing to an infrastructure plan.

Choose how much you want to manage.

These routes explain model serving. Check support for your exact model and requirements.

LESS INFRASTRUCTURE TO MANAGE

Hosted model API

Your app sends requests to a provider that already serves the model.

Responsibilities and costs
You manage
Connect the API and handle responses.
Control
Choose from the provider’s supported models and settings.
Billed for
Often tokens, requests or another usage unit.
Check first
Model availability, rate limits and data terms.
Find a suitable route for Hosted model API →

CHOOSE A MODEL AND A SERVICE

Managed endpoint

Deploy a model to a managed serving environment.

Responsibilities and costs
You manage
Configure the model, hardware and scaling.
Control
More deployment choices; access varies by service.
Billed for
Often provisioned compute time; check idle billing.
Check first
Supported runtimes, cold starts and minimum capacity.
Find a suitable route for Managed endpoint →

MORE CONTROL, MORE OPERATIONS

Self-managed runtime

Run your serving software on cloud compute you configure.

Responsibilities and costs
You manage
Deploy, secure, monitor and maintain the runtime.
Control
Choose compatible software and instance settings.
Billed for
Compute, storage, transfer and related services.
Check first
Memory fit, reliability and maintenance effort.
Find a suitable route for Self-managed runtime →
What makes a complete configuration?
01
Model

Name, revision, licence and intended task.

02
Runtime

Serving software, dependencies and deployment support.

03
Compute

Enough usable memory, suitable hardware and capacity.

04
Service

Region, access, storage, monitoring and availability.

Products to investigate.

2 alphabetical catalog examples tagged for this goal. These are starting points to verify, not a ranking or a guarantee of model support.

We currently earn no commission from these links. How we fund this site

OFFICIAL DOCUMENTATION / FURTHER READING

Hugging Face: endpoint configuration (opens in a new tab)Hugging Face: repository licences (opens in a new tab)Hugging Face: endpoint billing (opens in a new tab)

Editorial references checked 11 October 2026. Product features and terms can change; confirm the current documentation before purchasing.