We do not publish a card if critical fields are missing.
Methodology
Editorial methodology
WebStackRadar helps readers choose software stacks before paying. In the MVP, evaluation is manual, criteria are documented, and recommendations are separated from price and affiliate incentives.
A recommendation must explain when to use a tool and when to avoid it.
Affiliate availability is separated from editorial judgment.
What WebStackRadar is
WebStackRadar is an editorial decision engine for comparing software tools and stacks by fit, real cost, risk and use case. It is not an automated database or a promotions site.
What we evaluate
- Use-case fit: who it is for and who it is not for.
- Real total cost: minimum useful plan, limits, renewals and possible add-ons.
- Compatibility: how it fits with the rest of the stack.
- Risk: lock-in, dependency, migration, support and maintenance.
- Alternatives: when another category may be more sensible.
What we do not do
- We do not sell paid rankings in the MVP.
- We do not publish invented user reviews or scores without methodology.
- We do not use scraping or automatic price tracking yet.
- We do not promise legal, tax or financial advice.
How we decide to publish a card
A card should only be published when critical fields are complete: use case, limits, verifiable cost, main risks, recommendation conditions and enough sources or signals. If those fields are missing, the card stays pending.
What “use it if” means
“Use it if” describes the scenario where a tool appears reasonable by cost, friction, compatibility and project maturity. It does not mean the tool is universally best.
What “not recommended if” means
“Not recommended if” marks conditions where cost, complexity, lock-in or maintenance may outweigh the expected benefit.
Pros, cons and prices
Pros and cons should appear together and with context. Prices are reviewed manually, require a verification date and should link to the official source when relevant.
Affiliate links separated
Commission does not decide a recommendation. A tool without an affiliate program can win if it fits better.
Critical fields first
If verifiable price, limits, use case or risks are missing, the card should not be presented as a recommendation.
Manual in the MVP
Evaluations, price checks and editorial decisions are manual until WebStackRadar has its own infrastructure.
Context before ranking
The result depends on the scenario. WebStackRadar avoids absolute winners without explaining who they apply to.