---
title: "Knowledge: company RAG for engineering · Frazer"
description: "Frazer Knowledge maps your code and your company. Every answer cites its sources, follows each person’s permissions in the source, and is evaluated before any change ships."
url: https://frazer.ai/knowledge
index: https://frazer.ai/llms.txt
tokens: 1139
---

> For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt.

# Knowledge: company RAG for engineering · Frazer

Knowledge · Company RAG for engineering Fig. 1

# Company knowledge  
in every session.  
Permission-aware. Measured.

Frazer Knowledge maps your code and your company: repositories, pull requests, issues, runbooks, incidents, docs and threads. Every answer cites its sources, follows each person’s permissions in the source, and is evaluated before any change ships.

[Create a knowledge base](https://frazer.ai/start?product=knowledge)  `frazer knowledge create --preset engineering`

How do we rotate the payments webhook secret? ask as noah · acme-company

Create the new endpoint secret at the payments provider, store it as PAYMENTS\_WEBHOOK\_SECRET in the payments secret store, and deploy with both secrets accepted for one hour1. Remove the old secret after the dashboard shows no failed deliveries2. Payments on-call approves the production step3.

1.  1 runbooks/payments-webhooks.md · acme-payments@main GitHub
2.  2 Payments handbook › Secrets Notion
3.  3 Thread in #payments-oncall Slack

Cites every sentence · only what noah can open Good · Weak · Wrong

**Fig. 1** An answer from acme-company, as noah · demo organization

01 · Built for engineering Fig. 2

## It reads code like an engineer.  
And the company like a colleague.

Code is split by symbol, a pull request stays together with its review threads, a Slack thread is one document, tables are never cut in half. Runbooks and incidents come straight from the Frazer catalog.

**Fig. 2** Sources → connectors → index → MCP → every tool

02 · Permissions follow the source Fig. 3

## Same question, different people,  
the answer each of them may see.

**Fig. 3** Four steps between a question and a chunk

noah · payments team3 sources

Rotate at the payments provider, store as PAYMENTS\_WEBHOOK\_SECRET, accept both for an hour, remove the old one when deliveries are clean.

runbook · handbook · #payments-oncall

contractor · web team1 source

The public docs explain webhook signatures. The rotation steps are in documents you can’t open; ask the payments team.

public docs · no private sources used

03 · On every devbox, automatically Fig. 4

## Already connected  
when you open the box.

Admins tick a knowledge base in the provisioning profile. Every box in scope gets it in every tool, with a short-lived token for that person. Nothing to install, no keys to paste.

```
# provisioningProfiles/acme-baseline@v12
items:
  - kind: knowledge
    ref: knowledgeBases/acme-engineering
    enforcement: locked
  - kind: knowledge
    ref: knowledgeBases/acme-company
    enforcement: default
  - kind: mcp
    ref: frazer
    enforcement: locked
```

**Fig. 4** A profile item, as an admin writes it

**Fig. 4b** Rendered into each tool’s own config

04 · Retrieval that works Fig. 5

## Hybrid search, reranking,  
and the courage to say “I don’t know”.

**Fig. 5** The query path, with its defaults

05 · Evaluations

## Every change is tested  
before anyone sees it.

Each base has a golden set drafted from its sources and reviewed by a person, a permissions set run as test identities, and graded feedback from real use. A new index is built next to the live one and switches only if the gate passes.

Retrieval Recall@10, MRR@10, nDCG@10

Answers Faithfulness, relevance, citation validity, decline correctness

When Every index build, every setting change, nightly

| Gate rule (default) | Threshold |
| --- | --- |
| No metric drops more than 2 points | −2 pts |
| Faithfulness | ≥ 0.85 |
| Citation validity | ≥ 0.95 |
| Decline correctness | ≥ 0.80 |
| Permission leaks | \= 0 |
| p95 retrieval latency | +20 % max |

Thresholds are the defaults each base starts with. Every run reports the new index against the live one.

06 · Where it runs, what it costs

## Your servers, your vectors.

Connectors, the query service and the vector engine run in your organization’s data cluster, on your servers or the Frazer fleet. One organization’s vectors never share an engine with another’s; text and vectors are encrypted at rest; query logs keep ids and scores, not text.

On your servers **$0** for Knowledge itself; model calls through the LLM gateway

On the fleet **$0.25** per GB-month of index · **$0.50** per 1,000 searches or answers

Free each month 1 GB of index and 10,000 searches on the fleet

Connectors Included, no per-connector fee

## Ask your company.  
Get an answer you can check.

[Create a knowledge base](https://frazer.ai/start?product=knowledge) [See devboxes](https://frazer.ai/devboxes)