Hlebourg FZCO · Dubai
Three lines of operational software for the places an organisation loses its own trail — documents after they leave your perimeter, strain that never reaches a survey, and work done where the network is not. Every one of the 9 products runs in infrastructure you control and ships an MCP server, so an agent can operate it without a bespoke integration.
The through-line
These lines look unrelated until you ask the same question of each: where does this organisation stop being able to account for what happened?
A file shared legitimately with eleven people is controlled for the three months of a transaction and uncontrolled for the decade afterwards. A person's workload is legible in a resignation letter and in almost nothing that precedes it. A commitment made on a vessel, a site or a ward exists on paper until somebody has signal again, and the reconciliation is done by memory.
Each of those is a gap between what happened and what the organisation can later demonstrate happened. They are not adjacent markets. They are the same failure in three different departments, and each one is usually sold a product that measures the part that was already visible.
Agents make all three worse and faster. An assistant that fetches a document, writes a summary and sends it has crossed the perimeter three times in a second; an engineer whose working pattern changed because twenty agents now run in parallel is invisible to an annual survey; a field tool that queues work offline now queues an agent's work too. Speed is not the problem. The absence of a trail is.
What follows from that
Three lines
A line is a deployment boundary rather than a marketing group: products inside one share an environment, a store and one agent access profile. A product from the next line knows nothing about the first unless you deliberately connect them.
Confidential document control
Most leaks are not break-ins. A file is shared legitimately with eleven people, and one of them forwards it. Perimeter tooling stops the first case and is blind to the second.
Workforce sustainability
Attrition is visible in the resignation letter and in almost nothing that precedes it. Annual engagement surveys report on a quarter that has already been paid for.
Offline-first operations
Operations software assumes constant connectivity and a head office. Warehouses, sites, clinics and vessels do not have either, and the spreadsheet that fills the gap is never reconciled.
Start here
The rest of the catalogue is a click away; these three are where most evaluations begin.
Agent interface
Every product speaks the Model Context Protocol. That is the easy half of the claim, and it is the half everybody makes.
The hard half is what a vendor does with it once it works. An agent calls a tool under the authority of the person who authorised it, never a service account with a superset of everyone's rights — and every call lands in the audit record with both identities, the policy that allowed it, and the model request it came from. "The agent did it" is not a state any of these products can be in.
The other half nobody prints is the ceiling. Agent judgement degrades as you add tools, so across 70 of ours no single server exposes more than 8. You install two or three, not the catalogue, and during an evaluation we will say which of ours you should leave out.
Three kinds of tool
What is different here
Every one of these costs us something real — a discovery call we cannot run, a capability we cannot claim, a renewal we cannot hold. They are on the website rather than in a proposal because that is what makes them worth anything.
01
02
03
04
The pilot is €9,000, runs on your infrastructure with your data, and is credited in full against the first year if you continue. If the criterion is not met we say so in the report, and that is the end of it — there is no clause that turns a failed pilot into a subscription.