Access private and gated models
Use a read token from an account with access to the model. For gated models, accept the model’s license and obtain any required approval first.
Integration
Hugging Face integration for variables and secrets
Give Wodby apps access to Hugging Face models through a reusable access-token integration. Connected services receive HF_TOKEN, which Hugging Face libraries and vLLM can use to download private or gated models your account can access.
Variables
Provide the token to your runtime
Wodby supplies the token as HF_TOKEN to connected services, keeping model-access credentials out of your application repository.
Supported workflows
How Hugging Face fits into Wodby
Each supported integration kind maps Hugging Face into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider configuration into workloads.
Variables
Access token
Provide HF_TOKEN to services that download private or gated models from Hugging Face.
- Create a read token for an account with access to the models your app needs.
- Accept the license and obtain any required approval for each gated model using the same account.
- Connected services receive HF_TOKEN for Hugging Face libraries, vLLM, or application code that reads it.
Configuration surfaced to workloads
HF_TOKEN
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Hugging Face.
Stack fit
Stacks that commonly pair with Hugging Face
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
Python
Stack
Python application stack for custom web apps, APIs, workers, and automation services.
Use Python services that load Hugging Face models with HF_TOKEN supplied by the integration.
View stackNext.js
Stack
Next.js application stack for frontend and full-stack projects that need a reusable deployment setup.
Next.js apps can receive provider configuration through the services that need it instead of scattering values across the repository.
View stackNode.js
Stack
Node.js application stack for APIs, workers, and custom services with a repeatable runtime setup.
Node.js services can receive provider settings as runtime variables instead of repo-local env files.
View stackLaravel
Stack
Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.
Laravel is a strong fit when provider credentials and configuration should stay centralized at the stack layer.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.