EDGE Signal 143
Open-source helpdesk ResolveHQ runs entirely on Cloudflare Workers, D1, R2 and Queues
ResolveHQ is a self-hostable helpdesk built on Cloudflare’s edge platform, storing data and processing mail in the user’s own account.
Engineers can now deploy a full-featured helpdesk without managing servers or databases. The architecture demonstrates how Cloudflare’s edge primitives can replace traditional back-end infrastructure. Cost and scalability depend entirely on Cloudflare’s pricing tiers and limits.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
ResolveHQ stores tickets in Cloudflare D1, attachments in R2, and mail jobs in Queues, all under the user’s Cloudflare account.
The entire application runs as a single Cloudflare Worker, with optional AI drafting via OpenAI and outbound mail via Resend.
Deployment is a one-click ‘Deploy to Cloudflare’ flow, with free-tier operation possible for small teams within Cloudflare’s limits.
THE READ
What the cluster adds up to.
ResolveHQ is a helpdesk application that runs entirely on Cloudflare’s edge platform. It uses Cloudflare Workers for compute, D1 for relational data, R2 for object storage, and Queues for mail processing. All data and processing occur within the user’s own Cloudflare account, eliminating the need for separate database or storage services. This architecture shifts operational responsibility to Cloudflare, reducing the infrastructure engineers must manage directly.
The application is self-hostable and designed for small support teams. It includes features such as tenant isolation, ticket assignment, status tracking, full-text search, and email threading compliant with RFC 5322. Attachments are stored in R2, and mail is routed through Cloudflare Email Routing and sent via Resend. Engineers can deploy it with a single click using the ‘Deploy to Cloudflare’ button, provided they have a Cloudflare account, a domain, and optionally a Resend account for outbound mail.
ResolveHQ can operate on Cloudflare’s Free plan for small deployments, but usage must stay within the limits of Workers, D1, R2, Queues, and Email Routing. CPU-intensive tasks like authentication or mail parsing may require a paid Workers plan. R2 and Resend have separate billing and limits. The application includes a retention setting to automatically delete resolved and closed tickets after a configurable period, reducing storage costs and compliance overhead.
The deployment model is designed for simplicity but requires familiarity with Cloudflare’s ecosystem. Engineers must set up Email Routing rules in the Cloudflare dashboard and may need to configure Worker secrets for AI features or retention policies. Local development is supported via Wrangler and Vite, allowing engineers to test changes before deploying to Cloudflare. The application is open-source, enabling customization but also requiring engineers to maintain their own deployments.
While ResolveHQ demonstrates the viability of edge-native applications, it has limitations. Multi-language support and email notifications outside the app are not yet implemented. The reliance on Cloudflare’s platform means that scalability and cost are tied to Cloudflare’s pricing and service limits. Engineers adopting ResolveHQ must monitor their usage to avoid unexpected charges or service interruptions, particularly if their support volume grows.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER