Run Xodia previews on your own Cloudflare
Previews run on Xodia's own runtime by default. With Pro and Agency, Xodia can install that runtime in your Cloudflare account instead. Xodia then doesn't count preview hours, and Cloudflare bills you directly for what the runtime uses.
Free plan. 14-day Pro trial. No charge unless you choose a plan.
Xodia's Previews page with Your own Cloudflare in use: the Rise Bakery Cloudflare account connected, Workers Paid active and the Xodia runtime running in that account.
How it works
Xodia's runtime by default, yours when you want it
Every workspace starts on Xodia's runtime, with nothing to set up. In your workspace's Previews page you can switch to your own Cloudflare account, and the same runtime runs there.
- The editor, your AI and your saves work the same on either runtime
- New projects and projects from GitHub follow the workspace's choice
- Projects started from a template stay where their code is: ones you already have keep running on Xodia
Xodia's Previews page in a workspace's sidebar: Run by Xodia is in use, with nothing to set up, and Your own Cloudflare offers Connect Cloudflare, with no preview hour cap and Cloudflare billing you directly.
Hosted or your own
What changes when previews run in your account
Where previews run
Run by XodiaXodia's Cloudflare account
Your own CloudflareYour Cloudflare account, on a Worker Xodia installs there
Preview hours
Run by XodiaYour plan's hours each month (3 on Free, 25 on Starter, 80 on Pro, 200 on Agency)
Your own CloudflareNot counted
Previews at once
Run by XodiaYour plan's limit
Your own CloudflareNot limited by your plan
Template projects' code
Run by XodiaXodia's code storage
Your own CloudflareCode storage in your Cloudflare account
Updates
Run by XodiaAlways the latest runtime
Your own CloudflareYou press Update when a new version is out
Who bills it
Run by XodiaIncluded in your Xodia plan
Your own CloudflareCloudflare, on your Workers Paid plan
Plans
Run by XodiaEvery plan
Your own CloudflarePro and Agency
What's installed
What Xodia installs in your account
One Worker named xodia-runtime and what it needs to run previews. It's the same runtime Xodia runs for everyone else, at the version Xodia ships.
The runtime Worker
The xodia-runtime Worker on your workers.dev address. It answers only requests that Xodia signs for your install.
Durable Objects
One per project, with its own storage, to start, stop and look after that project's preview sandbox.
Containers
The preview sandboxes, from an image Xodia copies into your account's container registry. Each one stops 15 minutes after its last request.
Code storage
A git repository in Cloudflare Artifacts for each project you start from a template. Projects from GitHub stay in GitHub.
Browser Rendering
Used for the screenshots your AI takes of a preview to check its work.
A workers.dev subdomain
If your account doesn't have one yet, Xodia registers one for it, so the runtime has an address.
Hours and billing
No preview hour limits. Cloudflare bills you directly.
Xodia doesn't track preview time
Xodia counts preview hours only for previews on its own runtime. For projects on your Cloudflare it records no preview time, and they don't count toward your plan's limit on previews at once.
Your plan's projects and seats still apply.
Cloudflare charges your account
Your account needs Cloudflare's Workers Paid plan. Cloudflare bills the runtime's Workers, Durable Objects, Containers and other usage to you at its own rates. Xodia doesn't add a charge for it. See Cloudflare's pricing
Setup
Pro and upSet it up in a few minutes
Everything happens on your workspace's Previews page. Admins and owners can do it by default; the Manage connections permission decides.
- 1Connect Cloudflare. Sign in to Cloudflare and approve Xodia's access. You pick the account on Cloudflare's own consent screen.
- 2Check your plan. Xodia checks that the account has Workers Paid, and links to Cloudflare's plans page if it doesn't.
- 3Install. Xodia checks your plan again, prepares workers.dev, copies the preview image, deploys and pairs the runtime, and checks it responds.
- 4Edit as usual. New projects and projects from GitHub preview in your account from then on.
The Xodia runtime installing in a connected Cloudflare account: checking your plan and preparing workers.dev are done, copying the preview image is running, then deploying and pairing the runtime and checking it responds.
What Xodia asks for
Only what the runtime needs, and updates when you choose
The Cloudflare connection asks for the least access the runtime needs. When Xodia ships a new runtime version, your Previews page shows it with an Update button.
- Read your account settings
- Upload and manage Workers, Containers and Artifacts code storage
- Use Browser Rendering for screenshots
- Stay connected, so Xodia can update the runtime without asking you to sign in again
- Update runs the same install steps; your running version keeps working while the new one installs
Your Cloudflare setup in Xodia: Workers Paid is active, and the Xodia runtime card says version 1.0.57 is running and 1.0.58 is available, with an Update button.
Security
Your previews and template code stay in your account
The sandboxes and the code of template projects live in your Cloudflare account, and Xodia reaches them only through the runtime it paired with.
OAuth, encrypted
Connecting uses Cloudflare's OAuth sign-in. Xodia stores the access encrypted at rest with AES-256-GCM and refreshes it itself; it never reaches your browser or your AI.
Signed requests only
Each install gets its own secret. The runtime refuses any request that isn't signed with it, is stale or was changed on the way.
The same sandbox rules
Previews in your account keep the allow-list network of every Xodia preview. How previews are protected
A short-lived installer
Installs and updates run in an installer container that gets your Cloudflare access for each command and doesn't write it to its disk.
Disconnect any time
Your runtime and sites stay in your account. Xodia can't install or update anything there until you connect again.
Switch back any time
Switch to Xodia previews from the same page. Nothing is deleted, and installing your runtime again switches you back.
Questions
Own Cloudflare questions
Which plans can run previews on their own Cloudflare?
Pro and Agency, including the Pro trial. Previews on Xodia's runtime work on every plan.
Do I need a paid Cloudflare plan?
Yes. Previews need Cloudflare's Workers Paid plan on the account you connect. Xodia checks for it before it installs and tells you if it's missing. Cloudflare's pricing lists what it charges.
Do previews on my Cloudflare use preview hours?
No. Xodia counts preview hours only for previews on its own runtime, so projects on your Cloudflare don't use them and are never stopped for running out.
Can I move back to Xodia's runtime?
Yes. Choose Switch to Xodia previews on the Previews page. New projects and projects from GitHub move to Xodia's previews. Projects started from a template keep running in your account, where their files are, as long as the runtime stays installed and your plan includes it. Nothing is deleted.
What happens if my plan stops including it?
Previews on your Cloudflare keep working for 7 days after your plan stops including them, for example when a trial ends or you move to Free or Starter. Xodia shows the date in the app and emails the workspace owners when the 7 days start and the day before they end.
After that, projects from GitHub and new projects move to Xodia's previews, within your plan's preview hours. Projects started from a template stay in your account and are paused until you upgrade. Nothing is deleted, and upgrading turns everything back on right away.
How do runtime updates work?
Xodia's own runtime is always on the latest version. On your Cloudflare, the Previews page shows when a newer version is out, and Update installs it with the same steps as the first install.
Who in my team can set it up?
Whoever may manage connections: admins and owners by default. With team roles, the owner can change that in roles and permissions.
Keep exploring
Related pages
- Visual editorCanvas, Style panel, Navigator and Variables
- Bring your AIClaude, Cursor and any MCP app, with Xodia's tools and skills
- CMSContent files, collections and Sanity
- Git and publishingDrafts, restore points, branches and publish
- SEOPage settings, audits and speed tests
- Product overviewEvery feature in the order you use it
- PricingPlans, limits and the free trial
- FrameworksWhat you can edit on each stack