A group of enterprise software companies

Software that proves what happened.

Six companies. Different buyers, different industries — and one idea: a system should report what it can evidence, and say plainly what it cannot.

A system should report what it can evidence — and say plainly what it cannot.

The principle

Most enterprise software is confident by design. A dashboard shows a number because showing a number is what dashboards do; a variance report explains one hundred per cent of a movement because leaving a gap looks like a defect; a security tool asserts that a control is working because that is what was bought.

The gaps get absorbed quietly, and the person relying on the output has no way to tell which parts are established and which are inferred.

We think that is backwards. Every product in the group makes the same unfashionable choice: they surface the part they cannot support rather than smoothing it over.

It makes for less impressive demonstrations — and considerably more useful software.

01 / FINANCE

A variance engine that publishes the remainder

An amount it can't tie to an approved driver is shown as unresolved, with an owner — not netted away.

02 / SECURITY

A platform that shows you before it blocks

See exactly what would have been stopped, across real traffic, before anything is enforced.

03 / AGREEMENTS

A record a third party can verify

Completion records anyone can check independently — without having to trust us.

The companies

Six companies, one standard.

Each is built for its own buyer and run as its own company. What they share is how they're engineered — and what each one refuses to fake.

A

Agent Trust Cloud

Inventory, runtime enforcement and exportable evidence for AI agents from any framework.

The proofIt runs in monitor mode first. You see exactly what would have been stopped, across weeks of real traffic, before anything is enforced.

agenttrustcloud.com
Q

Qeluntra

Source-to-pay, supplier onboarding and supplier risk on one data model.

The proofThe supplier risk register is a live view of the operational record, not a document someone refreshes before an audit.

qeluntra.com
P

Pactlyra

Prepare, route, sign and verify business agreements in one workspace.

The proofEvery completed action leaves a hash-chained record and an exportable certificate that can be checked independently of us.

pactlyra.com
V

Valcenra

Evidence-first financial control — what changed in the numbers, and the records behind it.

The proofAn amount it cannot tie to an approved driver is published as an unresolved figure with an owner, rather than netted away.

valcenra.com
V

Veystrum

In development

Schedule, cost and approvals for project delivery, on one data model.

The proofThe delivery team's board and the board pack cannot disagree, because they are the same records. Where a regime isn't implemented, it answers "I cannot tell" rather than guessing.

veystrum.com
N

Naseej Consulting

Workforce operations from requisition and hiring through to engagement, time and billing.

The proofA working demo on sample data with no signup and no email address — and the record carries through to what an engagement cost against the role it was approved for.

naseejconsulting.com

How the group works

Separate companies. Shared engineering.

We're not going to pretend these are a suite. A procurement director evaluating Qeluntra has no interest in project controls, and nobody should have to buy six things to get one. What they share is an engineering position — one that only becomes visible at the seams.

01One data model per product rather than integrated modulesTwo systems of record that drift apart and need reconciling
02Evidence is produced as a by-product of the work, not assembled afterwardsAn audit trail that exists only because someone remembered to keep one
03Unexplained amounts, unverified controls and unknown states are reported as suchOutput that looks complete and is quietly partly inferred
04A customer can verify the claim without trusting us to be honest about itAssurance that depends on the vendor's word

The test we hold ourselves to

If a regulator, an auditor or a sceptical customer asked how you know a number or a control is correct — could you show them, without asking them to take the software's word for it?

Anything that fails that test is not finished.

Where this comes from

The same frustration, in different industries.

In each case the software wasn't wrong so much as unaccountable. It produced an answer without producing the basis for it — and the people responsible for the answer had to rebuild that basis themselves, in Excel, at the end of every month.

That is the work these products are trying to remove.

Procurement

Teams maintaining a risk register in a spreadsheet because the platform's version was a month behind reality.

Finance

Teams reconciling a variance report by hand because the tool had allocated the remainder to whichever driver had room.

Security

Teams asked to switch on blocking for AI agents nobody had inventoried.

Contact

Talk to Globixera.

Globixera is the holding company. For a product question, that company's own site is the fastest route — each has its own team.

Group, partnership or press: hello@globixera.com

Send the group a message

For partnerships, investors and press.

Opens your email app with the message ready to send. Please don't include anything confidential.