Skip to content
JeanEnterprise Open Jean

For IT, security and purchasing teams

Every AI your company approves, in one assistant people actually use.

Jean is a folder of static files you serve from your own address. It answers only through your AI gateway, signs people in with your identity provider, and needs no server of ours. Nothing to install, no price per seat.

Get the pilot kitRead the answersTry Jean yourself first

  • No Jean server
  • One header enforces it
  • Your gateway, your sign-in
  • Free per seat
  • Open source, MIT
  1. A browser tabJean, served from your own address
  2. Your AI gatewayLiteLLM, Portkey, Cloudflare, Azure API Management, Albert…
  3. Your modelsIn your cloud, on premises, or at a provider you chose
  • Your identity providerEntra ID or any OpenID Connect: the sign-in goes to the gateway
  • Your OpenTelemetry collectorThe audit, with a key
  • Servers of oursNone in the path
Each person’s work stays in their browser, sealed. Requests go only where your policy and your header allow.

Your people already use AI. The question is where it goes.

78%of people who use AI at work bring their own tools.Microsoft and LinkedIn, Work Trend Index 2024

3%of Microsoft 365 seats have paid Copilot: 15 million of 450 million.Microsoft, January 2026

27%of organisations have banned generative AI at least once. People kept using it.Cisco Data Privacy Benchmark 2024

Your AI gateway is where you govern models, costs and data. Jean gives everyone a front end that keeps it there.

A pilot in an afternoon

Hand it to your coding assistant

Paste this into Claude Code, Codex or Copilot. It asks for your logo, sign-in and gateway, then sets up your copy and checks it.

Set up our own Jean with the skill at https://github.com/jean-is/jean/tree/main/examples/enterprise/organisation-setup

Read the skill

Or set it up by hand

  1. Serve the folder

    Take a release signed by Warehouse SAS, or build one, and serve it from IIS, Azure Static Web Apps, S3, a container or any static host.

    npm ci && npm run build:web

  2. Point it at your gateway

    One policy.json beside index.html names your brains, your rules and every address Jean may use.

    { "signIn": { "issuer": "https://login.microsoftonline.com/<tenant>/v2.0", "clientId": "…" },
  "brains": [{ "baseURL": "https://ai.acme.example/v1", "auth": "oidc" }],
  "rules": { "send": "ask", "share": "never" } }

  3. Send one header

    The browser then refuses every other address, whatever Jean’s own settings say.

    Content-Security-Policy: connect-src 'self' https://ai.acme.example

  4. Check it

    Open policy.html at your address. It reads your policy and headers, tries each address, and says what’s wrong.

    https://assistant.acme.example/policy

Then people open the address, sign in with their work account and start. Edge and Chrome can install it as an app through Intune.

The pilot kit: the recipes, the policy, the header set and the trust pack

One box, for everyone

A question, a file or a folder goes in; back comes an answer with its sources, a Word document, a spreadsheet, a deck or a chart. Numbers are worked out by code, not guessed. In 46 languages, right to left included. It asks before sending, sharing or deleting anything.

See what Jean does for everyone

What your teams will ask

One line per question, with its status today. The documents to attach to your review are in the trust pack.

