PCSOFT charges WinDev and WinDev Mobile applications per session: each real combination of user × machine × application × database type counts (official definition, PCSOFT “Sessions” page). Last displayed list price: 290 € excl. VAT per session per year (removed from the PCSOFT site in mid-July 2026 — pricing is now quote-only). The circulating 3-year commitment offer: 75 € excl. VAT in year one… then 100 € in year two and 225 € in year three. A threefold increase over three years, on a session count that grows mechanically.
Calculate my exposure The staged exitEnter your application landscape. The calculation runs entirely in your browser: no data is sent, to us or to anyone. The result is a range — we explain why just below.
| Application | Users | Machines | Real workstations* | Database types** |
|---|
* Workstations = user-machine combinations actually in service. Leave
“auto” if you don't know them: we then use max(users, machines) as the lower
bound. This is the real counting basis — not the product of users by machines. Official
rule (PCSOFT “Sessions” page): a session is activated for 30 days and
automatically released if unused — in steady state, only genuinely
active workstations count. Developer workstations? A circulating sales answer says they
are excluded, forum testimonies say the opposite: get it confirmed in
writing.
** Number of database types accessed through the PCSOFT connectors (HFSQL, SQL Server,
Oracle, native PostgreSQL… and even SQLite or xBase, which count too). An application
that is 100 % HFSQL = 1; HFSQL + MySQL = 2.
| Estimated sessions (realistic → maximum) | — |
| Year 1 (full price) | — |
| Year 2 (full price) | — |
| Year 3 (full price) | — |
| 3-year commitment total (full price) | — |
| 3-year total with negotiated discount | — |
| After liberation from the PCSOFT DB connectors (stage 3) | 0 € on this dimension*** |
This calculator only sees the surface. The dependency audit — fixed price, on documents, with no access to your production data — gives you the facts; then each stage is decided separately and has its own value.
A map of your database and its access points, a forecast PCSOFT invoice on your real figures (as a realistic → maximum range), measured exit complexity, and the mechanical replacement rate of your data access. A costed, factual and verifiable report. Fixed price.
Your data migrated to PostgreSQL, your WinDev or WebDev application reconnected as is, with exhaustive verification delivered (counts, checksums, sampling). You no longer depend on HFSQL. Price per database.
Your data access goes through an API — no more PCSOFT DB connectors. A reduction of the tariff exposure surface, and a durable backend that will outlive a possible rewrite of the front end. Package + maintenance.
WinDev and WinDev Mobile are affected by per-session pricing (official “Offers” page). For WebDev, nothing published, nothing priced to date — but the sales-desk answers reported on specialist forums, consistent since late May, already sketch a model. Here is how to read that uncertainty.
One session = one user account × one application × one machine (physical or virtual) × one database type — even SQLite or xBase (definition published by PCSOFT). Sessions are activated for 30 days and automatically released if unused. Last displayed list price: 290 € excl. VAT/session/year (removed from the site in mid-July 2026 — quote-only since). The circulating 3-year commitment offer: 75 € in year 1, 100 € in year 2, 225 € in year 3. The fate of developer workstations remains contradictory across sources.
No priced decision yet, but the first elements circulating sketch a distinct model: a fixed part computed on the server (number of cores and GB of RAM) and a variable part based on the number of HTTP requests per day, averaged over a month. In other words: exemption was never the plan. Traffic-based billing tracks your audience, not the value you get from it — and migrating to WebDev to escape sessions is not a strategy.
The WebDev uncertainty doesn't change the underlying logic: it is the dependency on PCSOFT connectors and runtime that exposes you to the grid, whatever the product. Moving the data out (stage 2) then the data access (stage 3) protects you in every scenario — WebDev exempt, WebDev billed, or the grid changed yet again.
A « WAS » offer document (WEBDEV Application Server) was passed to us. This is a third-party testimony from a source who wishes to remain anonymous : it is not an official PC SOFT answer and these figures are unconfirmed. They do, however, give the first priced view of the « per-server » model : billing by number of cores and RAM, unlimited number of applications. The calculation runs entirely in your browser — no data is sent.
Prices pre-filled with the « progressive » 3-year commitment grid from the document (year 1 → year 3). Reported full price : €5,990 per core and €990 per GB of RAM. Edit freely.
| Year 1 | — |
| Year 2 | — |
| Year 3 (full price reached) | — |
| Total server cost over 3 years | — |
| Benchmark : the same capacity at full price × 3 years | — |
PCSOFT charges WinDev and WinDev Mobile applications per session. Official definition (PCSOFT “Sessions” page): one session = 1 user account (OS sense) × 1 machine (physical or virtual) × 1 application × 1 database type accessed through the PCSOFT connectors. Sessions are activated for 30 days and automatically released when no longer used. Last displayed list price: 290 € excl. VAT per session per year (recorded on 10 July 2026 on the “Offers” page; the price was removed from the site in mid-July 2026, pricing is now quote-only — the page retains bundles with sessions included and an “Early Adopter” discount limited to the first year). A 3-year commitment offer is also circulating: 75 € excl. VAT in year one, 100 € in year two, 225 € in year three — a threefold increase over three years, on a scope that grows mechanically with your installed base.
It depends on the number of workstations actually in use (real user-machine combinations) and the number of database types accessed, not on the product of users by machines. Our calculator above gives a range — from a realistic estimate to a theoretical maximum — projected over the three years of the commitment. As conditions remain negotiated case by case, these amounts are exposure estimates, never certain invoices.
No priced decision to date, but WebDev will not stay free: the first elements circulating (July 2026, no figures) sketch a distinct model — a fixed part computed on the server (number of cores and GB of RAM) and a variable part based on the number of HTTP requests per day, averaged over a month. Migrating to WebDev to escape sessions is therefore not a strategy: you change the meter, not the dependency. Traffic-based billing also raises its own questions (do crawlers count? what does a traffic spike cost?). Our staged approach protects you in every scenario, because it reduces the dependency itself, not just today's invoice.
Not publicly settled. A circulating sales answer (July 2026) says developer workstations are not counted; testimonies on specialist forums claim the opposite. In the absence of a rule published by PCSOFT, get this point confirmed in writing before any commitment — exactly the kind of grey area a dependency audit documents for your file.
No. We don't liberate by rewriting, we proceed in stages: a costed dependency audit, then the migration of the data from HFSQL to PostgreSQL, then runtime liberation of the data access through an API. Your WLanguage business code — your real value — is preserved at every step.
It is stage 3 (runtime liberation) that acts on the invoice: when an application no longer accesses any database through the PCSOFT connectors but goes through an API, it no longer exposes the “database type” dimension of the grid. This is a reduction of the exposure surface — not a guarantee, as the grid remains opaque — and a backend that will outlive a possible rewrite of the front end.
No. The audit is done on documents, from an export of the structure of your database and your application landscape — without any access to your production data. You receive a costed, factual and verifiable report, at a fixed price. Reply within 48 hours.
That's exactly why you should request the dependency audit. Reply within 48 h.
Request a dependency audit Chat on WhatsAppWhatsApp: free and instant, including from the European Union or Switzerland.
