Alex Pan

I write and test every guide on this site. Not a team, not a content farm — one person with free accounts and a notebook of what broke.

What I do here

I take an AI tool, use it the way a beginner would, and write down what actually happens: what the free plan allows, which button is where, what error message shows up when you hit a limit, and how long a job really takes. Then I check the vendor's own documentation for the numbers I cannot see from the outside, like token prices or plan limits.

Where the two disagree — and they often do — I show both numbers and say which one I could verify. The data page tracks the clearest cases, such as the free-plan figure that differs between one region's site and another.

How I test

What I will not do

Where the numbers come from

Prices, limits and feature lists come from the vendor's own pages: pricing pages, help centres, developer documentation and official release notes. Each article ends with a Sources block listing the exact pages used, so you can re-check any figure yourself. Where a number appears only in a third-party blog with no date, I do not use it.

When I get something wrong

Tools ship changes constantly, and free tiers are the first thing to move. If a guide on this site no longer matches what you see on screen, tell me through the contact page and I will re-test and correct the page, with the new check date on it. Corrections are made in place, not buried in a new post.

Start here

If you are new to this, the two pages that explain the method are How we test and About this site. If you want to see the raw figures rather than the guides, go to Our data.