Scitor

About the startup

If you're building a dev tool on GitHub, why manage support in a separate SaaS with its own logins, its own database, and no connection to your code? Scitor turns inbound emails into GitHub Issues. You reply by commenting, type /send, and the reply goes back to the customer as a normal email. Your entire support queue lives in the same UI you already use for everything else. No new infrastructure. The knowledge base is a docs/ folder in your repo. The chatbot on your site reads from those same markdown files. Config lives in .github/scitor.yaml — reviewed in PRs, rolled back with git. Extras you'll actually use: AI triage on every inbound (summary, category, sentiment before you open it), /block-sender for spam, CSAT built in, and GitHub Workflow triggers on new Issues so you can automate whatever you want.