Providers¶
Providers are Wodby's definitions for supported third-party services. A provider defines:
- which integration types it supports
- which fields or auth methods are required
- which environment variables it exposes, if it is a variable provider
- any provider-specific setup flow such as OAuth or scope selection
When you create a new integration, you first choose the provider and then fill in the fields required by that provider.
Provider changes are published as new revisions. New integrations use the current revision. Existing integrations can be advanced by a compatible managed rollout or remain pinned until they are updated explicitly.
If you are choosing by task rather than by vendor, start with Integration types and then jump to the matching provider group from there.
How provider pages are organized¶
In the documentation navigation, providers are grouped by the integration types they support, such as Kubernetes, databases, storage, Git, CI, registry, SMTP, Application Access, and VPN nodes.
Each provider group starts with its own Overview page that explains what that group is for before listing individual providers.
Variable providers have their own group because they are usually used to inject reusable environment variables rather than to create infrastructure resources.
Some providers support more than one type. Those providers can appear in more than one navigation group.
Built-in providers¶
Most providers shown in the dashboard are built in and maintained by Wodby. Their setup details are documented in the Providers section of this documentation.
Custom variable providers¶
If you only need to inject environment variables and there is no built-in provider for that service, you can create your own variable provider from the dashboard. Providers can be created interactively, from a local manifest, or from a Git repository containing one or several provider manifests.
The new variable provider form has an Owner selector. Choose Organization <organization> for an organization-owned provider or Project <project> for a project-owned provider.
Custom variable providers are useful when:
- you need a provider that Wodby does not ship yet
- you want to standardize a set of environment variables across multiple apps
- you want to manage service credentials centrally instead of repeating them in each app
Custom provider machine names are namespaced by organization. Git-backed providers can be updated manually or from matching branch and semantic-version tag events. See Custom variable providers for the manifest, Git layout, update, task, and sharing workflows.