Editorial policy

Sourcing

Every item we publish links to a primary source — a vendor changelog, release notes, an official announcement or a product listing. We summarise in our own words and quote only briefly, with attribution. We do not republish other people's articles, and we do not present someone else's reporting as our own.

Use of AI

Research and first-draft summarisation are AI-assisted. Specifically: an automated pipeline collects candidate releases from public feeds and drafts a short summary of each.

What is not automated: which items are worth covering, the “why it matters” judgment attached to each one, and the analysis in longer pieces. Those are editorial decisions. Drafts are reviewed before publication, and anything the pipeline cannot summarise accurately from the source is dropped rather than guessed at.

How it is written

Coverage is written in the register of a technical content writer rather than a tech journalist. In practice that means naming versions, limits, units and prices wherever the source states them; describing what a product now does rather than how anyone feels about it; and attributing vendor claims as vendor claims. Where a source is too thin to summarise precisely, the item is dropped rather than padded with adjectives.

How articles are checked

Longer articles are written from the primary announcement plus, where one exists, the practitioner discussion around it. Facts come only from primary sources; community comment informs the analysis and is attributed as comment, never presented as fact.

Every draft is then read back against its sources and rejected if it contains claims they do not support — particularly comparative or trade-off claims that sound plausible but were never stated. Drafts that drop a limitation or caveat the source gave are rejected too, because that caveat is usually the most useful sentence for a reader making a decision. Source links are assembled from the pages actually retrieved, never written by a model, so a citation cannot be invented.

Accuracy and corrections

We get things wrong sometimes. When we do, we fix the page, note what changed, and update the modified date. Email hello@productnews.tech with a correction and it will be handled — there is no form to fill in and no delay for a response.

We do not silently delete or rewrite published claims. If a substantive error is corrected, the correction is visible on the page.

Independence and disclosure

No vendor pays for coverage, placement or a favourable verdict, and no coverage decision is affected by whether a company has an affiliate programme.

Some links on comparison and alternatives pages are affiliate links, meaning we may earn a commission if you sign up. Those links are disclosed on the pages where they appear. The site also carries display advertising, which is sold programmatically — advertisers have no involvement in or advance sight of editorial content.

What we cover

Releases that change what a product does for its users. We generally skip funding announcements, personnel news, marketing rebrands and minor bug-fix releases, unless they have a direct practical consequence for people using the tool.