Teams & Enterprise
A new dev is productive the day they arrive.
One persistent environment per project, where your team's coding agents keep running and every dev attaches to the same session. Hosted in France, by a company under French law, with a DPA you can show your own clients.
- Hosted in France
- Signable DPA
- SSO/SCIM on the Regulated line
- Audit log
$ ssh team@project-acme $ tmux attach -t acme > session live · 3d 14h · attach #4 > audit: attach #4 logged · acl: 4 devs > region: france
A new dev attaches to a running project.
$ ssh team@project-acme $ tmux attach -t acme > session live · 3d 14h · attach #4 > agent: claude code (byok) > region: france
A team needs one environment per project, identical for every dev, still running when someone leaves. The environment and its history stay put; people attach and detach. Onboarding a dev added mid-project is tmux attach, not a setup week.
same environment every attach · history intact since day one
One isolated environment per client.
client A
own vm · own filesystem
client B
own vm · own filesystem
internal
own vm · own filesystem
one DPA · under French law
Each client's code lives in its own environment with its own filesystem and its own access list. Devs switch clients by switching sessions, never by mixing repos on one laptop. When an engagement ends, you close the environment: the VM and its filesystem go with it. What outlives it is the paperwork, not the code.
When your client's next RFP asks where their code sits: in France, under a DPA you can show their DPO.
Regulated sectors
Your own tenant, under French law.
On the regulated line your environments run single-tenant: dedicated machines, no neighbor workloads, hosted in France by Permia SAS, a company under French law with no US parent and no US point of presence. A US court order to a provider does not reach this infrastructure first; a French court does.
Your environment and the code stored in it stay in France. What your agent sends to its model vendor travels on your own keys, to the vendor you chose, whether that is Claude Code, Codex, Mistral or a local model running inside the tenant; we never sit in that path. We sell the environment and the hosting, never the model.
HDS / SecNumCloud: roadmap, not certified
What your legal department gets to read.
Contract
- DPA, downstream: a data processing agreement you can enforce toward your own clients.
- Sub-processor list: public, linked from the footer of every page.
Control
- SSO/SCIM: included on the Regulated line, no enterprise paywall.
- Audit log: who attached to which environment, and when.
- Access lists: per environment, per client, revocable the day a dev leaves.
Exit
- Standard stack: Linux, git, tmux; nothing proprietary in the way.
- Reversibility: your data exportable, the path documented before you sign.
Migration happens on a call with your lead dev.
- Scoping call: your repos, your agents, your constraints.
- We provision the environments and migrate with your lead dev on the call.
- Your team attaches. A human in France stays reachable.
The setup fee pays for this work. It is itemized on the quote, not folded into a mystery number.
How buying works.
- One annual price, invoiced by SEPA. A real invoice your accounting department can handle. No metered line items.
- The setup fee is itemized as the onboarding work above.
- Team plans from 1,490 EUR/yr (3 seats, +300 EUR per extra seat, 390 EUR setup). The regulated line at 4,990 EUR/yr (+490 EUR per seat, 1,990 EUR onboarding). Enterprise on quote, with the levers named: dedicated tenancy, volume, onboarding scope.
- What legal will ask, ready now: DPA, sub-processor list, AUP, residency documentation. All on the Legal & Documents page.
One environment per project. One contract your legal department has already read.
Book a 20-min demo. A human in France answers. Bring your lead dev and your DPO to the same call; we can send the DPA ahead of it.