A connector for your company's Claude

Connect every employee to the knowledge in your source code, without giving them access to it.

DeployIt connects your repositories to your company's Claude. Everyone asks about the product, you follow each developer's work, and the source code stays closed: only the developers you choose see excerpts of it.

GitHub, GitLab · 30-day trial, no card required

In your Claude · example

Why do some customers get “Invalid IBAN” when they sign up?

The form rejects an IBAN from a country that isn't accepted for direct debit. It shows the same message when the check digits are wrong, so the customer can't tell which of the two is blocking them.

Verified in the code3 files read · no line shown
  1. Connect your repositories.From GitHub or GitLab (gitlab.com), only the ones you choose.
  2. Share your company link.Each person adds it to their Claude and signs up under their name.
  3. Give a profile to whoever needs one.Everyone can ask questions; developers see excerpts; leadership follows the team.

What each team gets out of it

Support, sales, product, developers, leadership: each asks its question in Claude, and the answer comes from your code. Five examples.

Support

Support answers without waiting for a developer

A customer is stuck on a rule nobody knows by heart: the answer comes from the code, in plain words, with no ticket opened for the engineering team.

“Everyone” profilequestions, never code

Read the guide – Support answers without waiting for a developer
In your Claude · example

A customer says their discount code was dropped at renewal. Is that expected?

Yes. A discount code only applies to the first subscription period: at renewal, the plan price comes back. Nothing tells the customer before the charge.

Verified in the code4 files read · no line shown

Sales

The sales team commits to what the product really does

Before saying yes to a prospect, ask Claude. The answer says what exists, what does not, and how far it can be trusted.

“Everyone” profilequestions, never code

Read the guide – The sales team commits to what the product really does
In your Claude · example

A prospect wants invoices in several currencies. Can we do that?

Partly. Each invoice carries a single currency, set when it is created. The same customer can, however, receive invoices in different currencies.

Verified in the code6 files read · no line shown

Product

Product knows what changed, without rereading the PRs

What landed on the tracked branch, grouped into deliveries and said in plain words: enough to prepare a team update or warn a customer.

“Everyone” profilequestions, never code

Read the guide – Product knows what changed, without rereading the PRs
In your Claude · example

What changed this month in the checkout flow?

Three deliveries. Payment in three instalments is offered from a €150 basket. The delivery address is validated before payment, no longer after. The promo code can be entered on the basket page.

Read from the tracked branch3 deliveries · 17 commits · no name given

Developers

A developer finds the rule without digging through the repository

A newcomer, a module nobody has opened in months: the answer says where it lives and shows the excerpt. Only this profile sees code, and you decide who gets it.

“Developers” profilethe same questions, with excerpts

Read the guide – A developer finds the rule without digging through the repository
In your Claude · example

Where is the token renewal handled, and with what delay?

In the session service. The access token lives 15 minutes; it is renewed on the first request made in its last 2 minutes. A refused renewal closes the session.

// auth/session.ts
if (ttl < REFRESH_MS) {
  token = await refresh()
}
Verified in the code5 files read · 1 excerpt shown

Leadership

Leadership follows each developer, based on facts

DeployIt writes one fact per merged commit: shipped, reviewed or not, tested or not, fixed since or not. Claude builds the table you ask for, by month, quarter, half-year or year.

“Leadership” profileno code, with each developer's work

Read the guide – Leadership follows each developer, based on facts
In your Claude · example

Who shipped what this quarter, with what code score and how many confirmed defects?

Here is the quarter, developer by developer. Defects from the last 60 days aren't mature yet: that count can still rise.

Quarter report, example
DeveloperMerged commitsCode scoreConfirmed defects
Camille R.1323.92
Idriss B.1183.25
Léa M.974.11
Drawn from your commits347 merged commits · sample data

Example questions, answers and figures. In your Claude, the answers come from your repositories.

Example 1 of 5

Try it first, no account

Add this address to your Claude connectors and ask a demo repository: “What does this product do?”, then “What changed this week?”

https://mcp.deployit.ai/demo

The demo answers with the Everyone profile: questions, never code. Developer tracking is something you try on your own repositories, during the 30-day trial.

Two things to ask

No new tool to learn: questions get asked where your team already works.

How the product behaves

Support, product and sales ask, and an agent investigates the code before it answers.

  • “What happens when a payment fails twice?”
  • “What changed in billing this week?”
  • “Can invoices be exported to CSV?”

Each answer says what it is worth: verified, backend only, not found, or "I could not conclude". Only a verified answer counts as a fact.

What each developer does

DeployIt turns every merged commit into a fact credited to its author: shipped, reviewed or not, tested or not, fixed since or not, and what a model makes of the code. Claude builds the report you ask for from those facts.

  • “Give me October's report, developer by developer.”
  • “Who introduced the defects we fixed this quarter?”
  • “Which modules depend on a single person?”
October report, example
DeveloperCommits shippedReviewedTestedCode score
Camille R.4671%52%3.9
Idriss B.3860%31%3.2
Léa M.3566%40%4.1

By month, quarter, half-year or year. The score is always read alongside the number of commits it covers. Sample data.

Who sees what

Your company has one link. Whoever adds it to their Claude signs up under the name and email they declare (the address is not verified) and gets the Everyone profile. You give another profile to whoever you want, person by person.

ProfileCan ask aboutSees code
EveryoneHow the product behavesNo: the agent explains without quoting; a filter removes code, and no filter is infallible
DevelopersThe same questions, down to the detailExcerpts
LeadershipThe product, and each developer's workNo: filtered and tested; no filter is infallible
Data toolThe statistics, for your warehouse or BI tool, with a keyNever

Off-limits topics

Security, internal pricing: you list, profile by profile, what the agent won't discuss.

Names stay with those who need them

