Plans & standards: what each plan licenses
✅ Stable — The plan→standards map and the plan page described here are the ones running today. Prices are reference prices: contracting is assisted (contract or invoice), there is no self-serve payment gateway.
The froga engine is Apache-2.0 and always will be. What is licensed per plan are the paid standards: which normative catalogs your organisation can declare on its systems, and which ones the signed entitlement (.froga/entitlement.json) the engine reads can be issued for. The pricing unit is the governed AI system per year, not engine usage.
Two standards are free on every plan — the open-core frontier: ISO/IEC 23894 (AI risk management) and ISO/IEC 42001 (AI management system). ISO good practice, real signed evidence, zero cost. Everything else is paid, and which plan each standard lands in is what this page describes.
Which standard lands in which plan
Section titled “Which standard lands in which plan”The ladder is cumulative: each plan includes everything from the previous one, plus its own. Prices are reference prices, per governed system/year.
| Plan | Reference price | Adds (over the previous one) |
|---|---|---|
| Free | €0 | ISO/IEC 23894 (AI risk management) and ISO/IEC 42001 (AI management system) — the free standards. |
| Starter | €149 | The prEN presumption stack: prEN 18228 (risk management, AI Act Art. 9) and prEN 18286 (quality management system, Art. 17) — the presumption of conformity the law demands of you. |
| Pro | €449 | The full horizontal package: the remaining prENs (prEN 18282 cybersecurity Art. 15(5), prEN 18283 bias Art. 10, prEN 18229-1), the EU AI Act as a catalog, the GDPR, and the supporting technical ISOs (Croissant-RAI, ISO/IEC 5259-2/-3 data quality, ISO/IEC TR 24027 bias, ISO 24029-2 robustness, ISO 27001, ISO/IEC 12792 transparency, ISO 42105 human oversight, ISO 8200). Plus the two active verticals: medtech (MDR + ISO 14971) and finance (DORA). |
| Enterprise | €1,500+ | The remaining sectorials and national law: NIS2, the Spanish Workers’ Statute (RDL 2/2015, Art. 64.4.d) and Law 15/2022 (equal treatment). National normative layers are Enterprise segmentation. |
Beyond the standards, each plan carries its capabilities and limits: governed systems (1 / 5 / 25 / unlimited), the Annex IV as PDF (from Starter), the DORA register as CSV and the MDR documentation (from Pro), the retention vault and auditor seats (0 / 1 / 5 / 25). All of it is shown, plan by plan, on the plan page itself.
The Settings → Plan page
Section titled “The Settings → Plan page”Under Settings → Plan (/[org]/settings/plan) your organisation sees, unambiguously:
- The current plan and where it comes from (contract, or the default free plan), the matrix of enabled capabilities, the governed systems consumed against the limit, and the included KAG evaluations.
- The four-plan comparison, derived from the same plan→standards map the server enforces (there are no two lists that could diverge): each plan shows “everything in X, plus…” with its standards named, your current plan highlighted, and the standards already declared by your organisation’s systems marked “in use”.
- The assisted-sale upgrade CTA: “Contact to upgrade to Plan” opens an email to hola@venturalitica.ai with your organisation, your current plan and the target plan. There is no payment gateway: contracting closes via contract or invoice, and the plan is activated on the platform once it does.
What happens when you declare a standard outside your plan
Section titled “What happens when you declare a standard outside your plan”Monetisation is fail-closed at the moment of blocking, not an after-the-fact discovery:
- When declaring standards on a system (the portal’s standards-declaration mission), if the selection includes a standard your plan does not license, the declaration is blocked with an error naming the minimum plan that includes it (“requires the Starter/Pro/Enterprise plan or higher”) and a direct link — “See the plan and included standards” — to Settings → Plan.
- When issuing the entitlement (
froga entitlement syncfrom your machine or CI), the same server-side rule answers 403 with the same readable message: the issuer does not sign entitlements for out-of-plan standards. - Nothing opens without a valid plan: an unknown plan is treated as free, and a paid standard the map does not assign to any plan is not licensable on any of them (the error says so — check the identifier or contact support). The paywall never fails open.
The issued entitlement is a signed file, not DRM: .froga/entitlement.json travels in your repository, the engine and verifiers check it against the Venturalítica issuer’s public key, and your evidence remains yours. If a tender requires blocking clauses from a paid standard, the tender gate verifies that same file.