I would say it's more cloud native than cloud restricted. In the past we used to try to bring things from outside of the cloud into to the cloud, now we're starting to bring things born in the cloud out of the cloud.

Ironically, the spec under the CloudEvents standard is much less restricted to cloud-based objects than its early working version "open events"

We considered a number of cases where the event source is not addressable software. Heck, your local library can emit a feed of cloud events where the event source is an isbn Uri.

Nothing restricts it's usage, it's just that in the naming conversation, with the other names already taken, what domains were available, etc, it was the best option.

I certainly couldn't come up with anything else, and it seemed like the best name from the group.