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.
Xi-Batch and Xi-Text have always run entirely on customer-owned systems. This page explains what that means for current procurement and data-residency requirements.
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, so there is one product fewer to patch and renew.
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.
The data lives wherever you put the server, which you can already document.
The interfaces are native
GTK3, Motif, the full-screen character interface and the command line - as set out on Platforms. They work over SSH, over a serial console, and on a machine with no browser installed.
An operator needs no browser, so there is no web endpoint of ours in your operational path and nothing to expose on a console network.
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.
Licence renewal can reach our licence server over the internet, which is scriptable and saves a manual step. It is optional and it happens at renewal rather than in the operating path: licences can be issued and applied without it, and a system that never contacts us runs the same as one that does.
EU alignment
The Product Management 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.
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.