In professional services, losing knowledge costs you twice.
You rebuild it for the next engagement, and you already paid for it on the previous one.
Knowledge leaves with people.
A consultant who moves on takes the memory of their engagements: why choices were made, the client relationship, what worked. What stays behind is a folder of deliverables without the reasoning that produced them.
What stays is scattered.
Proposals, deliverables, scoping notes, meeting minutes: spread across the file share, the inboxes and the partners’ heads. Nobody owns it, it goes stale, and nothing traces who is allowed to see what.
And your method feeds a rented AI.
Your value is your method. Pouring it every day into an intelligence you do not own means building the business of a vendor who can cut access, change prices or shut the service down.
The answer to all three is the same: clean, structured, current, governed context that stays with you.
What your Kastel holds, for a firm
Not yet another document store: a structured representation of your business that any AI can read, within the limits you set.
Your clients and engagements
Linked records, never duplicated: a client exists in one place, connected to its engagements, its proposals, its contacts.
Your actual method
Scoping, delivery, review, handover: how work really gets done at your firm, exceptions included. The real procedure, not the brochure version.
Who decides what
Who is allowed to see which perimeter, who a validation escalates to. The same filter applies to people and to the AIs you plug in.
The case memory
Decisions made, their date, their reason, and what they replaced. Nothing is erased: what is no longer true is marked as such.
The tools you already use - email, file share, CRM, ticketing - plug into it. And under the hood it is versioned text files: export is total, your knowledge is locked in no proprietary format.
What it changes, day to day
Four moments every firm knows.
- 01
A new proposal goes out
The AI builds on what your firm already knows: comparable engagements, the method, past decisions. It does not start from a blank page, it starts from you.
- 02
A consultant joins
They query the firm’s memory and get the real procedure, the real precedents, within the limits of their perimeter. Onboarding leans on what is written, not only on who has time to explain.
- 03
A consultant leaves
What they structured and had validated stays: the reasoning, the decisions, the client context. Kastel does not retain people; it makes their time leave more behind than deliverables.
- 04
A client comes back two years later
The engagement context is there: what was decided, when, why, and what has changed since. The answer draws on the case memory, not on the memory of whoever handled it, if they are even still around.
Your clients trust you with their data. That does not change.
A firm works under NDA. Access control is not an option in Kastel: it is its pivot.
You decide what each AI is allowed to see
Each plugged-in AI gets an access of its own, limited to the perimeters you authorise. Two people asking the same question do not get the same scope of answer.
Your own AI keys
Inference runs on your keys, with the provider you choose, or on a model running on your own infrastructure. Kastel never resells inference and takes no margin on it.
AIs propose, a human approves
No AI edits your company memory directly. Proposals arrive in a queue, with the exact change they produce, and a sensitive action waits for the approval of the person accountable for it.
Everything is traced
Every write is attributed to its author, and governed actions are sealed in an audit chain. When a client asks who has access to what, and who approved what, you have an answer.
Your methodological capital belongs to you
Only now, the question of ownership. In a business where knowledge is the product, it is not a compliance detail: it is the goodwill itself.
On your infrastructure, if you want
Kastel runs on your own server, and the complete core is free there, forever. If you would rather operate nothing, we host an isolated instance for you, in Europe.
Total export
One command, and everything comes out: context, governance, logs. Text files, readable without any Kastel tooling.
Swap the AI in one click
The AI is a mercenary you swap in one click. Same Kastel, same standard socket, same access principle: replacing a model rebuilds nothing.
You are locked in with no one
The protocol AIs plug into, the export format and the connector contract are open and standard. You own your data and your context.
Kastel is not exempt from its own rule: total export at any time, free self-host for life. Proof, not promise.
Let’s build your fortress.
The complete core is free when self-hosted. If you would rather we host it, or want help building it, tell us.
Prefer to be guided? Our partner integrators will take it from here.