Keep workloads private
Use the provider to expose services only to approved operators or networks instead of the public internet.
Integration
Tailscale integrations on Wodby
Use Tailscale to give Wodby workloads a private network path into internal services, operator-only environments, or gateway stacks that should stay off the public internet.
VPN
Reach internal systems
Apps and automation services can connect to internal APIs, databases, or tools through one reusable network path.
Reuse the same access model
Carry the same private networking setup across development, staging, and production where appropriate.
Supported workflows
How Tailscale fits into Wodby
Each supported integration kind maps Tailscale into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.
VPN
Tailscale network
Use Tailscale to connect workloads to private networks and internal services.
- Reach internal resources that are not exposed on the public internet.
- Useful for gateway, automation, or operator-facing workloads that should stay private by default.
- Keep one reusable network access pattern across multiple environments.
Configuration surfaced to workloads
TAILSCALE_CLIENT_IDTAILSCALE_CLIENT_SECRET
Configuration surface
Values teams usually configure for Tailscale
Wodby keeps these values at integration level and makes them available to the workflows or service containers that need them.
TAILSCALE_CLIENT_IDTAILSCALE_CLIENT_SECRET
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 Tailscale.
Stack fit
Stacks that commonly pair with Tailscale
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.
OpenClaw
Stack
Private OpenClaw gateway stack for always-on agent workflows with integrations such as Tailscale.
OpenClaw is the most direct stack pairing because the gateway is commonly kept private behind Tailscale.
View stackTailscale
Stack
Tailscale integration stack for private networking between apps, services, and operators.
The dedicated Tailscale stack is the obvious fit when networking itself is part of the workload you are operating.
View stackNode.js
Stack
Node.js application stack for APIs, workers, and custom services with a repeatable runtime setup.
Node.js services that need access to private APIs or internal systems can benefit from a reusable VPN path.
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.