Connector · Tickets & work

AI search over GitHub, on your own infrastructure.

Ask questions across your GitHub content and get cited answers, with access limited to what each person can already open. The connector runs inside your environment and keeps content in sync.

Category
Tickets & work
Runs in
Your infrastructure
Permissions
Carried from GitHub
Sync
Continuous, no manual uploads

In short

The DeepVox GitHub connector reads the GitHub content you choose, inside your own infrastructure, and carries its permissions across. People ask in chat, voice or other tools and get answers that cite the GitHub source, limited to content they are already allowed to see.

What it does

Connected, governed, cited.

Permissions carried across

Answers only draw on content the person can already open in GitHub.

Continuous sync

New and changed content is picked up without manual uploads.

Runs in your environment

Content is never copied to a third-party AI service.

Cited answers

Every answer links to the GitHub item it came from.

Typical content

What we usually index from GitHub.

Scope is agreed in discovery: which spaces, folders, projects or tables to include.

  • Repositories and READMEs
  • Issues and pull requests
  • Wikis

What people ask

Example questions.

  • “Where is retry logic implemented?”
  • “Why did we change the auth library?”
  • “Summarise open pull requests for the API.”

Works alongside

Often connected together.

FAQ

Questions, answered.

Does the GitHub connector copy our data to a vendor?

No. The connector, index and models run in your own infrastructure.

Are GitHub permission changes reflected?

Yes. Permissions are kept in sync with GitHub, so access changes there are reflected in answers.

Can you connect a system that isn’t listed?

Yes. Anything with an API, a database or an export can be connected; we build the connector during customization and the code is yours.