About - OctoDesk

What we believe in

GitHub is the system of record

Your conversations live in your repository, not in our database. An OctoDesk issue makes sense even to someone who has never heard of OctoDesk.

Internal by default

Nothing you write reaches a customer unless you explicitly release it. When in doubt, OctoDesk does not send.

No new concepts

Status is open or closed. Priorities are labels. Ownership is an assignee. Automation is GitHub Actions. You know all of it already.

Nothing to install

Every integration works from a static HTML page. You never have to run our code on your servers.

Setup without a meeting

Every step is self-service and reversible, with sensible defaults. Minutes, not days.

Priced per project

Everybody with access to the repository can help your customers. We will never charge you per person.

Why we built OctoDesk

Small software teams run their whole company on GitHub, except for the part where customers talk to them. That part happens in a shared mailbox, where requests get forgotten, or in a helpdesk product, which is one more system to learn, to keep in sync, and to pay for by the seat.

GitHub issues already offer nearly everything a helpdesk needs: assignees, labels, mentions, notifications, search, automation, and a mobile app. The only thing missing is a bridge to the people outside of GitHub. OctoDesk is that bridge, and deliberately nothing more.

Who OctoDesk is for

OctoDesk is made for teams that already live in GitHub: small software companies and indie developers running SaaS products, apps, and developer tools; agencies looking after several client projects, each in its own repository; and open-source maintainers who want a private support or security contact next to their public issue tracker.

If your support is handled by a large team of dedicated agents who have never seen a pull request, a classic helpdesk will serve you better, and we will be the first to tell you so.

About OctoDesk