Does anyone know if LiveWhale will still function properly if we put our calendar behind Cloudflare?
Hi Brandon,
Great question – we’ve actually started implementing CloudFront (Amazon’s “built-in” CDN, essentially) to LiveWhale sites over the last couple years and it’s been working really well. Many LiveWhale sites are already using it, I expect we’ll roll it out to any remaining calendars and sites in by mid-to-late 2025. In the meantime, if you have specific performance concerns about your calendar or hosting, you can also always feel free to reach out with a hosting question using the [Request Help](Request Help - LiveWhale Support] form. Or, happy to continue the conversation here if you have general questions about how we’re using CloudFront. Thanks!
Karl
Thanks, Karl. It’s not necessarily about site performance, it’s just all our other sites are behind our enterprise Cloudflare account and our calendar is the remaining hold out. Having things behind our Cloudflare allows us to have finer grain control over things like WAF and redirects.
Would there be any technical concerns about using our Cloudflare in front of our calendar?
Thanks Brandon, that context is useful.
Chatting about this with the team, we don’t see adding your own CloudFlare as something we’d be able to support under our current license/contracts. The logistical reason being, our contracts essentially make us responsible for server uptime (with few exceptions for, you know, if you upload a custom script that breaks the site). Given that, we’re not able to let people setup their own CDNs/proxies/firewalls/etc. since then we’d be on the hook for uptime on a server architecture we don’t have full control over.
That being said, if you have particular settings from your own CDN or firewalls you’d like us to route as a suggestion to our hosting team, please let us know. Thanks!