Last updated: October 2026
This policy explains how Web3 Infra Guide chooses topics, gathers facts, keeps coverage independent and fixes mistakes. It applies to every article, guide, comparison and news item on the site.
Our Editorial Principles
- Accuracy first. Every factual claim about pricing, features, chain support, certifications, incidents or funding is checked against a primary source before publication.
- Independence. Vendors, protocols and sponsors never review, edit or approve our coverage before it is published.
- Usefulness. Each article should leave a reader with a clearer buying or build decision, including who a product is not right for.
- Transparency. We show our sources, date our facts and say what we could not verify.
Sourcing
We prefer primary sources: vendor documentation, pricing pages, terms of service, status and incident pages, changelogs, published audit reports, certification registries, regulatory filings and official statements. Secondary sources such as news reports are used only when a primary source is not available, and we name them. We link to sources so readers can check them. Statistics are attributed to the organization that produced them, with the date of the data.
Pricing and Feature Claims
Infrastructure pricing changes often. Pricing, plan limits and feature claims are checked on the vendor’s own pages at the time of writing and dated in the article. If a vendor publishes no price, we say “custom pricing” rather than guess. When we compare products, we compare like with like and explain the unit each vendor uses, such as requests, compute units or credits.
Independence From Vendors and Tokens
No vendor, protocol, foundation or token issuer can pay to change a ranking, a verdict or the wording of an article. Staff and contributors may not accept tokens, airdrops, allocations or gifts connected to coverage. Commercial relationships, if any, are labeled as described in our Advertising & Sponsorship Disclosure.
Desk Bylines and Review
Articles run under openly labeled desk bylines, which are team labels and not individual authors. Each desk is staffed by the Web3 Infra Guide editorial team. Every article is edited by a human editor before it is published. When an outside expert reviews a piece, we name them and their role, and we never invent experts, credentials or quotes. You can read about each desk on our About page.
Use of AI Tools
We use AI tools to help with research, summarizing long documentation, drafting outlines, checking grammar and producing illustrations. AI tools do not decide our rankings or verdicts, and AI output is never published without human review and fact-checking against primary sources. Featured illustrations are AI-assisted artwork; product screenshots are real captures of vendor pages and are never generated or altered beyond cropping.
Testing and Rankings
Our ranking criteria and the limits of our testing are explained on our How We Test page.
Corrections and Updates
If we get something wrong, we fix it. Material corrections are noted at the end of the article with the date of the change. Routine updates, such as a new price or a new supported chain, update the “Last updated” date at the top of the article. To report an error, email editorial@web3infraguide.com with “Correction” in the subject line.
Vendor Requests
Vendors may send us corrections to factual information about their own products, with a link to a public source. We review every request, but we do not change opinions, rankings or verdicts on request, and we do not remove accurate criticism.
Not Financial Advice
Our content is about infrastructure software and services. It is not investment, legal, tax or financial advice. See our Disclaimer.