By industry
Customer stories
See how our clients are using Zipchat and the awesome benefits it's bringing to their businesses!
What this does: Zipchat indexes a snapshot of your GitHub repository at connection time. Your AI gets read access to source code, pull request descriptions, issue text, and inline documentation. Every question about your codebase gets a specific answer drawn from your actual files, not a generic reply.
Security questions come first, so here are the accurate answers before anything else.
Zipchat does not hold SOC 2 certification at this time.
Included in the snapshot
Not indexed
Three steps from your Zipchat dashboard to a code-aware AI.
To reflect new code changes, disconnect the repo and reconnect from the Integrations dashboard. Zipchat will index a fresh snapshot of the current default branch.
A developer asks: "Why is my API call returning a 403?" The AI looks up the actual error-handling logic in your codebase and gives a specific answer tied to the relevant files, not a generic troubleshooting checklist. Support tickets that would otherwise require an engineer get resolved from chat.
See ticket deflection use cases
New engineers ask the AI questions about the codebase instead of pulling senior engineers off tasks. "How does the auth middleware handle token refresh?" gets a real answer with references to the relevant files. Onboarding time drops and institutional knowledge stops living only in senior engineers' heads.
See internal knowledge base use cases
Prospects on your docs site ask code-level questions about integration depth, API behavior, or implementation patterns. The AI answers with references to actual code paths rather than generic marketing language. Buyers get answers faster and sales engineers spend time on deals, not documentation.
Zipchat indexes a snapshot of your repo at connection time. There is no automatic re-sync when you push new code. To update the AI's knowledge of your codebase, reconnect the repo from the Integrations dashboard.
For teams with frequent deploys, the recommended pattern is to reconnect after major releases or architectural changes rather than after every commit.
The GitHub integration is available on all Zipchat Code plans. See pricing.
Yes. When you install the GitHub App and authorize repos, you select which repos to include. Private repos are supported with the same read-only access model as public repos.
Zipchat indexes a snapshot of the default branch (typically main or master) at the time of connection. Non-default branches are not included in the snapshot.
Yes. If you connect a monorepo, Zipchat indexes all source files within it. For very large monorepos, indexing may take longer. The AI can reference any file within the indexed repo, regardless of directory depth.
Zipchat does not have access to files excluded from the repo (for example, files listed in .gitignore). Source files are indexed as-is from the repo archive. We recommend ensuring secrets are stored in environment variables or a secret management tool, not committed to the codebase.
Not currently. Zipchat connects to repositories on github.com only. GitHub Enterprise Server (self-hosted) is not supported at this time.
Reconnect the repo from the Integrations dashboard. Zipchat will index a fresh snapshot of the current default branch. There is no automatic re-sync on code push.
Go to your GitHub account settings under Applications and remove the Zipchat GitHub App. This immediately terminates Zipchat's access to all connected repos.
Yes. You can authorize the Zipchat GitHub App at the organization level and select specific repos within that organization.
Security summary: No model training on customer code. Code indexed in an isolated sandbox environment. GDPR-compliant data handling. Access revocable at any time from GitHub App settings.
Connect in three steps. Your AI gets access to your source code, pull requests, and issues, and starts giving specific answers drawn from your actual codebase.
