Skip to content
Hlebourg

Hlebourg FZCO · Dubai

Agent-native software for work that cannot be improvised

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.

See the productsRequest a 90-day pilot
Products
9
Across three lines, each deployed into its own environment.
Agent tools
70
Never more than 8 on any one server, and you should not install them all.
Default deployment
Yours
Self-hosted, air-gapped included, with nothing gated behind a tier.
The through-line

Three places where the record stops

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

  • The record is the product. Every one of these keeps an append-only trail that we expose no way to edit — including to ourselves.
  • It has to work where you are. Self-hosted by default, offline where the work is offline, and readable by software that is not ours.
  • An agent's action is a person's action. Every call an agent makes is attributable to the human whose authority it borrowed, with the policy that allowed it recorded alongside.
  • What it will not do is written down. Refusing a capability is a design decision with a stated reason, not a roadmap item we are quiet about.
Three lines

What each one is for

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

Nocturne

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.

Who buys it
Legal, corporate finance, deal advisory, IP-heavy engineering
Products
Nocturne Vault · Nocturne Trace · Nocturne Entropy

Encryption, per-recipient tracing and key material for documents that leave your perimeter and must not be untraceable when they do. Built for the files that a DLP product never sees, because they were sent deliberately.

All Nocturne products

Workforce sustainability

Cadence

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.

Who buys it
People operations, engineering leadership, occupational health
Products
Cadence Signal · Cadence Pulse · Cadence Ledger

Burnout screening, team pulse and personal capacity tracking that measure a person against their own baseline instead of a company average. Designed so that the number a manager sees is one the employee has already seen.

All Cadence products

Offline-first operations

Harbour

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.

Who buys it
Operations, trade and distribution, field and site services
Products
Harbour Registry · Harbour Flow · Harbour Watch

A counterparty registry, an order and demand engine, and an obligation follow-up system that keep working with the network cable pulled out. State lives on the machine; synchronisation is something you choose, not something you depend on.

All Harbour products
Start here

One product from each line

The rest of the catalogue is a click away; these three are where most evaluations begin.

Nocturne Vault

Beta

Controlled distribution you own, opened in an ordinary browser

Vault moves from encrypting files on one device to controlling the files you share with other organisations. It is a document room you host yourself, air-gapped if needed. Files render on the server, so readers need only an ordinary browser, and an original is released only where policy permits. Access is decided against attributes, and a refusal names the clause that failed. Every grant carries an expiry. Every open, print attempt and download enters an append-only trail. Your own staff can read offline in an optional desktop viewer.

MCP server
hlebourg-vault
Priced by
One deployment for the organisation, sized on its document estate

Nocturne Vault

Available

Encryption at rest for files on macOS and Windows, with keys protected by the device’s own hardware

Vault is an embeddable component that encrypts files at rest. Each file has its own key, wrapped by a master key, which a root key protects. The root key is held in the Secure Enclave on macOS or as a TPM-backed key on Windows, with the platform’s secure key storage as the fallback. Authenticated AES-256 means a file altered or taken out of its authorised context fails to decrypt with a clear error. The master key rotates every 90 days by default, without downtime.

Platforms
macOS · Windows, offline
You receive
Source code, libraries, optional installers, administrator command-line tool, guides

Cadence Signal

Beta

Burnout screening measured against a person’s own baseline, with results the person sees first

Signal scores a screening questionnaire derived from the Copenhagen Burnout Inventory: personal, work-related and client-related exhaustion on a 0 to 100 scale, in a green, amber or red band. It reads each result against that person’s own 90-day baseline, not a company average. Short check-ins every three to four weeks and work-pattern metadata from your AI gateway feed a drift index; message content is never read, emotion never inferred. The person sees their own file first; a manager sees a band only with consent. Self-hosted by default. Screening, not diagnosis.

MCP server
hlebourg-signal
Priced by
Each person in scope of screening, counted once a month

Cadence Signal

Available

Burnout screening that stays on the employee’s device

Signal is an embeddable burnout-screening module. On the employee’s device it runs a questionnaire built on the structure of the Copenhagen Burnout Inventory. It scores personal, work-related and client-related exhaustion, combines them into a burnout index from 0 to 100 and places it in a green, amber or red band with non-clinical suggestions. Trends cover rolling periods you choose, such as 30, 90 or 180 days. Thresholds, suggestions, reminders and questionnaires are yours to configure; each person can adjust or switch off reminders.

Platforms
macOS · Windows, offline
You receive
Source code, sample configurations, tests, guides; screens not included

Harbour Registry

Beta

An encrypted offline record base that synchronises across devices, with every merge rule declared per field

Registry is an encrypted record base for work orders, inspections, stock counts and approvals; it works without a network and synchronises across devices and with your own backend. Each field is declared in a versioned entity model with its own merge rule, such as a state machine for statuses. Where no rule describes a conflict, Registry quarantines the record rather than guessing. Every mutation is audited with its origin device, so a field’s current value can be traced to the competing writes and the rule applied. Self-hosted by default.

MCP server
hlebourg-registry
Priced by
The autonomous site — one place, vessel or enclave that has to keep working through a disconnection, counted where it is, not by what is in it

Harbour Registry

Available

An encrypted client base that works without a network

Registry is a client base built into your own macOS and Windows applications. It keeps encrypted client cards — contact channels, company details, the responsible person and team, tags, categories, statuses, last contact, next reminder and attached files — on the user’s device. Fields and lists are configurable. Search covers the fields you choose, with filters by tag, category, status and date. Every change leaves an audit entry: who, when and which fields. Selected clients export to CSV or JSON, and reports to PDF.

Platforms
macOS · Windows, offline
You receive
Source code, configurations, tests, guides; compiled components where agreed
Integration

One interface, and an honest account of its limit

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.

How integration works

Three kinds of tool

read
Returns data, changes nothing. The worst case is that an agent learns something its operator was already entitled to know.
write
Changes state inside the product. Granted per tool, and every call names both the human and the agent.
act
Has an effect outside the product — sends, exports, notifies. Off by default everywhere, enabled only against a written policy.
What is different here

Three positions, each checkable before you talk to us

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.

  1. 01

    Every product has a section listing what it cannot do

    Not caveats at the bottom of a datasheet — a required field in the schema these pages are built from, so a product page that does not state its limits fails the build rather than shipping vague. Some of those limits are capabilities we are refusing on purpose, and we say which.

    See the catalogue →

  2. 02

    The exit costs nothing and we will rehearse it

    Full history in a documented format, the question library that makes it comparable, a standalone decryptor for anything encrypted — free during the contract and for as long as we hold a copy of your history, on any anniversary you ask. A renewal conversation held with your own history as collateral is not an honest one.

    Read the exit terms →

  3. 03

    We will design the study that could show we do not work

    Pre-registered, randomised at the organisational unit, run by an evaluator you contract and pay directly, with the outcome measure fixed before the data exists. The strongest evidence against this whole category — Fleming's study of 46,336 workers across 233 organisations — deserves an answer better than a case study.

    How the evaluation works →

Ninety days, one team, a criterion agreed before we install anything

The pilot runs on your infrastructure with your data, and the pilot fee is the whole commitment. 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.

Request a pilotSee all six servicesAsk something specific

Hlebourg is a software design and systems consultancy in Dubai. Software is contracted from there; deployment happens wherever your infrastructure already is.