An Independent Publisher, and One That Means to Stay So
One company writes this engine and sells it, and that is what gives you a second supplier where you were down to one.
What a Second Supplier Is
Anybody whose job is buying parts knows this one. You do not buy every screw from the same works. Not because the works is bad — because the day it puts its prices up, or stops making the size you use, or is bought by somebody with other plans, you want a second name in your address book.
Software is bought the same way, except that a piece of software sits deeper in your own product than a screw does. The part of your programs that writes your invoices, your payslips, your statements and your labels is not something you swap in an afternoon. So the question a technical director asks before signing is not whether the thing is any good — it is what happens if they have to leave.
That question has an answer only if there is somebody to leave for.
What a Second Name Is Worth Here
Ask around for a second supplier for this one piece, and count the names you come back with. That number is the whole point of this page.
Here is one more, and here is what it commits to.
If This Company Were No Longer Here
The question behind the question. A second supplier answers what happens if you have to leave; this one answers what happens if we do.
Depositing the source of the engine with an independent trusted third party is available to any customer who asks: write to us and we arrange it. It is handed over to you if this company ceases to exist, discontinues the engine without a migration path, or breaks its commitment after a change of owner.
What we commit to
Six things. Each of them is about us, and each of them can be checked on this website rather than taken on trust.
- No count of what you owe us after the fact. Our licence does not inspect your machines, does not ask what you installed, and does not send us anything. One thing alone is checked: the signature at the end of your licence key, and that happens on your own machine, with no connection to us. Nothing in the library or the server reports back: the server sends its failure alerts only to an address you give it, and to none if you give none.
- The licence is readable before you buy, in full, on this website, with no account to create and nobody to talk to first — and every figure we charge is written beside it.
- We sell to companies, and one company takes the money: ours. No middleman. Everything here is out in the open, and the whole of this website shows it.
- Everything the engine can do is named on this website, and nearly all of it comes with a document you can download and the program that wrote it. What we cannot do yet is written there too.
- Everything runs on your machines if you want it to. Buy the library or the server and nothing you create ever leaves your premises: there is nothing in them that would send it.
- No outside shareholder stands behind this company. Nobody else's timetable decides what becomes of this engine, and nobody else has to be asked before you are answered.
Technically
What is delivered is a compiled Rust library and a CPython wheel built against the stable ABI, both pinned to a version, both fetched from your account here and resolvable from your own artefact store. No build step on the target, no compiler required, and no package index reached at install time.
Zero network traffic from the library, by construction: there is no HTTP client in the dependency tree, and no code path that opens a socket. It runs in a build chain cut off from the network and in a container with no way out. The licence key you were given ends in a signature, verified against a public key embedded in the binary. That text is all the library reads: nothing installed on your machines is looked at, and nothing is counted — an offline operation, with no call home, no floating licence daemon and no seat count.
Output is deterministic: the same inputs give back the same bytes, because the writer never reads the clock and never draws anything at random: a date or an encryption key comes from the program that calls it. That is what lets you compare two builds and lets a regression suite pin a document byte for byte — and it is what the twin-checking script behind this site does across every worked example, in Rust, in Python and as a request over the internet.
Where to Look Next
Our licence, and why your own code stays yours What You Pay, and for How Long Changing the Library That Writes Your Documents What Becomes of the Documents You Send