Migrate all databases to Cloudflare databases

[lucis]

Our current .dev.vars file looks like this.

SUPABASE_URL=
SUPABASE_SERVER_TOKEN=
TURSO_ORGANIZATION=
TURSO_GROUP_DATABASE_TOKEN=
CF_ACCOUNT_ID=
CF_API_TOKEN=
CF_DISPATCH_NAMESPACE=
CF_R2_ACCESS_KEY_ID=
CF_R2_SECRET_ACCESS_KEY=
RESEND_API_KEY=
TURSO_ADMIN_TOKEN=
OPENROUTER_API_KEY=
WALLET_API_KEY=
OTEL_EXPORTER_OTLP_ENDPOINT=
OTEL_EXPORTER_OTLP_HEADERS=
OPENAI_API_KEY=
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_REGION=
LLMS_ENCRYPTION_KEY=

It makes hard to deploy a self-hosted version of deco.chat.

It has more points of failures than it would need to...

We recently implemented:

• Workers, leveraging Workers for Platforms.
• A File System MCP on top of R2
• Agents running on Durable Objects

So, it would make sense we have all the right incentives to leverage Cloudflare DB capabilities, simplifying the architecture.

It has:

• D1, a SQLite database.
• Vectorize, a vector database ready for LLM applications.

The solution is probably something similar to what we've done with R2. We manage the service with multitenancy linking Cloudflare resources to workspaces.

Users willing to self-host on their own Cloudflare can just use their CF tokens.

This would require:

• Migrating off Supabase and Turso.
• Managing the hosted D1 databases.

Resend, Wallet, OpenAI should all become MCP Servers where we configure them with our tokens and offer (and use) at a price.