Methodology

How we score every product we rank.

Every number on this site is the output of a documented process. Here's exactly how it works.

Methodology v1.0.6 Last updated May 2026 View version history →
The 0–100 scale

What a GAX score actually means.

Scores represent a weighted composite across five dimensions — not an average of user reviews. A 90+ product genuinely leads its category on capability, pricing honesty, and operational quality. A product scoring below 40 has meaningful gaps that create real operational risk.

90 – 100
Best-in-class
Category leader with no significant weaknesses.
75 – 89
Excellent
Strong across all dimensions; minor gaps only.
60 – 74
Good
Solid choice with some notable trade-offs.
40 – 59
Acceptable
Works for constrained use cases; gaps are real.
0 – 39
Poor
Meaningful deficiencies; proceed with caution.
Score visualisation

Colour bands at a glance.

Every ranking page displays scores alongside colour-coded indicators. The gradient below maps directly to the bands on the left.

0 40 60 75 90 100
Example score indicators
94
Best-in-class
81
Excellent
67
Good
48
Acceptable
31
Poor
Scoring dimensions

Five dimensions. 100 points. No black boxes.

Weights are fixed between quarterly recalculations. The same formula applies to every product in every category.

01
30%

Core capability & performance

How well the product delivers on its core function under real production conditions.

Feature completeness against category baseline
Benchmark performance vs. peer products
Reliability and behaviour under load
API quality, versioning, and stability
02
25%

Pricing transparency & TCO

Whether the true cost of using the product is knowable before signing.

Public pricing availability and clarity
Contract flexibility and exit provisions
Hidden costs and metered overages
Enterprise discount opacity and negotiation norms
03
20%

Developer / operator experience

How fast a competent team can go from zero to production-grade.

Onboarding time to first working integration
Documentation quality and accuracy
CLI and API ergonomics
Debugging tooling and observability hooks
04
15%

Ecosystem & integration depth

How well the product connects to the rest of a modern stack.

Native integrations with tier-one tools
API surface area and coverage
Partner ecosystem maturity
Migration tooling and data portability
05
10%

Operational reliability & support

What happens when something breaks at 2 a.m.

Uptime SLA commitments and historical track record
Incident response time and communication
Support tier quality at standard pricing
Status page transparency and post-mortem culture
Weight distribution
= 100%
Data collection

Four steps from product to published score.

Step 1

Product research

We gather all publicly available information: documentation, pricing pages, changelogs, blog posts, and third-party benchmarks. No NDAs. If it isn't public, it doesn't count.

Step 2

Hands-on evaluation

Where a free tier or trial is available, we run standardised test scenarios against each product. Real usage, real latency, real integration time — not the vendor's demo.

Step 3

Community validation

Practitioner interviews, forum threads, and Reddit signal surface the gaps that don't appear in docs. We weight first-hand operator experience heavily in the DX and reliability dimensions.

Step 4

Score calculation

The weighted formula is applied, producing a raw composite. A second editor peer-reviews the score inputs against the evidence log before any score is published or updated.

Update cadence

Scores don't go stale — by design.

🔄

Quarterly full recalculation

Every score across every product is recalculated from scratch in January, April, July, and October. Products are never grandfathered — a product that was #1 last quarter must earn that position again. No score carries over without fresh evidence.

January April July October

Continuous monitoring

Major product changes — pricing overhauls, significant feature launches, downtime incidents, or public controversy — trigger an out-of-cycle score update. Once triggered, the updated score is published within 30 days of the event, with a timestamped change note on the ranking page.

Out-of-cycle updates published within 30 days of a material change
Score challenges

Disagree with a score? Tell us.

We actively want to be corrected. The process is transparent, time-bound, and publicly logged.

How to submit a challenge

Email methodology@gaxonline.com and include the following three items:

1
The product name
Exact product name and the category page URL where the score appears.
2
The specific criterion
Which of the five dimensions you believe is scored incorrectly and why.
3
Evidence
Links to documentation, pricing pages, public benchmarks, or other verifiable sources.

What happens next

5 business days
We respond to every challenge submission within five business days — whether we agree, disagree, or need more time to investigate.
If the score changes
A correction is published at the top of the ranking page with the timestamp, previous score, new score, and a brief explanation of what changed.
Note: challenges must include verifiable public evidence. We do not accept NDA-gated information or vendor claims as the sole basis for a score change.
methodology@gaxonline.com Response within 5 business days — guaranteed.
Version history

Every change to this document is logged.

Version
Date
Change
v1.0.6 Current
May 2026
Added Bittensor subnet evaluation framework
v1.0.5
Mar 2026
Revised pricing transparency weight from 20% to 25%
v1.0.4
Jan 2026
Added AI agent orchestration sub-criteria
v1.0.0
Sep 2025
Initial methodology published

All scoring weight changes trigger a full recalculation of affected rankings before publication. Questions about a specific version? Email methodology@gaxonline.com.