The request
Each request sends the model only the task's context, capped in size. A boundary against prompt injection guards all outside content.
Each firm's space is partitioned from the others, and every action in it is traced to its source.
Your context layer holds your firm's data, in its own sealed space, wherever your firm decides it lives.
Your own cloudYour context layer runs in your firm's own cloud.
Our cloud in EuropeOur sovereign cloud in France, or a sovereign cloud in your own country in Europe.
In France, with a host qualified SecNumCloud by ANSSI, the French national cybersecurity agency, out of reach of the US Cloud Act.
On premiseOn request and at a premium, your context layer runs on your own servers, inside your firm.
Each firm works in its own partitioned space, and the firm decides who enters it.
Partner, manager, analyst and external contributor each see what their role allows, on the firm's policies.
Consultants sign in through the firm's identity provider, in SAML or OIDC.
Joiners and leavers sync with the firm's directory.
An IP allowlist opens the Workspace only from the firm's approved networks.
Bekames keeps only the de-identified shape of the work, such as its structure and the corrections made to it, never mission content. For a shared workflow, its steps, instructions and templates, de-identified from the firm and its clients.
The AI works inside the firm's Workspace, on the models the firm allows. The firm reads its consumption in real time, by user, team and use case.
Each request sends the model only the task's context, capped in size. A boundary against prompt injection guards all outside content.
The consultant picks a model from the list the firm allows. Models hosted in Europe run by default.
No model keeps mission content or trains on it, whichever model the firm allows.
From the audit log to leaving
Every action, request and answer is logged, timestamped and traced to its source. The consultant confirms what the mission keeps.
The firm exports the log, each request with its sources.
The firm sets retention and deletion policies, with export controls.
After the contract ends, the firm has 30 days to export its data as open files any model reads.
Bekames then deletes it within 30 days in production and 90 days in backups.
| GDPR | Designed to comply |
|---|---|
| AI Act | Designed to comply |
| ISO 42001, AI management system | Designed to comply |
| SecNumCloud | Carried by our host, qualified by ANSSI |
|---|---|
| SOC 2 Type II | After the seed |
| ISO 27001 | Planned |