Integration

Tailscale Application Access on Wodby

Use Tailscale Application Access to give complete Wodby apps or selected HTTP endpoints stable private addresses inside a tailnet. When the Tailscale node itself is the workload, use the separate Tailscale Node integration with the dedicated or a custom stack.

Application AccessNetworking service

Give apps private tailnet addresses

Keep selected HTTP endpoints reachable only to users and devices authorized by the connected tailnet.

Keep access app-level

Protect the complete app or selected endpoints without adding a Tailscale service to every application stack.

Deploy a node only when you need one

Use the separate Tailscale Node integration when networking itself is part of the stack workload you want to operate.

Supported workflows

How Tailscale fits into Wodby

Application Access connects Tailscale to the app itself. Other supported integration kinds remain separate workflows for provider variables or network services where available.

Application Access

Application Access

Give complete Wodby apps or selected HTTP endpoints stable private addresses inside a tailnet.

  • Give authorized tailnet users and devices stable private HTTPS addresses for app endpoints.
  • Protect the entire app or select only an admin, preview, dashboard, or other sensitive HTTP endpoint.
  • Wodby manages endpoint devices, connector resources, public-route suppression, reconciliation, and cleanup.

Networking service

Tailscale Node

Deploy a Tailscale Node service when the network node itself is part of the stack workload.

  • Deploy the private-network node as a service in a dedicated or custom stack.
  • Use it when networking itself is part of the workload rather than only an app access path.
  • Choose Application Access instead when the goal is to protect HTTP endpoints for an existing app stack.

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.

Explore Application Access

Compare public delivery, identity-protected publishing, and private-network access for Wodby apps.

See service integration workflows

Deploy a private-network node as a service when networking itself is part of the stack workload.

Browse all integrations

Compare this provider with the rest of the integration catalog and other supported workflows.

Stack fit

Stacks that commonly pair with Tailscale

Application Access is selected for an app rather than built into its stack. These web stacks are common fits for Tailscale when the complete app or selected HTTP endpoints should be protected.

  • 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 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 stack
  • Node.js

    Stack

    Node.js application stack for APIs, workers, and custom services with a repeatable runtime setup.

    Node.js dashboards and internal APIs can keep selected web endpoints reachable only inside the tailnet.

    View stack
  • Python

    Stack

    Python application stack for custom web apps, APIs, workers, and automation services.

    Python dashboards and automation services can expose operator-facing HTTP endpoints without ordinary public routes.

    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.