Here it is
Your licence file is in the same email as your receipt, 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.
Download FoundrySuite
One archive. Inside it are Windows, macOS and Linux launchers; you use the one for the machine you are installing on.
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 a language model, and FoundrySuite does not ship one. The installer carries a manifest naming the files it looks for and, for each, an address and a digest: where an address is published, the file is fetched on first run and checked against its digest before it is accepted, and one that does not match is deleted rather than used. Where no address is published, nothing is fetched and the AI features report the weights as absent instead of failing quietly. Everything else — the books, the contacts, the pipeline — does not wait on any of it.
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.
Nothing is fetched behind your back
If a model download is available it happens once, on first run, with a progress bar you can watch and cancel, and it resumes if the connection drops. FoundrySuite never checks whether that download is still current, never re-downloads it behind your back, and never needs a network connection again — the only feature that uses one afterwards is researching a company online, and that is off until you ask for it.
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 the model has to be fetched again
It will be, on a machine that never fetched it. On a machine that has, you can copy the models/ folder across instead and skip the download entirely — which is also the fastest way to set up three machines on the same desk.
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. On macOS the first launch is unquoted by Gatekeeper once; the launcher handles that itself.
The model download failed or stopped partway.
Start it again. It picks up where it stopped rather than starting over, so a dropped connection costs you minutes rather than the whole file.
It says it is not licensed.
That means it cannot find a licence file it can accept, and the message names the exact reason — none, malformed, or issued for a different computer. Run foundrysuite license status in a terminal to see which, then foundrysuite license install with the file from your receipt email. If it says the licence is for another computer, send us the output of foundrysuite license fingerprint 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.