Integration

Cloudflare Application Access on Wodby

Use Cloudflare API credentials in application code, protect public forms with Turnstile, or place Wodby endpoints behind Cloudflare Access or enrolled Cloudflare One devices. Each selected kind exposes only its own credentials and configuration.

VariablesVariablesApplication Access

Connect application code to Cloudflare APIs

Inject an Account ID and scoped API token only into services that explicitly request the Cloudflare API kind.

Protect browser access with identity

Publish customer-zone hostnames through Cloudflare Tunnel and place a reusable Cloudflare Access policy in front of the app.

Keep apps inside a private device network

Route enrolled Cloudflare One devices to private Wodby endpoints without leaving matching ordinary public routes exposed.

Supported workflows

How Cloudflare fits into Wodby

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

Variables

API

Inject Cloudflare settings into services as environment variables instead of hardcoding them into app code.

  • Keep provider keys, tokens, and DSNs outside repositories and local dotenv files.
  • Attach the integration to reusable stacks, then connect it to the services that actually need it.
  • Override values per environment without rebuilding the stack.

Configuration surfaced to workloads

CLOUDFLARE_ACCOUNT_IDCLOUDFLARE_API_TOKEN
See integration workflows

Variables

Turnstile

Inject Cloudflare settings into services as environment variables instead of hardcoding them into app code.

  • Keep provider keys, tokens, and DSNs outside repositories and local dotenv files.
  • Attach the integration to reusable stacks, then connect it to the services that actually need it.
  • Override values per environment without rebuilding the stack.

Configuration surfaced to workloads

TURNSTILE_SITE_KEYTURNSTILE_SECRET_KEY
See integration workflows

Application Access

Application Access

Publish Wodby apps behind Cloudflare Access or route private endpoints to enrolled Cloudflare One devices.

  • Choose protected publishing with an identity policy or private-network access for enrolled Cloudflare One devices.
  • Protect every eligible HTTP endpoint or select only the services that should move behind Cloudflare.
  • Wodby manages the Tunnel connection, provider routes, matching public-route suppression, reconciliation, and cleanup.

Configuration surfaced to workloads

Account IDAPI Token
Explore Application Access

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 Cloudflare.

See integration workflows

Store provider keys, tokens, and DSNs once, then reuse them across environments.

View page

Explore Application Access

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

View page

Browse all integrations

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

View page

Stack fit

Stacks that commonly pair with Cloudflare

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

  • Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.

    Drupal can run as an internal CMS, intranet, or protected editorial environment behind Cloudflare.

    View stack

  • WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.

    WordPress can serve private portals and protected preview environments through the same app-level access model.

    View stack

  • Private OpenClaw gateway stack for always-on agent workflows with integrations such as Tailscale.

    OpenClaw gateways can stay off ordinary public routes while approved users connect through Cloudflare One.

    View stack

  • Next.js

    Stack

    Next.js application stack for frontend and full-stack projects that need a reusable deployment setup.

    Next.js is a strong fit for internal dashboards, admin applications, and customer portals protected by Cloudflare.

    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.

Browse all integrationsApplication Access overview