Editorial Policy

This policy describes how StackPipeline content is produced, reviewed and corrected. It exists so readers can audit our process rather than take our word for it.

1. Editorial independence

Editorial decisions are made independently of commercial relationships. Specifically:

• No vendor receives pre-publication review of any article about their product
• No vendor can pay for inclusion, placement or a higher score
• Advertisers have no input into editorial calendars or conclusions
• Writers assign scores before anyone checks whether an affiliate program exists, and are not told commission rates

2. Sourcing standards

Every factual claim must be traceable to one of:

• Primary testing — our own hands-on use, with hours logged on the page
• Vendor documentation — official docs or pricing pages, dated when cited
• Named expert sources — practitioners identified by name and role
• Published research — linked directly to the original, never to a summary

We do not cite competitor articles as sources of fact, and we do not republish vendor marketing claims without independently checking them.

3. Testing requirements

A product cannot be scored unless a member of our team has used it. For reviews, that means a minimum of 20 hours on a paid or full-featured trial plan. Our testing methodology sets out the rubric and weighting.

Where we have not tested a product ourselves, we say so explicitly and do not assign a score.

4. Fact-checking and review

All comparison and review content is fact-checked by a second person before publication. The fact-checker independently verifies:

• Every price against the vendor's live pricing page on the day of review
• Every feature claim against current product documentation
• Every statistic against its cited source
• That pros and cons reflect the testing notes rather than vendor positioning

The fact-checker is named on the page. Articles display a "Fact-checked by" badge only when this review has actually taken place.

5. Update and review cycle

SaaS pricing changes constantly, so published content is not treated as finished:

• Pricing pages and reviews — re-verified every 90 days
• Integration tutorials — re-tested every 180 days, or immediately after a vendor UI change
• Comparisons — re-scored annually, or when a competitor ships a material feature

The "Last updated" and "Verified" dates on each article reflect real review events, not cosmetic edits. We do not bump dates to game freshness signals.

6. Corrections policy

When we get something wrong, we fix it and say so. Substantive corrections — anything affecting a score, price, recommendation or factual claim — are noted at the foot of the article with the date and nature of the change. Typos and formatting fixes are made silently.

Report an error to editorial@stackpipeline.com. We aim to respond within two business days.

7. Use of AI tools

We use AI assistance for research triage, outlining and copy editing. We do not publish AI-generated articles. Specifically:

• Every article is written, edited and signed off by a named human author
• All testing data, scores and screenshots come from actual product use, never generation
• No factual claim enters an article on the authority of a language model
• AI-assisted drafts receive the same fact-checking as any other content

8. Authorship and expertise

Every article carries a named byline with a linked profile listing the author's relevant experience and credentials. We do not use pen names, generic "staff" bylines or fabricated author personas. Writers only cover categories where they have direct operating experience.

9. Conflicts of interest

Contributors must disclose any financial interest, employment history or advisory relationship with a vendor they cover. Where a conflict exists, either the contributor is reassigned or the relationship is disclosed prominently on the article.

10. Sponsored content

We do not currently publish sponsored posts, paid guest articles or link insertions. If we ever do, such content will be labelled "Sponsored" in the page header, excluded from rankings and scored content, and marked with rel="sponsored" on all outbound links.

11. Contact the editorial team

Editorial Director: Priya Raghunathan — editorial@stackpipeline.com