Nothing here can be bought
Most tool directories monetize the listing itself — paid placement, paid “verified” badges, bid-ranked positions, or analyst access economies. This site is built on the opposite premise: the data is the product, and its value depends on no one being able to influence it. This page is the standing policy that makes that checkable.
Last reviewed · permanent policy · see also the methodology and inclusion criteria
The no-pay-to-play policy
- No listing fees. No product has ever paid to be listed, and none can.
- No sponsored placement or ranking. Position on any page is determined by data and written rules, never by spend.
- No paid badges or “verified” programs. A verification date on a record reflects our review, not a vendor purchase.
- No advertising, no affiliate links, no referral revenue from any listed vendor.
- No vendor influence on verdicts. When editorial assessments ship, they will carry a dated rationale and the same no-vendor-influence rule.
How the project is funded and run
enterpriseai.tools is an open-source project (MIT-licensed, public repository) maintained by Tiberiu Arva and run on static hosting at negligible cost. There is no revenue model: no subscriptions, no ads, no paid tiers, no sponsored content. That independence is deliberate — it removes every channel through which a vendor could pay to shape the data.
Zero tracking
- No analytics and no tracking scripts — we cannot see who you are, and we do not want to.
- No cookies, no email capture, no lead funnel. Subscribing means RSS/Atom or the calendar feed, which identify nobody.
- No runtime third-party requests: pages are static files, and nothing phones home when you read them.
Corrections: resolved by sources, not by spend
- Open a public issue in the repository naming the record, the field, the value you believe is wrong, and the primary source that supports the correction.
- Corrections are resolved by comparing sources, in public, in the issue thread — never by who is asking or what they spend.
- License corrections follow a stricter path: the upstream LICENSE file is re-read and the record changes only after verification, with the change logged in the public feed.
- Vendors are welcome to correct facts about their own products this way. Facts can be corrected; position cannot be bought.
Start a correction in the public repository.
Accountability
The dataset is edited by a named maintainer — Tiberiu Arva — through a regulated-enterprise delivery lens, and every edit is attributable in the public git history. If this policy is ever violated, the evidence would be public; that is intentional.