LANEXIO Get early access

Cloudflare

Lanexio LANEXIO

Cloudflare-first
for Astro teams.

Lanexio gives Astro teams a Cloudflare-first path for deployment, storage, routing, and operations. Start fast on Cloudflare, keep the application layer portable, and move later only if you want to.

$ npx lanexio create my-site --template saas --hosting cloudflare

One command to scaffold an Astro project with the Cloudflare path preselected, then grow into a managed on-ramp if you want less setup work.

Get product updates, Cloudflare notes, and hosted-onboarding announcements.

The full Cloudflare stack. Wired in.

Workers — serverless at the edge

Run Lanexio server functions on Workers close to the request path. It is a strong fit for low-latency rendering without a traditional Node.js server.

Learn more

Pages — static and hybrid delivery

Deploy Astro-driven static sites and pair them with Functions when a page needs server logic.

Learn more

D1 — SQLite at global scale

Use D1 when you want a serverless SQL layer that fits Cloudflare-native deployments and a simple operational model.

Learn more

KV — global key-value store

Store session hints, feature flags, and lightweight cached state close to the edge with a key-value model.

Learn more

R2 — object storage, no egress fees

Store media and file assets in S3-compatible object storage with no egress fees to the Internet.

Learn more

Connect — hybrid worker setup

The @lanexio/cf-connect package generates the hybrid worker manifest, route patterns, and wrangler template for Cloudflare-first Lanexio projects.

Access — perimeter auth and admin protection

Use Cloudflare Access patterns to protect admin, preview, and internal routes without bolting a separate perimeter onto the stack later.

Images — media that stays on-network

Pair R2 storage with Cloudflare image delivery patterns so media, assets, and generated files stay close to the request path.

Hosted on-ramp — fastest way to start

Lanexio is being built with a Cloudflare-hosted onboarding path for new users who want the quickest route from signup to live project.

The edge advantage.

330+ Cities on Cloudflare's network
125+ Countries served
5 Core Cloudflare surfaces covered
1 Adapter entry point
12 Cloudflare-aligned packages on this page
84 Starter templates that can take the Cloudflare path

Cloudflare adapters included with Lanexio.

@lanexio/cf-connect

Hybrid hosting worker templates and deployment helpers

@lanexio/cf-d1

Cloudflare D1 database patterns

@lanexio/cf-kv

Cloudflare KV patterns

@lanexio/cf-r2

Cloudflare R2 and Images patterns

@lanexio/cf-workers

Cloudflare Workers runtime patterns

@lanexio/auth-cf-access

Cloudflare Access authentication adapter

@lanexio/analytics

Privacy-first analytics and exports

@lanexio/ai-engine

AI content voice, humanization, and generation

@lanexio/email

Email capture, newsletters, and drip automation

@lanexio/notifications

Notification center and delivery queues

@lanexio/backup

Hosting-aware snapshots and restore workflows

@lanexio/domain

Domain and email diagnostics and monitoring

How it connects

Cloudflare first. Not Cloudflare only.

The Cloudflare path is optimized so new users can move faster, but the application layer still runs through the hosting abstraction. That is what makes a future move possible without rebuilding the site.

lanexio.config.ts

import { defineConfig } from '@lanexio/core';

export default defineConfig({
  hosting: '@lanexio/hosting',
  adapters: {
    cloudflare: '@lanexio/cf-connect',   // binds D1, KV, R2, Workers
    auth:       '@lanexio/auth-cf-access', // Zero Trust auth
    database:   '@lanexio/db-d1',         // SQLite via D1
    cache:      '@lanexio/cf-kv',         // KV for sessions + flagging
    storage:    '@lanexio/cf-r2',         // R2 for images + files
  }
});
Portability

Cloudflare is optimized. Not required.

Lanexio is opinionated about the fastest starting path, not about permanent lock-in. Switch providers later and keep the same components, blocks, and application structure.

lanexio.config.ts → hosting target: vercel

The hosting abstraction keeps the application layer stable while the deployment target changes.

Vercel

lanexio.config.ts → hosting target: netlify

Keep the same components and blocks, then switch the deployment target for Netlify-backed builds.

Netlify

lanexio.config.ts → hosting target: node

Self-host on any VPS or platform that can run the Lanexio hosting layer with Node.

Node.js

lanexio.config.ts → node target in a container

Package the Node hosting target in Docker and deploy anywhere containers are supported.

Docker

Zero-server export

Run pnpm build with no hosting adapter and get a fully static site. CDN-perfect.

Static

Cloudflare questions, answered.

Do I need a paid Cloudflare plan?

Not necessarily. Cloudflare offers both free and paid usage tiers across these products. Which plan you need depends on traffic, build volume, storage, and how much server-side work your project performs.

How does Lanexio connect to Cloudflare services?

Use @lanexio/cf-connect for the hybrid Cloudflare setup and pair it with focused packages like @lanexio/cf-d1, @lanexio/cf-kv, and @lanexio/cf-r2. The CLI can scaffold the Cloudflare worker template and wrangler file when you choose the Cloudflare flow.

What happens if I want to move away from Cloudflare later?

Nothing breaks. Every server-side operation in Lanexio goes through the hosting abstraction layer. Swap the adapter, update lanexio.config.ts, redeploy. Data migration is outside Lanexio's scope, but the application layer is fully portable.

Can I use Cloudflare D1 as my main database?

Yes, for the right workload. Lanexio ships D1-focused helpers in @lanexio/cf-d1 and a database bridge in @lanexio/db-d1. Whether it should be your primary database depends on your write profile, migration workflow, and operational needs.

Can Lanexio AI features run on Cloudflare-backed deployments?

Yes. Lanexio's AI layer is provider-adapter based. The current source ships provider adapters for Anthropic, Google, Ollama, and OpenAI, and those can run from Cloudflare-backed applications through standard fetch-based requests.

Will Lanexio offer a hosted Cloudflare deployment path?

Yes. Lanexio is being built with a Cloudflare-hosted deployment path for new users who want the fastest start. That hosted on-ramp is meant to reduce setup friction while keeping the underlying application layer portable.

Is R2 better than an S3-compatible CDN for images?

R2 is a strong fit when you want S3-compatible object storage on Cloudflare's network and no egress fees to the Internet. Whether it is better depends on your storage workflow, image pipeline, and the rest of your infrastructure.

Get early access

Deploy to the edge.
From day one.

Join the waitlist for product updates, Cloudflare deployment notes, and hosted-onboarding announcements.

Built for Cloudflare Vercel Netlify Node.js the edge any host

No spam. No nonsense. Just Lanexio.

Back to top