Hugging Face
0.0.1 commercialHugging Face is a platform providing pre-trained machine learning models, datasets, and tools for natural language processing and computer vision tasks.
hf endpoints hardware --vendor aws --region eu-west-1 hf endpoints deploy gpt-oss-120b-vllm \ --repo openai/gpt-oss-120b \ --engine vllm --custom-image vllm/vllm-openai:v0.23.0 \ --tensor-parallel-size 8 hf buckets settings username/my-bucket --private
Summary
Hugging Face is a commercial ai-infrastructure platform that hosts machine learning models, datasets, and demo applications (Spaces) on a Git-based hub, alongside libraries for building, training, and deploying them. It runs primarily as a hosted SaaS hub, backed by client libraries and a CLI for scripting and agent access, with paid tiers covering dedicated inference endpoints and org-level access controls. It targets machine learning engineers and applied researchers building or shipping models, rather than security teams directly, though its resource-group permissions and audit-log endpoints suggest platform and access-management concerns for organizations running it at scale. Its own documentation lists it alongside adjacent tools like Transformers, Diffusers, and Gradio rather than naming external competitors, positioning it as the shared hub those tools build on.
Hugging Face is a platform providing pre-trained machine learning models, datasets, and tools for natural language processing and computer vision tasks.
What Hugging Face answers
Can I scope permissions more finely than a single org-wide role?
yes, access controls apply per resource group, so Jobs can stay open to everyone while Inference Endpoints or blog publishing are restricted to specific groups
What can I use to track who did what across the organization?
an audit-log export endpoint alongside membership and resource-group endpoints, aimed at admins managing access at scale rather than individual model builders
Can agents and CLI tools authenticate and act on my behalf?
the CLI and its installer set up a skill file that agents like Claude Code can read directly, and service-account tokens can be issued, scoped, and revoked through dedicated endpoints
How do I find a specific run among a large set of jobs?
jobs pages support filtering by label, either through clickable chips of the most-used labels with counts or a free-form key-value filter for labels not surfaced as chips
Where do the models and datasets I use actually run?
either on Hugging Face's own hosted inference infrastructure and endpoints, or exported to run on AWS, Azure, or Google Cloud through their respective deployment integrations
Do I need to rewrite access requests if I change how I gate a dataset or model?
access-request handling now works in batches, so approving or denying multiple pending requests to a dataset or model repo is a single call rather than one per user
Release history
- docs update
Hugging Face CLI v1.29.0 adds bucket visibility controls, hardware discovery, and managed engine deployment with parallelism flags
└──▷ TRY ITBefore deploying, find valid hardware combos in your region and see live quota and pricing to pick the right instance.$ hf endpoints hardware --vendor aws --region eu-west-1
Deploy a multi-GPU model with vLLM, explicitly spreading across all 8 accelerators so the API accepts the configuration.$ hf endpoints deploy gpt-oss-120b-vllm \ --repo openai/gpt-oss-120b \ --engine vllm --custom-image vllm/vllm-openai:v0.23.0 \ --tensor-parallel-size 8
Lock a bucket down to private to prevent unintended public access.$ hf buckets settings username/my-bucket --private
- ›Adds
hf buckets settings <bucket> --privateand--publicflags to switch a bucket between private and public visibility. - ›Adds
hf endpoints hardwaresubcommand to list deployable hardware combinations with vendor, region, accelerator, instance type, instance size, memory, GPU memory, price per hour, quota, and status. - ›Adds
--vendor,--region,--accelerator, and--instance-typefilter flags tohf endpoints hardwareto narrow results to the exact values you intend to pass tohf endpoints deploy. - ›Adds
--allflag tohf endpoints hardwareto include hardware that is deprecated, temporarily unavailable, or out of quota (hidden by default). - ›Adds
--engineflag tohf endpoints deployto run a container as a managed engine (vllm,sglang,tgi,tei,llamacpp,hf-serve, …), unlocking engine-specific settings.
+2 moreshow less
- ›Adds
--tensor-parallel-sizeand--data-parallel-sizeflags tohf endpoints deployandhf endpoints update, writing parallelism config into the engine'smodel.imagefield that the API validates against the instance's accelerator count. - ›Adds
--engineflag tohf endpoints updateas the only CLI path to change an existing endpoint's image, replacingmodel.imageentirely rather than patching it.
└──▷ BREAKING ON UPGRADE- !The API now rejects vLLM and SGLang deployments where
--tensor-parallel-sizeand--data-parallel-sizeare both unset, because those engines default to one accelerator while the endpoint receives every accelerator of its instance.
- ›Adds
- 0.0.1
API surface changed: +6 endpoints, 5 modified
API CHANGEAPI surface changed: +6 endpoints, 5 modified
- + GET /api/users/{username}/followers
- + GET /api/users/{username}/following
- + GET /api/users/{username}/following/orgs
- + GET /api/{repoType}/{namespace}/{repo}/duplicate/status
- + PATCH /api/collections/{namespace}/{slug}-{id}/items/{itemId}
- + PATCH /api/collections/{namespace}/{slug}/items/{slug}
- ~ GET /api/datasets/{namespace}/{repo}/lfs-files: param direction (query) added; param sort (query) added
- ~ GET /api/models/{namespace}/{repo}/lfs-files: param direction (query) added; param sort (query) added
- ~ GET /api/spaces/{namespace}/{repo}/lfs-files: param direction (query) added; param sort (query) added
- ~ POST /api/repos/create: response schema changed
- ~ POST /api/{repoType}/{namespace}/{repo}/duplicate: response schema changed
- ›New endpoint GET
/api/users/{username}/followers - ›New endpoint GET
/api/users/{username}/following - ›New endpoint GET
/api/users/{username}/following/orgs - ›New endpoint GET
/api/{repoType}/{namespace}/{repo}/duplicate/status - ›New endpoint PATCH
/api/collections/{namespace}/{slug}-{id}/items/{itemId}
+6 moreshow less
- ›New endpoint PATCH
/api/collections/{namespace}/{slug}/items/{slug} - ›GET
/api/datasets/{namespace}/{repo}/lfs-files: param direction (query) added; param sort (query) added - ›GET
/api/models/{namespace}/{repo}/lfs-files: param direction (query) added; param sort (query) added - ›GET
/api/spaces/{namespace}/{repo}/lfs-files: param direction (query) added; param sort (query) added - ›POST
/api/repos/create: response schema changed - ›POST
/api/{repoType}/{namespace}/{repo}/duplicate: response schema changed
- 0.0.1
API surface changed: 3 modified
API CHANGEAPI surface changed: 3 modified
- ~ GET /api/datasets/{namespace}/{repo}/user-access-request/{status}: response schema changed
- ~ GET /api/models/{namespace}/{repo}/user-access-request/{status}: response schema changed
- ~ GET /api/users/{username}/overview: response schema changed
- ›GET
/api/datasets/{namespace}/{repo}/user-access-request/{status}: response schema changed - ›GET
/api/models/{namespace}/{repo}/user-access-request/{status}: response schema changed - ›GET
/api/users/{username}/overview: response schema changed
- 0.0.1
Hugging Face now publishes an API — 316 endpoints across 27 areas: Spaces, Datasets, Models, …
- ›Spaces (41 endpoints) — Get information from all Spaces on the Hub.
- ›Datasets (36 endpoints) — Get information from all datasets on the Hub.
- ›Models (36 endpoints) — Get information from all models on the Hub.
- ›SCIM (28 endpoints) — Use the SCIM API to control and manage your hub Enterprise organization manage members' access. - Must be organization owner - Use Access token with write permission on organization - Organization must be Enterprise…
- ›Jobs (23 endpoints) — The following endpoints manage jobs.
+4 moreshow less
- ›Discussions (20 endpoints) — The following endpoints manage discussions.
- ›Collections (18 endpoints) — Use Collections to group repositories from the Hub (Models, Datasets, Spaces and Papers) on a dedicated page.
- ›Organizations (16 endpoints) — The following endpoints let you interact with Hub Organizations and their members.
- ›19 more areas: Buckets, Users, Agentic Provisioning, Resource groups, Service Accounts, Paper pages, Webhooks, Notifications, Kernels, OAuth, Documentation, Repositories, SQL Console, Inference Endpoints, Repository Search, Agents, Auth, Container Registry, Tokens
- Build Spaces with AI Agents
Hugging Face Spaces now supports AI agent-driven Space creation for models, papers, or local folders.
- ›New option on the Space creation page at
huggingface.co/new-spaceto build a Space using an AI agent, generating a command you paste into your agent to build and iterate automatically. - ›AI agent Space builder supports targeting a model, paper, or local folder as the source for the generated Space.
- ›New option on the Space creation page at
- Egress metrics for users and organizations
Hugging Face adds egress usage metrics to user and organization dashboards, with per-member breakdowns.
- ›Users can now view their CDN egress usage directly in the Hugging Face dashboard.
- ›Organization dashboards now include a per-user egress breakdown showing how much data each member consumes.
- Filter Jobs by Label
Hugging Face Jobs pages now support filtering by label via clickable chips and free-form
key=valueinput.- ›Adds label-based filtering to user and organization Jobs pages, with most-used labels surfaced as clickable chips showing job counts.
- ›Supports free-form
key=valuelabel input to filter by any label, including those not shown as chips.
- Granular Feature Access
Hugging Face adds per-resource-group feature access controls, enabling fine-grained permissions beyond org-wide roles.
- ›Enables feature access controls at the resource group level, so permissions like Jobs, Inference Endpoints, and blog publishing can be scoped independently per group rather than only by organization role.
- MCP Server Enhancements
Hugging Face MCP Server gains unified
hf_fstool and Sandbox execution environments for AI assistants.- ›Adds the
hf_fstool — a single interface covering repositories, storage, documentation, and papers, with built-in search, operable in just over 1,000 tokens. - ›Adds Sandboxes, giving assistants secure execution environments attached to buckets and repositories for dataset analysis, model training, and Space creation.
- ›Adds the