zlacker

They do have the CDN proxy too. Not sure when it was implemented though.

It's a similar process to Cloudflare. Point the NS to them and enable the proxy for a domain or subdomain.

>>pier25+(OP)
You can also create a standalone pull zone and point your existing DNS provider to the CNAME they give you.

(don't use CNAME flattening with DNS-routed CDNs like Bunny though, if you must use an apex domain then use the CDNs integrated nameservers)

>>pier25+(OP)
When I tried it last year, their edge compute infra was just not there yet. It could not do any meaningful server-side rendering because of code size, compute and JS standard constraints.

Has this situation changed?

>>osener+k4
Not sure what you mean with ssr for a CDN?

>>pier25+ra
Edge computing. Cloudflare workers for example.

Bunny has a similarity concept: https://bunny.net/edge-scripting/

>>jshear+v1
> don't use CNAME flattening with DNS-routed CDNs like Bunny though

What is the problem with doing that?

>>osener+k4
I haven’t tried to do SSR in bunny but they also have bunny magic containers now where you run an entire container instead of just edge scripts (but still at the edge).

>>osener+k4
Depending on your precise requirements, I think it might have changed.

I've been trying out Bunny recently and it looks like a very viable replacement for most things I currently do with Cloudflare. This new database fills one of the major gaps.

Their edge scripting is based on Deno, and I think is pretty comparable to e.g. Vercel. They also have "magic containers", comparable to AWS ECS but (I think) much more convenient. It sounds from the docs like they run containers close to the edge, but I don't know if it's comparable to e.g. Lambda@Edge.