Sovereignty as standard
Everything runs on your systems, and nothing in the operating path depends on us. This is how the products have always worked.
Sovereignty is a live procurement question across Europe, and most answers to it are recent. This one is not. Xi-Batch and Xi-Text have run entirely on the customer's own systems for forty years, because that is what a scheduler and a print spooler in a data centre have to do.
Nothing below is a repositioning. It is a description of how the products are built, stated in the terms procurement now asks for.
Where the software runs
On your systems
Both products install and run on your own hardware or your own virtual machines. There is no vendor cloud in the operating path - no control plane, no telemetry channel, no service of ours that has to be reachable for your jobs to run or your output to print.
Without the internet
They operate where the internet does not reach, including air-gapped estates. Installation needs no external package registry, and neither does runtime: the packages carry what they need.
Without a database
There is no relational database to install, licence, tune or keep running. One less product in the estate, one less licence to renew, one less thing to patch.
Where the data stays
Job definitions, job output, print data and spool files stay on the systems you installed the products on. They are not copied anywhere, and there is nowhere for them to be copied to.
That makes the data-residency question answer itself. Where the data lives is wherever you put the server, which is a decision you already made and can already document.
The interfaces are native
The command line, the full-screen character interface, Motif and GTK3 - as set out on Platforms. They work over SSH, over a serial console, and on a machine with no browser installed.
An operator does not need a browser tab pointed at anything, which means there is no web endpoint of ours in your operational path, and nothing to expose when the network the console sits on is deliberately small.
Continuity
- Perpetual licensing
- The licence does not expire, so continuity does not depend on renewing a subscription, on an acquisition, or on anyone's roadmap. A system licensed today keeps running.
- Supported until at least 2035
- Extended from 2030 at customers' request. The release notes record the extension.
- An independent supplier
- Three of the best-known schedulers in this market now share a single owner. Xi Software does not, and the products are not a line item inside somebody else's portfolio.
One honest qualification
Licence renewal can reach our licence server over the internet, and for most customers that is the convenient way to do it - it is scriptable and it saves a manual step.
It is a convenience, not a dependency. It happens at renewal, not in the operating path, and it is optional: licences can be issued and applied without it. A system that never contacts us runs exactly as well as one that does.
EU alignment, stated precisely
The customer portal carries a Cyber Resilience Act declaration of conformity and a CycloneDX SBOM for each release, so the supply-chain evidence a procurement process asks for is available where you download the software.
For the products themselves, the relevant work is the security hardening campaign that shipped in Xi-Text 1.25.4 and Xi-Batch 1.9.1 in July 2026, and the published vulnerability reporting path - both set out on Security and deployment, which is this argument at the altitude of a network diagram.
Answering a procurement question?
Tell us what the questionnaire asks and we will tell you which of the above answers it, and where the evidence lives.