Developer tools

Usually not. A hosted service takes administration, updates and backups off your hands. An installation of your own, or one at a French provider, earns its place when a customer contract forbids the code leaving your infrastructure, or when everything must stay inside the Union with a named supplier such as OVHcloud or Scaleway.

Yes, on two conditions. First, pick a plan whose current terms rule out training models on your code, which we verify before purchase because those terms move. Second, set plain rules: no customer data and no secrets pasted into a prompt. We apply those settings at organisation level so they do not rest on everyone's goodwill.

Almost always as a per-user subscription taken out directly with the publisher. What matters is that it stands in the company name and attaches to a work account. A subscription bought on a private address walks out with the employee and the money is gone.

Most teams already work largely with free tooling: version control, containers, editors, libraries. What gets paid for is the full suites, the assistants and the build minutes in the cloud. We take the opportunity to reread the terms of the libraries sitting inside whatever you resell.

None whatsoever. We are neither a reseller nor an introducer and no publisher pays us anything. You buy directly, on your own legal entity, and you pay us only for the time spent choosing, costing and configuring. That is the only way advice stays advice.