Questions answered from the source
Project and building teams get the answer from your own specifications, standards and manuals, with the clause or the page cited.
Real estate and construction · AI agents inside the company
Real estate and construction agents. A person decides. Data stays.
Katonic runs AI agents inside your own data centre or private cloud. Agents read your contracts, your specifications and your project and property records, prepare the work, and stop for a named person.
No agent issues a contract notice, certifies a payment, approves a design, signs off an inspection, or accepts or rejects a tenant. It prepares, and a person decides.
Bids, contracts, drawings and tenant records stay on infrastructure you control.
Contracts, drawings and tenant records stay on your infrastructure
A model you serve
Each person's permissions kept
No agent decides about a tenant or a worker
Tenders, contracts, submittals, payment applications and leases run on reading, checking and drafting. That is where an agent helps most, and where a missed date or a wrong decision about a person costs most.
The property-maintenance templates we opened message tenants and contractors with no step where a person approves.
None of the vendor pages we read states an on-premises or customer-cloud option. And running there is not enough: what matters is which tool waits for a person, whose identity the agent uses, and what is recorded.
A contract has clocks. Its notices have time limits and stay with the contract administrator, so an agent lists the dates and sends nothing.
Tools must be chosen one by one: of 15 public real estate and construction interface descriptions the importer read, none was refused; 14 fit the import size limit and carry 548 operations, 227 sent as changes. The fifteenth is one platform's whole description, 3,391 operations in one file twelve times the size limit, so a company imports the part it needs.
Tenant records are personal data, and bids, cost records and drawings are the company's own. Both have to stay inside the company.
What the rules ask
A named duty holder answers for a building's safety record. A person, not software alone, decides what significantly affects a tenant. A contract notice stays with the contract administrator. The company knows where the data is.
Agents read and draft. People keep every decision about the contract, the design, the building and the tenant.
Questions answered from the source
Project and building teams get the answer from your own specifications, standards and manuals, with the clause or the page cited.
Work prepared for a decision
Tenders, submittals, payment applications, variations and handover sets are checked and set out for the person who decides.
Dates you can act on
Notices, lease dates, inspections and overdue defects are listed with the clause or the record behind each.
A record of every step
Who asked, which tool ran and what was decided.
From bids and contracts to design, site delivery, safety and quality, handover, leasing, property operations and finance.
Bids and contracts
Tender packs, quotes, obligations, payment applications
Design and site
Queries, submittals, daily reports, method statements
Handover and leasing
Handover sets, manuals, leases, critical dates
Operations and finance
Maintenance requests, inspections, invoices, cost reports
Each is a use case a developer, a contractor or a property manager can build in Katonic Studio. A name with a link has its own page.
Every agent follows one rule: it prepares, and a named person decides.
Go deeper
Guides and answers
A developer or a contractor that wants AI agents on its own infrastructure has more than one kind of product to choose from. The products sold for this fall into four types: agent platforms you run yourself, infrastructure platforms, automation platforms with agent features, and developer frameworks. Our comparison describes fifteen of them with the same fields, read on each vendor’s own pages: where each runs, who operates it, governance, price and limits. For project work, document permissions by project and approval steps on anything contractual matter most.
On-premises AI agent platforms compared: 15 options by type →An agent reaches your documents and systems in one of four ways, all through the same tool gateway and the same approval rules.
Connection · 01
A tender, a contract, a drawing register, a site diary, a lease.
Connection · 02
Contracts, specifications, standards, method statements, the employer's requirements, leases and operating manuals, indexed with each reader's permissions kept.
Connection · 03
↗Give Katonic the description of an interface you already run, and choose which operations become tools. This is the route to project documents and issues, the programme, cost records, tenancies and work orders.
Connection · 04
↗Servers from the catalogue, deployed inside your own cluster, for the data warehouse, reporting databases and web search.
System names are left out on purpose. You supply the address and the sign-in. Nothing here is a tested integration with a named product.
It runs on the company's own infrastructure or private cloud, with a model the company serves. Bids, contracts, drawings and tenant records stay there.
Every tool call passes the company's policy. A policy can allow a tool, record its use, hold it for a person's approval, or block it, for the whole company or for one project.
A tool that changes something waits for approval unless the company has decided otherwise for that tool. That is how no notice, certificate, reply or payment goes out unapproved.
No agent decides about a tenant, an applicant or a worker. It prepares the record, and a named person decides.
The agent acts as the person using it. Where the company's API checks the caller, Katonic passes the signed-in user's identity, and the agent cannot claim another.
Every call is recorded, with who asked, which tool, and what was decided, and an agent, a tool or a whole server can be switched off at once.
From visual workflows to full code - pick the path that fits your team and project.
Visual Builder
Follow guided steps to build agents. Configure each stage through the UI. No code required.
Best for
Commercial, design and property analysts
Conversational Builder
Staff describe how they check a payment application against a subcontract or a submittal against a specification. AI generates the agent. Developers refine together.
Best for
Staff + Developers together
Full IDEs
JupyterLab, VS Code, RStudio with GPU access, pre-installed frameworks, and direct deployment.
Best for
Data Scientists & ML Engineers
The rules on building safety, tenancy, contracts and site work differ by country and point the same way. Each is a matter of how the system is built.
A safety record with a named owner
Under UK building safety law, a building's safety information must be kept as a record a named duty holder answers for. Here an agent checks the record against the required list and lists the gaps. The duty holder decides what is added and signs it.
A person, not software alone
Under GDPR Article 22, a decision that significantly affects a person, such as a tenancy, is not left to software alone. Here no agent screens, scores or ranks a person for a tenancy, and no agent sets a rent.
Notices stay with the contract administrator
Contract notices have time limits, and they stay with the contract administrator. Here an agent lists the notices a contract requires and the dates they fall due. It sends none.
No agent allocates or scores work
In the European Union, AI that allocates tasks to workers or evaluates them is high-risk from 2 December 2027. Here no agent allocates work to a site worker, and no agent scores one.
Katonic AI is certified to ISO 27001. This is a summary of published rules, not legal advice.
On a contractor's project, a commercial manager uploads a signed subcontract, and an agent lists every obligation, notice period and date with its clause; the manager checks the list against the contract. In the design office, an agent sets a supplier's submittal against the specification and lists each departure for the designer, who accepts, comments or rejects. In a landlord's property team, an agent sets out a lease's term, rent and dates with their clauses, and the team checks the summary against the lease. Each one reads what the company already has, changes nothing by itself, and leaves a record.
Seven questions to ask any supplier before an agent touches a contract or a lease, with our answers.
On infrastructure you control: your data centre or your private cloud. The model is one you serve there.
What the person using it can read. Knowledge sources keep each reader's permissions, and where your API checks the caller, Katonic passes the signed-in user's identity.
Only what you allow. A tool that changes a record, a reply or a payment waits for approval unless you have decided otherwise for that tool.
A named person. No agent issues a contract notice, certifies a payment, approves a design, signs off an inspection, or accepts or rejects a tenant.
No. An agent drafts, and a person reads and sends what goes to a tenant, a buyer or a subcontractor. When the documents do not answer, the agent says so.
Who asked, which tool ran and what was decided, for every call.
At once. An agent, a tool or a whole server can be switched off by your administrators.
A contract obligations summary can run on the first day, because no system of record is touched. Talk to our team about building it on your infrastructure.