CDN / Reverse Proxy Domains

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want CDN / Reverse Proxy Domains working in a real project rather than a sandbox.

   Set up CDN / Reverse Proxy Domains in this project — connect domains routed through Cloudflare, CloudFront, or Fastly. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Apps behind Cloudflare

   The record lists this as one of the jobs CDN / Reverse Proxy Domains is meant for, so it is a fair first test of whether it fits your app.

   In this project, use CDN / Reverse Proxy Domains for apps behind Cloudflare. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   CDN / Reverse Proxy Domains is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses CDN / Reverse Proxy Domains before I publish. Check CNAME-based setup and auto SSL, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Multi-region edge

   A second job the record lists for CDN / Reverse Proxy Domains, useful once the first path works.

   Extend this project so CDN / Reverse Proxy Domains also covers multi-region edge. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is CDN / Reverse Proxy Domains?

  CDN / Reverse Proxy Domains is Lovable's Publishing feature: Connect domains routed through Cloudflare, CloudFront, or Fastly. Reintroduced support for custom domains routed through your own CDN or reverse proxy, with a CNAME-based config and Lovable-handled SSL once the record is live.

• Is CDN / Reverse Proxy Domains GA or in beta?

  CDN / Reverse Proxy Domains is generally available (GA) on Lovable.

• What Lovable plan includes CDN / Reverse Proxy Domains?

  CDN / Reverse Proxy Domains is available on Lovable's Paid plans plan.

• When did CDN / Reverse Proxy Domains launch?

  CDN / Reverse Proxy Domains launched on Apr 2, 2026.

• Granular Publishing AccessSame category, also GA · Apr 2026
• Project Visibility & Public RemixingSame category, also GA · Apr 2026
• Branded app URLsSame category, also GA · May 2026