Threaded email, attachments, delivery status, and customer export or erasure make this feel like a real small-team helpdesk, not just infrastructure glued together. What's missing on the page is the obvious part: a few screenshots of the inbox, ticket thread, and help center.
ResolveHQ
Cloudflare-native shared support inbox for small teams
5 ratings3.68
Saves71
CategoryBusiness
PlatformWeb
PricingFree
ResolveHQ is a self-hostable, Cloudflare-native helpdesk solution designed for small support teams. It provides a shared inbox with tenant-isolated customers, ticket management, assignment, status, priority, tags, and full-text search. Features include role-based workspace management, RFC 5322 compliant email threading, inbound and outbound mail handling via Cloudflare Email Routing and Resend, attachment uploads to Cloudflare R2, AI-assisted responses (opt-in), public help centers, reporting, automation rules, and data export/reset capabilities. The product runs within a single Cloudflare Worker in the user's account leveraging Cloudflare services such as D1, R2, Queues, and Email Routing.
small-teamsself-hosted
Ratings & Reviews
Write a reviewInformation
CategoryBusiness
PlatformsWeb
PricingFree
AccountNot confirmed
ListedSeptember 2026
WebVisit
Report a problem
Around the Web
Show HN71 source points · 25 comments
Just used a very similar stack to make my own mail client. Workers for routing, Resend for sending, uses a CF and Resend key to set up any inbox on any domain I want ~instantly so I can have inboxes for everything. Very cool, I think workers are underrated!
gepeake · Imported from Show HN
Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!
orliesaurus · Imported from Show HN
I get the temptation to self-host your support platform, as the existing tooling out there can be quite expensive when you want to upgrade from just using an email inbox. If any founders find themselves reading this, and don't think it's the best idea to self-host your own support infra, I've just spent the last 6+ months building stayupfront.com which has, I think, quite reasonable pricing, and a few more features than this... largely around the customer's portal experience (changelog, roadmap, etc.) and includes monitoring & incident management which I think should all be ran from the same surface. I've only just soft-launched, so still have founding pricing on there. Would certainly love to speak to others in this space too, as I was surprised how neglected an area it seemed to be when I was trying to find a replacement for jira service desk for a company I was working with at the beginning of this year.
robgough · Imported from Show HN
nice stack. one question from someone who just built one of these: how do you handle inbound email threading? in my case the provider (SES) rewrites the Message-ID in transit, so In-Reply-To/References matching silently breaks. I ended up putting the ticket id in a plus address on the Reply-To, the envelope survives even when the headers don't. also curious how you handle webhook redeliveries, for me duplicates turned out to be the normal case, not the rare one.
sfraxo · Imported from Show HN
It may be very nice, but with no screenshots and no demo site you're going to have trouble getting people to try it out.
14u2c · Imported from Show HN