In construction, knowledge is paid for in lost margin.
Every project is a prototype. What it teaches you costs dearly, and almost none of it survives handover.
Knowledge lives on site, not in the company.
The memory of a project lives in the site manager's head: the incidents, the fixes that worked, the reliable subcontractors, what was agreed with the design team. When they move to another project or another employer, it goes with them.
What stays is scattered and contradicts itself.
Site meeting minutes, emails, annotated drawings, tracking spreadsheets: spread across the file share, the inboxes and the binders. Nobody owns it, versions contradict each other, and nothing traces who is allowed to see what.
And your pricing feeds a rented AI.
Your price library, your ratios, your estimating methods make the difference between a project won and a project lost. Pouring them 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 construction company
Not another document repository: a structured representation of your business, that any AI can read, within the limits you set.
Your projects and their parties
Records linked to each other, never duplicated: a project exists in one place, connected to its client, its design team, its subcontractors, its decisions.
Your real methods
How estimating, preparation and delivery actually work in your company, exceptions included. The real procedure, not the quality-binder 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 memory of your projects
The incidents, the fixes that were chosen, the decisions made, their date and their reason. What is no longer true is not overwritten: it is marked as outdated, and the trace remains.
The tools you already use - email, file share, calendar, tracking spreadsheets - 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 construction company knows.
- 01
A tender response goes out
The AI builds on what your company already knows: comparable projects, proven methods, actual resources. The technical proposal starts from you, not from a blank page.
- 02
A site manager joins
They query the company's memory and get the real procedures, the real precedents, within the limits of their perimeter. Their ramp-up rests on what is written, not only on who has time to explain.
- 03
A known incident comes back
The execution problem that cost you dearly three years ago is documented, with the fix that was chosen and why. The answer rests on the company's memory, not on the luck of having the right veteran in the corridor.
- 04
The client calls after handover
A defect is reported, a question comes up about what was agreed: the project's context is there, decisions dated and attributed. You answer from what is written, even if the team has changed since.
Your pricing and your margins are nobody's business but yours.
A construction company lives in a permanent consortium: client, design team, subcontractors, joint ventures. Access control is not an option in Kastel: it is its pivot.
You decide what each AI is allowed to see
Each AI you plug in gets an access scoped to its purpose, limited to the perimeters you authorise. Estimates and margins are visible only to the people you designate.
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 modifies 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 who answers 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 you who has access to what, you have an answer.
The knowledge of your projects belongs to you
Only now, the question of ownership. In a trade where the edge is made on pricing and method, it is not a detail: it is your advantage.
On your servers, 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 tool.
Swap the AI in one click
The AI is a mercenary you swap in one click. The same Kastel, the same standard socket, the same access rules: replacing a model rebuilds nothing.
You are locked in with nobody
The protocol AIs plug into, the export format and the connector contract are open and standard. You own your data and your context.
Kastel does not escape 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 in self-host. 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.