[bcye]

Very nice and a great service. I wish there API Keys were scoped however so setting up continuous deployments doesn't risk your, say, MX records getting changed if the key is leaked. And it would be very awesome if they would support IPv6-only origins for the CDN.

[joe-at-bunny]

Hey! Thanks for the feedback.

We're doing discovery on API key scopes at the moment, we don't yet have a public ETA for this but rest assured it's being worked on!

Regarding IPv6-only origin support, We brought this in just last week! We now support IPv6-only addresses direct as an origin, as a hostname, as well as dual stack hostname resolution.

Best, Joe

[xyzzy_plugh]

Hey Joe, just to pile on...

If you had have supported API key scoping then I'd have a ton of businesses/startups running on you. As it stands currently it's difficult for me to recommend you to orgs that are scaling up. Compliance in particular was the biggest issue. For one-man shops it's a no-brainer.

In your defense, Cloudflare has historically also sucked in this area.

Anyways, I'm looking forward to this feature!

[is_true]

Hello Joe.

How does the USD1 minimum works? Say I have setup a pull zone and i don't use it for over a month, I get charged anyway?

Thanks.

[tpetry]

Yes. You‘re getting charged. But a dollar for your entire bunny account (not for every service or domain) is not that much to ask for.

[tpetry]

I wish for the sme. Right now I‘ve created specialized edge functions to e.g. make a deployment which has the global access key.

So, my scripts on my servers dont have the bunny api key. Its only saved within those edge functions and I authenticate against the edge functions.

A little bit more effort than scoped keys but it works