Editorial Standards
Last updated: August 27, 2026
Stackwrite is a one-person publication. That is worth saying up front, because it shapes everything below: we cover a narrow set of things properly rather than a wide set badly, and the person who takes the money is the person who writes the words. The only workable answer to that is to be explicit about the rules and to publish our mistakes. This page is both.
What we actually publish
We write one kind of page well: reference pages with concrete, checkable numbers — real rate limits, real free-tier ceilings, real prices — and first-hand build reports about shipping software. If a question can be answered accurately by a vendor's own documentation, we would rather link to it than restate it. We add value where no single vendor can: comparing what several of them actually give you.
Our scope is tools for people who build software — AI and developer tools, infrastructure, developer productivity, and iOS/Android apps. Consumer web apps, lifestyle tools, and marketing products are outside it, and submissions for them are not published at any price.
How tools get picked
- Because a question exists. We track the questions developers actually ask about tool limits and pricing, and write the page that answers them with numbers.
- Because we can verify it. If we cannot check a claim ourselves, it does not go in.
- Not because of traffic potential alone. Publishing to fill a schedule is what produced the pages we had to retire in August 2026.
How we verify numbers
- Figures are taken from the vendor's own pricing or documentation pages, or measured directly, and checked by hand before publication.
- Every reference page carries a visible last-updated date. If it looks stale, it probably is — tell us.
- Pricing and limits pages are re-verified on a monthly cycle, whether or not anything changed. Maintenance is the point; an unmaintained numbers page is worse than none.
- We say when a number could not be confirmed, rather than rounding it into something that reads better.
Money, and what it does not buy
We sell two things: a Featured listing ($39.00) and a Sponsored article ($149.00). Here is exactly what that means.
- Payment buys placement and our time. It does not buy a verdict. We keep full editorial control of what is written, including the trade-offs and the parts a vendor would rather we left out.
- Sponsored articles are labelled as sponsored, on the page, where a reader sees it before reading — not in a footer.
- Paying does not change anyone else's coverage. A sponsor does not get moved up, and a competitor does not get moved down or removed.
- We can say no, and we refund rejected paid submissions in full. See our Refund Policy.
- No pay-to-remove. We will correct anything inaccurate for free, and we will not delete accurate criticism for money.
- Free editorial review is genuinely free and carries no obligation, no timeline, and no guarantee of coverage.
Affiliate links and other conflicts
- Where we use affiliate links, they never change a ranking, a recommendation, or a number. If a tool with no affiliate program is the better answer, it wins.
- The site is run by Hirak Banerjee, who also builds and sells his own apps. His products do not appear in our "best of" roundups or comparison tables, disclosed or not — a publication ranking its owner's own product is not a ranking. They appear only in first-hand build reports, where the subject is what was learned, and the interest is obvious on its face.
Corrections policy
When we get something wrong, we fix the page, note what changed, and move the updated date. If the error is fundamental rather than a detail, we retire the page instead of patching it — a wrong page that stays reachable keeps being wrong, and search engines and AI assistants keep quoting it. We do not silently edit a claim and pretend it was always that way.
Found an error? Email hello@stackwrite.com. Corrections from vendors about their own products are welcome and are not treated as a commercial conversation — you do not have to buy anything to have us fix a number about you.
Corrections we have made
This list is public because a corrections policy nobody has ever invoked proves nothing.
2026-08-16
Our automated comparison pages carried wrong facts about a vendor.
A PlanetScale employee publicly pointed out that our Neon vs PlanetScale comparison was, in their words, "all kinds of wrong" — it described PlanetScale as MySQL-only at $39/month with no free tier, when PlanetScale had shipped Postgres and single-node plans from $5/month. Some pages also rendered unfinished placeholder text to readers.
What we did: We retired all 395 automatically generated comparison and alternatives pages the same day. They now return HTTP 410 Gone rather than being quietly hidden, because a page that is wrong should stop being retrievable, not just stop being indexed. We no longer generate comparison pages from a data file. Comparisons are written by hand or not at all.
2026-08-05
An app roundup listed products we could not verify.
Our April 2026 iOS app roundup listed a product twice as two different apps. On review we could not verify that every app in it existed as described.
What we did: The article was deleted rather than patched. We do not keep a page alive when we cannot stand behind its basic facts.
2026-08-05
GitHub star counts were months out of date.
Several articles quoted star counts that had drifted badly from reality — one project was listed at "70K+" when it had passed 199K.
What we did: Star counts are now refreshed from the GitHub API on a monthly schedule, and the article's updated date moves when they change.
Questions
Anything about these standards, a specific article, or a listing: hello@stackwrite.com. See also our Terms, Privacy Policy, and Refund Policy.