Local CLI
Run the MIT-licensed engine locally or in CI and keep execution inside your environment.
Read the getting-started guideStart with the open-source CLI, add a hosted workspace, or evaluate Fendix with a managed pilot.
Each path uses the same decision model: evidence, coverage and policy remain visible instead of being reduced to a scan count.
Run the MIT-licensed engine locally or in CI and keep execution inside your environment.
Read the getting-started guideAdd shared scan history, scheduled scans, team workflows and credentials for supported integrations, according to the selected plan.
Compare hosted plansEvaluate one repository and, where applicable, one staging API with a reviewed decision record and clear next step.
See the 14-day pilotEvery plan, Free included, makes the same deterministic release decision — PASS, WARN, BLOCK or INCOMPLETE — with its reasons and coverage. Plans differ in team size, history, integrations and capacity.
Evaluation and personal projects.
Workspace and evidence
Capacity
Optional AI assistance (never used in the release decision)
Individual developers shipping production APIs.
Workspace and evidence
Capacity
Optional AI assistance (never used in the release decision)
Development teams and growing companies.
Workspace and evidence
Capacity
Optional AI assistance (never used in the release decision)
Organizations with custom deployment and contracting needs.
Workspace and evidence
Capacity
Optional AI assistance (never used in the release decision)
Paid plans are enabled on request, not through self-service checkout: send a request and the Fendix team confirms the plan with you before enabling it.
AI credits apply to optional agent-assisted work. Deterministic release policy does not depend on an AI recommendation. The configured model provider receives the messages and scan context that work involves; read how that data is handled in the Trust center before using these features.