Cloudflare O2O
O2O is not specific to Clonable and is not required by default to place Cloudflare in front of your clone. For that, follow the Cloudflare guide.
Clonable does not use Cloudflare in front of its own servers. O2O is therefore only relevant to the connection with your original provider's Cloudflare integration.
When do you need O2O?
Does your original hosting provider already have a managed Cloudflare integration where you cannot configure your own rules, as with Shopify or Kinsta? If you want to place your own Cloudflare in front of it, for example for subfolder routing to Clonable, you need O2O to connect your Cloudflare zone to your provider's zone.
How does it work?
Visitor → your Cloudflare zone → provider's Cloudflare zone → original website
This is the route to your original website; a Worker can route the clone's subfolder to Clonable. O2O uses Cloudflare for SaaS with a proxied CNAME pointing to your provider. Follow the requirements and instructions for your provider: