Customers file a request. Agents solve it or escalate it. Engineers get a real issue with the whole conversation attached - and the customer sees the fix land. No copy-paste, no integration to maintain, no dropped context.
Hey Product Hunt ๐
I'm Giacomo, and today I'm launching Prizy: Linear + Zendesk, together in one workspace.
Most software teams run an issue tracker for engineering and a helpdesk for support, and they pay for the gap between the two. Tickets get copy-pasted into issues, nobody tells the customer when the fix ships, and every new hire needs two logins and two sets of permissions.
Prizy puts both in one app. When a customer reports a bug, the agent links the ticket to an engineering issue. Developers see it under Escalations, and the customer's portal shows that engineering is on it. There are no sync jobs and no second tool.
What's in v0.0.1:
๐ Build: issues, cycles, projects, milestones, a roadmap, releases with generated changelogs, plus GitHub and Slack integrations
๐ง Support: a shared ticket desk, SLA policies with business hours, CSAT, a public Help Center with translations, and a customer portal with magic-link sign-in
๐ Reporting on both sides, and a full workspace export
It's open source (MIT) and free to self-host. One installer script takes a fresh Debian/Ubuntu or RHEL server to a running Prizy with automatic HTTPS. It installs Docker, generates every secret, and asks only for your domain, an email for Let's Encrypt, and how to send mail.
Want to hack on it? composer dev starts the whole development environment with one command.
It's an early release, so I'd love your honest feedback:
โข What would you need before moving off Linear + Zendesk (or Jira + Intercom)?
โข What's missing on day one?
I'll be here all day answering questions ๐
๐ prizy.dev ยท ๐ docs.prizy.dev ยท โญ github.com/giacomomasseron/prizy