Everything RepoHelpdesk does.
Answers for your team, docs and a chatbot for your clients, and answers about the actual customer — all from your code, without handing it out.
Works where your team already is — and where your customers are.
Nobody opens another tool. Ask from the apps your team lives in, from inside your own product, or let customers help themselves.
For your team
For your customers
Ask from inside your own app.
Put RepoHelpdesk on the pages your team already works in. When something goes wrong, they ask right there — and it sees what they see.
One line, or nothing to install
Add a script tag to your app, or use the Chrome extension on any site you allow.
It sees the errors on the page
The page's console and network calls are recorded from the moment it loads, and handed to the AI.
It can look at the page
With the Chrome extension, the AI can take a screenshot when seeing the page helps.
Only where you allow it
It appears only on the sites your project lists.
Why did my save just fail?
The save was turned down because someone else changed this customer a moment ago. Refresh to load their version, then make your change again.
Docs that write themselves — and stay accurate.
RepoHelpdesk writes your customer docs from your code and updates them every time it changes. Customers read them, search them, or just ask the chat bot.
How can we help?
- Export a report to Excel Updated 2 days ago
- Set up single sign-on (SAML) Updated last week
- Why a scheduled report didn't send Updated 3 weeks ago
Can I export more than 10,000 rows?
Yes — an export can hold up to 50,000 rows. For more, split the report by date range.
From: Export a report to ExcelWritten from your code, kept current
Articles come from what your software actually does. When the code changes, they are updated — you choose how much to review before anything goes live.
Your look, your address
It picks up your logo and colors from your website, and can live at docs.yourcompany.com.
A chat bot for your customers
Add it to your site with one line. It answers from your published articles only — and the questions it can't answer show you what to write next.
Ready for AI assistants
Your docs come with llms.txt, Markdown copies and an MCP server, so your customers' AI tools can read them too.
Answers about this customer, not just how the code works.
Ask about a real customer and get an answer that fits their situation — not a general description of how the software behaves.
Priya · Support Why didn't Dana Lopez get her password reset email?
Reset emails are retried three times, then dropped. Ask the customer to check their spam folder and try again.
Dana asked for a reset at 9:42 this morning, and all three tries bounced. The email on her account is dana.lopez@acme.con — a typo for .com. Fix it on her account, then send the reset again.
About the customer in front of you
Their account, their history, what actually happened — not a general explanation.
Works with what you already use
Databases, logs, Stripe, Zendesk, Jira and more.
Safe by default
It only reads your data. Nothing is ever changed without a person saying yes.
Faster every time
Once it has answered a kind of question, the next one like it comes back straight away.
Every answer makes the next one faster — and cheaper.
A general AI tool starts every chat from zero, for every person, at full price. RepoHelpdesk learns your software once and shares what it works out with the whole team.
It keeps a map of your software
When you connect a repo it works out how your software fits together — features, rules, data — and keeps that current as the code changes. Each answer starts from the map, not from a blank page.
It learns from every conversation
Something explained once is known next time — for the whole team, not just the person who asked.
Less reading, less AI spend
Because it already knows where to look, it reads less of your code for each answer. Fewer tokens, lower bill.
Repeats cost nothing to work out
Once it knows how to answer a kind of question, the next one like it comes back at once — no paying the AI to figure it out again.
Our own models, at a fraction of the price
Three RepoHelpdesk models — Spark, Forge and Summit, from quick to deep — are the default. Claude is there when you want it.
- Plans and limits
- Invoices
- Refunds
- Roles
- Single sign-on
- Invites
- Scheduling
- Export to Excel
Your code is secure.
We never see your code. A small program — the Agent — reads it on a server you control, and the answer comes back to your team. The code itself stays put.
- ✓ The Agent runs on a server you control and reads your code right there.
- ✓ When the AI needs a few lines of code, the Agent sends them straight to the AI model — never through our servers.
- ✓ We keep only who asked, when, and how much AI it used. Never your code, never the chat itself.
- ✓ Passwords and keys found in your code are never shown in an answer.
- ✓ Need our help? Share one chat, read-only, for 1, 3 or 7 days — every view is logged.
Our cloud
Your network
Answers that know who's asking.
Your software already decides who can see what. RepoHelpdesk follows the same rules, so each person only hears about what they're allowed to use.
Yes. Open Admin → Accounts → Billing and change the renewal date. The next invoice is adjusted for the difference.
Billing dates are changed by the Billing team. Pass the request on with the customer's account number.
It reads the rules from your code
Who signs in where, the roles and permissions your code checks, and which plan unlocks what. The AI works it out — nobody writes it down.
You check it once
An admin reviews who can see what, fixes anything that is off, and tests it on a real person before switching it on.
It looks each person up
When someone signs in, RepoHelpdesk checks their role in your own system — so answers match what they can do today.
Customers too
Publish separate docs for each kind of customer. Each set only covers what those customers can use.
Setup in 60 seconds — two ways to get started. Both fast.
On your server
Run a single command with your project's pairing token. Done. Now anyone on your team can ask, from any browser.
On a server we run for you
- 1Sign up and choose We host it.
- 2Connect GitHub, GitLab, Bitbucket or Azure DevOps.
- 3Start asking questions.
Nothing to install. A dedicated server for your project, on any plan.
Connect a repo. Ask a question.
See what we mean.
Free trial. No card needed.