Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues

28 pointsposted 4 hours ago
by mirza_rizvi

10 Comments

orliesaurus

3 hours ago

Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!

aetherspawn

2 hours ago

Yeah GitHub repos need screenshots.

ttul

2 hours ago

Just have Codex or whatever take the screenshots and post them to the repo. Easy peasy.

brazukadev

an hour ago

it is more efficient to prompt the meat proxy

robgough

2 hours ago

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.

gepeake

3 hours ago

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!

aetherspawn

2 hours ago

You don’t need resend anymore, email is CF native.

14u2c

2 hours ago

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.

roflchoppa

2 hours ago

Can it kill Jira? That’s all I ask :(