When we built Deno KV, a zero-config, ACID/multiple consistency supported data store, that when used with Deno Deploy becomes a globally distributed serverless database, there were growing concerns of potential vendor lock-in. These are important concerns, as Deno is intentionally built on web standards. This aligns with our philosophy: knowing Deno means knowing the web, which empowers you to reach over a billion internet users.

We're excited to share the open source, standalone Deno KV binary (MIT licensed), that you can self-host with any VPS of your choosing. This should make using Deno KV more flexible with whatever architecture you prefer.

We'd love to hear your feedback. Would you self-host Deno KV? What would you improve about the experience of using Deno KV? Any other part of your stack that gives you headaches?

Thanks!