With the Everyone profile, the names of the people DeployIt knows are removed from the answers; as with code, the filter removes, it does not guarantee.

A log

Who asked what, and what came back. The context attached to a question and the content the investigation read are not kept.

A leak test

DeployIt attacks every no-code profile itself and tells you what gets out. It warns you; it doesn't switch anything off.

What we do with your code

Put simply, so you can decide. The details are on the Security page.

We read it, we write no code to it

DeployIt reads your repositories; the only thing it adds to them is one webhook per repository, to be told about new commits, and it removes it with the repository. No commit, branch or PR ever comes from DeployIt.

We keep a working copy

It lets DeployIt answer without rereading the whole repository. It is hosted by DigitalOcean in London (United Kingdom), kept while the repository is connected and erased when you remove the repository from DeployIt.

A language model reads your code

At indexing time, the content of each selected file is sent to it to write a summary; after that, what it needs to answer a question or read a commit. OpenAI's models by default; your provider's, for each role where you add your key. We do not train or fine-tune any model on your code.

Tracking is individual, and we say so

Each tracked developer has a record, commit by commit, with the evidence. The rules for this use are set out in our terms of service.

A fixed price, known in advance

You choose how many developers are tracked; the price follows. Everything else is included: repositories, profiles and everyone who asks questions, within a fair-use limit per plan and a per-person cap that you set.

Free

€0 a month

  • 15 questions about the code a week, for the whole company
  • Answers already known don't count
  • No developer statistics
Connect my code

Team

€290 a month

or €2,900 a year

Up to 25 tracked developers

  • Questions, statistics, report prompts
  • All repositories, all profiles
  • Data tool key
Start the trial

Business

€590 a month

or €5,900 a year

Up to 60 tracked developers

  • Questions, statistics, report prompts
  • All repositories, all profiles
  • Data tool key
Start the trial

Group

€1,190 a month

or €11,900 a year

Up to 200 tracked developers

  • Questions, statistics, report prompts
  • All repositories, all profiles
  • Data tool key
Start the trial

30-day trial, no card required, once per account, when you create your first company: everything is open, up to 25 tracked developers. Without a plan at the end of the trial, your company moves to the free plan.

  • No overage, ever: you can't track more developers than your plan covers. A newcomer beyond the limit isn't tracked, and you're told.
  • Coding agents and bots never count as tracked developers.
  • Questions from the whole company are included, within a fair-use limit: a monthly cap per plan, shown in your workspace, lifted if you bring your own model key. The Everyone profile is also capped by default at 40 questions per person per month, a setting you can change.
  • Paying yearly, you pay ten months for twelve. Prices exclude tax. Several companies: one plan each.
  • Beyond 200 tracked developers, let's talk.

Questions we get asked

Could my colleagues end up seeing the code?

Not with the Everyone or Leadership profile: a filter strips code blocks and file paths from answers and, for Everyone, names too. DeployIt also attacks each profile itself with trick questions and warns you if anything gets out. No filter is foolproof, which is why the test shows you what it managed to extract.

Who gets which profile?

Everyone who signs up through your company link gets Everyone. An administrator gives Developers or Leadership to whoever they choose. Signing up again with the same address never gives a broader profile.

Is developer tracking individual?

Yes, that is its purpose. Each tracked developer has a profile: what they shipped, reviewed, tested, fixed, and the score of their code. During the trial or on a plan, tracking starts as soon as your repositories are connected, with 6 months of history: inform your teams beforehand, or turn statistics off. The terms set out the framework, and we give you what you need to inform people, including an export of one person's data.

What is the code score?

A language model reads each commit and scores it from 1 to 5 on five criteria: correctness, maintainability, robustness, tests and security. It is read over a month, a quarter, a half-year or a year, always with the number of commits it covers. It is a clue, not a verdict.

And how is a defect counted?

DeployIt finds the commit that a fix came to repair. As long as only the machine has counted it, the defect is "to confirm". An administrator confirms or dismisses it; an investigation that rereads the code can only confirm it. The human decision prevails.

Does it have to be Claude?

Yes, to ask questions: sign-up works today from Claude (web and desktop) or from a local client such as Claude Code; Cursor and Windsurf cannot sign up yet. A data warehouse or a BI tool reads the statistics with a Data tool key.

We have several companies.

One account, one company per legal entity. Each has its repositories, its link, its profiles, its developers, its log and its plan; nothing passes from one to another. The 30-day trial opens once per account, with the first company; the next ones start on the free plan.

What if we stop?

When your subscription ends, your company moves to the free plan: nothing is erased at that moment, but developer tracking stops and the statistics close; the data is kept for its retention period. While your plan or the trial runs, you can export the statistics with a Data tool key: do it before you cancel. Each person's profile can be exported from Developers. Removing a repository from DeployIt erases its working copy and, if you tick the box, its statistics. You can delete the company once the last paid period has ended (a cancellation takes effect at the end of the period): access is cut at once, then a queued job erases the data, usually within the following hours, and retries if it fails. The daily database backups hold the data until they rotate: DigitalOcean keeps them for seven days.

What is an MCP server?

A server that gives an assistant such as Claude tools it can call, over the Model Context Protocol (MCP). DeployIt is one: you add your company link to Claude's connectors, and Claude calls it when a question is about your product or your developers' work.

Which repositories can we connect?

GitHub repositories, through the DeployIt GitHub app, and GitLab repositories (gitlab.com), and only the ones you choose. DeployIt makes no commit, branch or PR there: it adds one webhook per repository, and removes it with the repository.

Connect your code, ask your first question

30-day trial, no card required. DeployIt reads your repositories: no commit, no branch, no PR.

A question before you connect your code?

Write to us at [email protected]: a person will reply.

We use your address to reply to you, and for nothing else. Privacy