Where do prompts and files go?
To your gateway and nowhere else. Your header makes the browser enforce it.
Built
What can code the AI writes reach?
It runs in a sandboxed worker with an opaque origin and no network. The page enforces Trusted Types and a strict policy.
Built
What stays on laptops?
Each person’s work, sealed with AES-256-GCM. Policy can require a passkey or password lock.
Built
Can the AI read client names and card numbers?
Not if you hide them. People’s names in English, French, German and Spanish, and your policy’s lists and patterns, are found on the device, and a cloud AI reads marks in their place, put back when it answers. What nothing finds goes as it is, and the rest of a text can still say who it is: masked, not anonymous.
With a key
Is every action logged?
Each turn, brain call and tool use goes to your OpenTelemetry collector. Your gateway’s log stays the authoritative one.
With a key
How do we trust a release?
Releases are signed and come with a CycloneDX bill of materials, checked with OpenSSH. Three libraries load up front.
Built
Does it follow ANSSI’s guide?
Each of its 35 recommendations for generative AI systems is mapped in the trust pack: what Jean does, what is left to you, what isn’t built.
Built
Has it been tested from outside?
The brief for the test is published. The test isn’t done yet.
Not yet
Is Warehouse SAS a processor?
Not for your deployment: nothing of yours passes through our servers.
By design
Is there a DPIA?
A template, filled in for what Jean does and left blank for what you decide.
Built
Can we keep records for a set time?
Each task is kept at least as long as you set, six months for the AI Act, with its certificates.
With a key
Is generated content marked?
Pictures and files Jean makes are marked, and each answer has a certificate saying where it was done.
Built
Is our data used to train models?
We never receive it. The terms of your gateway’s providers apply.
By design
How do people sign in?
With Entra ID or any OpenID Connect provider. Their sign-in goes to your gateway as its key.
Built
Which gateways and models?
Any OpenAI-compatible or Anthropic endpoint: LiteLLM, Portkey, Cloudflare, Azure API Management, Albert, SAIA, a server on premises.
Built
Microsoft 365 and Google?
Mail, calendar and files, through your own app registration.
Built
Proxies and mirrors?
Every address can be replaced: model weights, Wikipedia, package registries.
Built
Updates?
Signed releases. Long-term support releases come with a subscription.
With a key
An admin console?
None. You govern in your gateway, your identity provider and your collector.
By design
What is the licence?
MIT. The audit export and retention are under Elastic 2.0 with a key, and become MIT if no key can be bought for 12 months.
Built
What does it cost?
Nothing per seat. Free for an organisation of fewer than 250 people; from 250 people, €9,900 a year, whatever its size, with keys, long-term support and filled-in questionnaires.
By design
Is it accessible?
Partly. Our own audit against RGAA 4.1.2 met 80.7% of its criteria, and the statement lists what falls short.
Not yet
Can we leave?
Everything is plain files and open standards, and nothing sits on our servers.
By design
Who is the vendor?
Warehouse SAS, a French company.
Built
Does it record what people do?
Nothing reaches us. Your audit is off unless you turn it on.
By design
What would the audit hold?
Metadata only by default: which brain, which tool, when. Content only if you add it.
With a key
Does it name people?
When the audit is on, yes, by their work address. Your agreement with staff representatives decides.
With a key
Which brains can people use?
Only those your policy names. Auto picks among them.
Built
Can it reach our systems?
MCP connections that sign in from the browser, named or denied by policy.
Built
Our own skills and templates?
Skills from your own source only, and project templates with locked instructions, skills and rules.
Built
Our documents?
Search over files and folders on the device, and your knowledge bases through connections.
Built

How it compares

Kinds of answer, not products.

JeanPer-seat cloud assistantsAssistant platformsSelf-hosted open-source chat
Where it runsEach person’s browser, from your addressThe vendor’s cloudThe vendor’s cloud, EU optionsYour servers
What you operateA static folderNothingNothing, or their on-premises editionApp servers, a database, storage
Who handles promptsYour gateway onlyThe vendorThe vendorYour servers
ModelsAny, behind your gatewayThe vendor’sMany, through the vendorAny
PriceFree per seat; a subscription per organisationPer seat, per monthPer seat, per monthFree, plus running it
CertificationsA trust pack: nothing of yours on our serversSOC 2, ISO 27001SOC 2, ISO 27001Yours to obtain

What Jean doesn’t do

Everything your review asks for, in the open

Check a release with the OpenSSH every system has:

ssh-keygen -Y verify -f allowed_signers -I jean.is -n file -s SHA256SUMS.sig < SHA256SUMS

Every change passes type checks, unit tests, size budgets, browser tests in Chromium and WebKit, registry signatures and known advisories.

Free for every person. A subscription for the organisation.

One rule: free for every organisation of fewer than 250 people, and €9,900 a year excl. VAT for every organisation of 250 people or more, whatever its size.

A key unlocks every version released before its end date, forever. Jean checks it offline and never calls home.

Questions

Can it sit alongside Microsoft 365 Copilot?

Yes. It serves the people without a Copilot licence, on any device with a browser, and reads and writes Microsoft 365 through your own app registration.

Can it run without the internet?

With your gateway on premises and the header limited to it, nothing leaves your network. On a capable computer, Jean can also answer on the device.

Which gateways work?

Any OpenAI-compatible endpoint: LiteLLM, Portkey, Cloudflare AI Gateway, Azure API Management, and public services such as Albert or GWDG’s SAIA.

Can we put our name on it?

Yes: your name and colours, and your own privacy page and terms.

What if Warehouse SAS stops?

You keep the releases and the code under MIT, and people keep their files. If no key can be bought for 12 months, the enterprise code becomes MIT.

Share this page with your review team

Security, privacy, purchasing and staff representatives each have their answers above. Send them this address:

https://jean.is/enterprise

Questions: arnaud@jean.is