Here it is
Your license file is emailed to the address you paid with, and it goes in your FoundrySuite data folder — not beside the launcher, and not anywhere on the network. FoundrySuite reads it once at startup, checks a signature against a key built into the program, and gets on with it. No sign-in, no activation wizard, and no question for your computer to answer over the internet before it will start. It works with the network unplugged.
Finish your license
Payment is not quite the last step. Every license is bound to the one machine it may run on, and that binding needs a fingerprint only this machine can produce. Two minutes, once, and the file is yours.
- On the machine you will use FoundrySuite on, run leadflow license fingerprint. It reads the machine’s identifier locally and prints 64 hexadecimal characters. It makes no network call.
- Open the fulfillment page and paste them into the field. The signed license is emailed to the address you paid with, and downloads from the same page, so it is yours even if no mail ever arrives.
Your checkout session was found in this page’s address, so the fulfillment page opens with your purchase already filled in.
Download FoundrySuite
Linux x86_64 binary available now. Windows and macOS run from the source — see the install guide for details.
Keep your receipt email. It is the proof of what you bought, and if anything at all goes wrong, that email and one message to us is all it takes to sort out.
Check the download before you run it
You are about to run a program from a company you have not dealt with before. This is how you confirm you got the file we sent, without installing anything to do it.
Every release ships a SHA-256 checksum — a 64-character fingerprint of the files, printed below. If your copy produces the same fingerprint, the file is byte-for-byte the one we built, and nothing was altered between our build and your hard disk.
The whole bundle, one digest:
46c429c3dd4e9a1878b1f5a14d2d7059d8025c67550eaec6189563373327060b
The full per-file list is published alongside the installer as SHA256SUMS.txt.
How to check it
Windows, in PowerShell:
Get-FileHash .\FoundrySuite-1.0.zip -Algorithm SHA256macOS or Linux, in a terminal:
shasum -a 256 FoundrySuite-1.0.zipCompare the output to the digest above. Identical means intact. Any difference means stop and email us — do not run it.
What this does not prove
Worth being straight about: a checksum tells you the file has not changed in transit. It does not prove who sent it, because anyone able to swap the download can swap the checksum published next to it. What makes it worth doing is that it is the same fingerprint that appears in your receipt email, which reaches you over a different channel than the download. Check it against the email, not against the website, and it is a real check rather than a formality.
What happens the first time you open it
Three steps, in this order, and none of them asks you to prove anything.
Unpack it
Put the folder wherever you want the software to live. Not in Program Files, not somewhere you have to be an administrator to read. It keeps its own environment inside itself, so there is nothing to install first.
Decide about the AI
The AI features need model weights, and FoundrySuite does not put them in the installer. What it carries is a manifest naming each file, the Hugging Face revision to fetch it from, and the SHA-256 of those bytes: a file is downloaded only once you have agreed to it, and it is checked against the digest before it is accepted, so one that does not match is deleted rather than used. Budget about 5.7 GB for this, once. On your first run FoundrySuite tells you the total, lists who publishes each file, and waits for you to agree before a single byte moves. Say no and nothing is fetched and nothing is remembered against you: the books, the contacts and the pipeline work as they always did, and the software says plainly that the AI features are waiting on weights rather than showing you an empty result that looks like an answer. Say yes and it downloads in the background, with the AI features switching on as each file lands.
One thing to know before you commit to it: the language model is IBM’s, from IBM’s repository. The two OCR files are not DataLab’s — DataLab publishes no GGUF, so those are community quantizations from a third-party Hugging Face account. The digest verifies the bytes, not the publisher. The Privacy Notice names all three sources.
You can take either model out of it. The dialog draws a box per model rather than per file: the language model, and the OCR pair, which are two files and one inseparable choice. Untick one and that model is no longer offered, is not counted in the total, and will not be fetched — now or at any later prompt. Untick both and FoundrySuite will not download any weights at all, and will say so plainly rather than leaving you to wonder whether a 5.7 GB install failed. There is a field for a model file of your own as well, for the language model. A model you take off the list is remembered, but as a setting rather than a mark against you: a line in model-preferences.json in your data directory, never sent anywhere, and undone whenever you like from Settings → Model files.
Make the first account
Create the user who owns this installation. It exists on this machine and nowhere else. That account is the administrator, and only you can add the people who work alongside you.
There is exactly one fetch, and it waits for you
When you first start it, FoundrySuite asks whether you want about 5.7 GB of model weights from huggingface.co. It shows the total, the size of each file and the account each one comes from, and the box has to be ticked before the button will do anything. Nothing is fetched until you do that, and if you would rather not, nothing is written down — the same question is simply asked again next time, and the download stays available for good under Settings → Model files. There is a third answer besides yes and no: untick the models you will supply yourself, and that is remembered as a setting you can change back. Once you agree it runs once, in the background. You can watch it; leadflow models prints the percentage, and re-running it picks up where the last attempt stopped. Every file is checked against its published digest before it is accepted.
After that, nothing is fetched unless you ask for it. FoundrySuite never checks whether that download is still current, never re-downloads it, and never phones anywhere — no update check, no telemetry, no analytics. The only feature that uses a network connection afterwards is researching a company online, and that is off until you ask for it. Pull the cable out and everything except web research keeps working.
Moving it to another machine
Because you bought it rather than rented it, this is a supported thing to want.
Copy the whole folder. Launch it on the new machine and it runs. Nothing phones home to check whether this machine was already registered, because there is no registration to check and nothing in the software that would need to.
Your data goes with you as well, because it was never ours: it is the data/ folder. If you are moving from one machine to another, copy that folder across and you have moved everything.
If you brought your own model
Copy the models/ folder across and the new machine has it too — which is also the fastest way to set up three machines on the same desk. No download, no wait, and the AI features work as soon as the program starts.
We do not host the weights, so we cannot send them you. On a machine without them, FoundrySuite will fetch the same three files from the same pinned Hugging Face revisions — once you have seen what that costs and agreed to it, and never before.
If something has gone wrong
All of it is worth one email, and you will get a person.
The installer will not open.
Check you unpacked the whole archive rather than dragging a single file out of it — the folder and its contents travel together.
The AI says the weights are not installed.
It means the download has not finished, or you never started it. Run leadflow models to see the progress or start it again — it shows you the same total and sources and waits for your answer, and it resumes rather than restarting. If you would rather not download them at all, put your own model files in the models/ folder, or point FoundrySuite at a local endpoint you run. Everything except the AI works exactly as it did before. How →
It says it is not licensed.
That means it cannot find a license file it can accept, and the message names the exact reason — none, malformed, or issued for a different computer. Run leadflow license status in a terminal to see which, then leadflow license install with the file from your receipt email. If it says the license is for another computer, the fulfillment page issues one for this machine: run leadflow license fingerprint, paste the output, and the file follows. If the machine has no stable identifier to fingerprint, send us the output of leadflow license status and we will reissue it for this one, free.
I want a refund.
Ask, and you will get an answer from a person rather than a form. The support page says plainly what we have and have not decided, and this line is not a policy: if it needs one, we will publish it rather than leave you to find out after paying.