Isn't deno running locally no your self-hosted instance? How are they charging? Enqueuing a Message: Each enqueue action translates into a KV write operation

Isn't deno running locally no your self-hosted instance? How are they charging? Enqueuing a Message: Each enqueue action translates into a KV write operation. Receiving a Message: Every received message entails a KV write, and a single request charge. I would be really curious to know. Are they only talking about Deno Deploy in the cloud, with FoundationDB? Is this "open core"?