Skip to content

FAQ

No. Your code never leaves your machine — DevKit reads your project files locally and answers from them, with no telemetry. The one exception is a Pro licence: on activation the licence key (never your code) is checked once against the Polar licensing API, then DevKit works offline. On this site, the checkout links carry where your visit came from (its utm_ tags, or the referring site), which Polar keeps with the payment; it is remembered for the browser tab only, with no cookie — never who you are.

Not unless you ask it to, with Pro. DevKit reads files, including the installed plugins in node_modules, and follows their code statically: it doesn’t start Strapi, execute a plugin or touch your database. The one exception is Pro’s Config Sync through your Strapi: when you compare, export or import, it loads your project’s Strapi the way config-sync’s own CLI does — on a local development database only.

Both. The version is detected per project, and v4-in-v5 patterns (e.g. strapi.entityService) are flagged.

No Strapi 6 is announced yet — the CMS is on v5, and Strapi’s stated 2026 focus is stabilising v5. DevKit reads your real schema.json and detects the version per project, so it’s built to adapt when v6 lands.

VS Code and its forks — Cursor, Windsurf, Google Antigravity, VSCodium — via the VS Code Marketplace and Open VSX.

Identical behavior for ESM and CommonJS projects, challenged by a JS⇄TS parity test in the engine.

No. DevKit for Strapi is an independent, community-built tool — not affiliated with, endorsed by, or sponsored by Strapi SAS. “Strapi” is a trademark of Strapi SAS, used only to describe compatibility.

Bugs, questions and feature ideas → open an issue on GitHub. A missed magic-string pattern or a v4/v5 quirk is exactly what I want to hear about.

Anything about a Pro licence (key not received, refund, billing) → email pro@paulrichez.fr — that stays private.