Skip to content
Layeron Doc

Cloudflare Native

Cloudflare Native lets you call underlying Cloudflare resources directly from Layeron while keeping Cloudflare-native configuration pass-through.

Use it when you want direct access to a Cloudflare product surface, including products Layeron has not wrapped yet. Layeron records the config in the app spec, resource graph, runtime topology, plan, and deployment state. Wrangler-shaped fields stay Wrangler-shaped.

During layer deploy, Layeron generates an inspectable Wrangler artifact and runs Wrangler as the Cloudflare Native execution layer:

Terminal window
.layeron/deploy/<env>/cloudflare-native/wrangler.jsonc

Layeron runs its direct Wrangler dependency for this deploy step. New Cloudflare product support becomes available when Layeron updates that dependency, while Layeron keeps the app declaration, graph visibility, generated Worker bundle, and deployment record; Wrangler owns Cloudflare product-specific deploy behavior for native config.

Cloudflare Native is best for teams that need direct Cloudflare platform capabilities or need to reference, adopt, or bind existing Cloudflare resources inside the same backend app model as first-class products.

What It Covers

Section titled “What It Covers”

Cloudflare Native can represent common Cloudflare bindings and advanced Wrangler fragments:

  • KV namespaces.
  • R2 buckets.
  • D1 databases.
  • Queue producers and consumers.
  • Durable Object bindings.
  • Workflow bindings.
  • Advanced or newly added Wrangler sections.

Layeron extracts known binding shapes for graph visibility and Worker attachment. Unknown sections are preserved so the app can still deploy with the Cloudflare configuration the user provided.

When To Use It

Section titled “When To Use It”

Use Cloudflare Native when:

  • A Cloudflare product surface has no dedicated Layeron product yet.
  • You need a Wrangler-shaped option that should stay close to Cloudflare’s native configuration.
  • Existing Cloudflare resources should be bound into a Layeron app.
  • A route or queue consumer needs direct access to native Worker binding APIs.

Use a first-class Layeron product when Layeron owns the higher-level behavior, such as Database, Secrets, Logs, Observability, Captcha, or future capability modules.

How It Fits

Section titled “How It Fits”

Cloudflare Native stays inside the platform pipeline:

Terminal window
app.cloudflare.wrangler(...)
  -> AppSpec native config
  -> RuntimeTopology bindings and entrypoints
  -> Resource graph
  -> Plan and apply
  -> generated cloudflare-native/wrangler.jsonc
  -> wrangler deploy --config <artifact>
  -> Deployment state

This keeps native escape hatches inspectable and traceable while preserving the Layeron app pipeline.

Next Steps

Section titled “Next Steps”
  • Get started: Add Wrangler fragments, runtime entrypoints, bindings, Durable Objects, Workflows, and helper calls.
  • Resource model: Understand graph extraction, deployment artifacts, vars, and secret references.
  • Backend native resources: Learn how native Cloudflare resources fit beside capability modules.