6 comments

  • 14u2c 0 minutes 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.
  • robgough 25 minutes 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.

  • orliesaurus 40 minutes ago
    Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!
    • aetherspawn 32 minutes ago
      Yeah GitHub repos need screenshots.
  • gepeake 1 hour 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 31 minutes ago
      You don’t need resend anymore, email is CF native.
  • roflchoppa 34 minutes ago
    Can it kill Jira? That’s all I ask :(
  • sfraxo 12 minutes ago
    [dead]