What changed in 2.0

One release, three honest sentences: the licence changed, the product went enterprise-only, and the founding refusal — we never read your content — stayed exactly where it was.

The licence

Versions 1.8.9 and earlier are MIT. Forever — that grant is irrevocable and those releases stay on PyPI untouched. From 2.0.0, Siphrix is source-available under the Business Source License 1.1: every line stays readable, production use requires a commercial licence, and every version becomes MIT four years after its release. The full statement, including the superseded MIT-era text kept under its banner rather than erased, is in the repository's LICENSING.md. Claims are superseded here, never deleted — an audit product that rewrote its own history would have no product left.

The business

Siphrix is sold to organisations, invoiced, one plan. Self-serve signup is closed; the old install.ps1 / install.sh one-liners answer with a retirement note instead of an installer. Machines are enrolled by your organisation — a signed Windows installer deployed through Intune, one connection code per machine, never a secret on a command line.

New since 1.8.9

• Enterprise sign-in, complete. OIDC with IdP group→role mapping (an IdP can never mint an owner), a SAML 2.0 SP (SP-initiated only), and SCIM 2.0 provisioning — offboarding deactivates the account and revokes live sessions in the same breath.
• Fleet deployment. Version-true installer metadata, silent enrolment via a staged code file, browser extension managed by policy (the organisation's choice wins over the popup), and a Machines view that shows agent version and last-seen — rollouts you can watch.
• Personal-data flags, without reading anything. NI numbers, payment cards, IBANs, bank accounts and payroll rows are recognised by shape and checksum on your machines; only a category label ever travels. One named alert channel, de-duplicated, muteable.
• The Copilot direction. A file appearing in "Microsoft Copilot Chat Files" is recorded as handed to Copilot — and a file from a payroll, HR or legal area raises a critical alert. Files that appear while an AI site is in use on the same machine are reported as exactly that: a coincidence in time, by the server's clock, never a claimed cause.
• Who can access that file. On demand, from Microsoft Graph: grants, groups and sharing links for one OneDrive file — never its content, and nothing stored.
• Evidence that argues for itself. Machines sign their coverage claims with keys that never leave them; the compliance report carries a detached Ed25519 signature and verifies offline with siphrix verify-report — no call to us required.

What did not change

No document contents, no prompts, no completions, no pasted values — detection runs where the data lives and labels are what travel. The one amendment is stated in the code that implements it: the LLM proxy now reads the shape of a request before forwarding it, and records a category, never a byte. The code is source-available so this paragraph can be checked rather than believed.

Questions, licences: hello@siphrix.com