Methodology & Research Standards

Selection criteria

Shipped Tools evaluates software based on practical utility for developers building websites and web apps. We prioritize tools with stable public documentation, active maintenance, clear pricing models, and standard web interoperability. We deliberately exclude vaporware, abandoned repositories, and products that obscure basic operational limits.

Profile requirements

Before any tool qualifies for a standalone profile page, it must meet these research criteria:

• Two sourced strengths: Concrete capabilities verified directly against official vendor documentation.
• Two sourced tradeoffs: Meaningful limitations, platform lock-in considerations, or architectural caveats verified from primary vendor sources.
• Documentation links: Direct links to official technical documentation and pricing resources.
• Checked dates: Every claim includes a timestamp indicating when the primary documentation was retrieved and verified.

If a tool cannot be substantiated with primary documentation for both its strengths and its trade-offs, it remains in the general index rather than receiving a dedicated profile.

How sources and dates work

We do not rely on memory, marketing summaries, affiliate roundups, or third-party review aggregators. Every factual claim is verified using primary vendor documentation, pricing schedules, or official code repositories. Developer tools change often, so each claim records a verification date. Readers can inspect the exact primary source behind any statement to confirm whether platform details have changed.

What tested means

When a guide or stack is marked as tested, that means we personally installed the packages, configured the code, and executed the build process locally. We never claim a tool was tested in production or deployed to a live cloud environment unless we actually ran that specific deployment step. If a guide step involves manual infrastructure setup, such as external DNS configuration or live payment webhooks, we explicitly state that the step was not executed during testing.

Refresh practice

Software platforms frequently revise pricing tiers, rename API methods, and restructure feature plans. Before publishing each directory edition, our maintainers re-check source documentation across existing profiles and guides. Any dead links, superseded documentation references, or outdated feature descriptions are updated or removed.

Conflicts of interest

Editorial work must stay separate from commercial incentives. Directory placement cannot be purchased, and vendor sponsorships do not influence tool evaluations, stack selections, or comparison conclusions. If commercial relationships are established in the future, they will be transparently disclosed without altering editorial assessments. Corrections can be submitted via our GitHub issue tracker.