Despia uses a limited Cloudflare API key to create Workers directly on your account instead of running its own servers. You keep the hosting responsibility and any downtime falls on Cloudflare, not Despia.
But what we don't want to do is cloud hosting. So what I'm very against is I don't want to run your infrastructure. Everything that runs in your app is offline. And if you want infrastructure, and we are now at the point where we need to add some infrastructure for some features, we're actually going to have you put in your Cloudflare API key, grant us limited access to create Cloudflare workers to do certain things on your Cloudflare instance. And then you do this under your own Cloudflare account and Despia is just a nicer interface for doing it. That's no code. So we don't have to manage hosting because then if something is down, I can always blame it on Cloudflare because it's not our fault. Where if I would be using Cloudflare on my end and something is down, it's my fault. But if we're the interface and they directly host with Cloudflare and Cloudflare is once again down because they love being down, uh, then it's Cloudflare's fault, not mine, you know? And I don't have to do support for
