Hands-on when we can get in
We sign up, complete a real job in the product, and score what actually happens: setup, core features, edge cases, exports, integrations, and failure modes. Launch posts do not count.
How we review
How we review. Tested or researched.
We test the product when we have access. When we do not, we run deep research and aggregate the public record. Sponsored work is labeled. A payment does not change the verdict.
Last updated
Two paths
Hands-on when the product is accessible.
Not every product gives us a usable login. We still publish. Each review says which path it took, and a research review does not pretend we opened a product we could not log into.
Deep research when we cannot
No usable login? We aggregate what is public online: official docs, pricing, changelogs, privacy and security pages, public benchmarks, comparable tools, and other published reporting. The page says the review is research-based.
Commitment
A payment does not change the verdict.
Reviews exist to help you decide whether a tool fits the job. The site is funded through clearly labeled sponsored articles and reviews, relevant paid link placements, and affiliate commissions where those are disclosed. Those relationships do not change the verdict or the ranking. The full commercial rules are in the Editorial Policy.
Process
Five steps, same standard.
1. Scope the job
We define the use case, who the tool is for, and which products it competes with. That scope decides what a fair test, or a fair research pass, has to cover.
2. Test, or research
If we can get in, we run the workflow in the product. If we cannot, we aggregate docs, pricing, benchmarks, and other public reporting. We do not imply we used a product we could not log into.
3. Score and structure
We score only what the evidence supports. Hands-on reviews can judge ease of use and failure modes. Research reviews stick to documented behavior, pricing, and positioning. Every review still gets pros, cons, a best-for audience, and a plain-language verdict.
4. Verify and publish
Pricing, claims, and screenshots are re-checked close to publish. Sponsored work is labeled. A Verified badge appears only when the page has a recorded last-verified date and matches this methodology.
5. Revisit and update
Major product changes trigger a revisit. Update dates and last-verified dates change only when the tool is actually re-checked, not on every build.
Scoring
1 to 5, only where the evidence reaches.
When a review includes numeric scores, they are a judgment on a 1–5 scale at the time of evaluation. We do not invent a score for a criterion we could not judge. Research-based reviews may omit ease-of-use or reliability scores.
- FeaturesDoes the tool deliver the core jobs it promises for its category? Judged from use when we have access, and from documented behavior when we do not.
- Ease of useTime to first value, UI clarity, and learning curve. Scored only when we ran the product. Research reviews describe documented UX, not a fake walkthrough.
- Value for moneyPricing transparency, free-tier usefulness, and cost relative to alternatives, from public pricing and, when we have access, what you actually get.
- Support and docsDocumentation quality, support channels, and how reliably the vendor ships updates.
- Trust and safetyData-handling disclosures, export options, and operational reliability where we can test it.
Sponsored reviews
Payment funds the review. It does not change the verdict.
- The sponsor provides a factual product brief, and access when they want a tested review.
- With access, we run the same workflows as other reviews. Without it, we aggregate the public record and say so on the page.
- AIUnpacker writes the score when the evidence supports one, plus pros, cons, limitations, and the verdict.
- The sponsor may identify factual errors once.
- AIUnpacker makes the final decision and publishes with a Sponsored label.
Current packages and pricing: Work with us.
Verified
What "Verified" means.
A Verified badge means key claims — pricing, core features, and public product positioning — were re-checked against this methodology, and the page records a lastVerified date.
It is not a guarantee of uptime, vendor honesty, or fit for your job. It is not a security audit or a legal compliance certificate. A page without a verification date is editorial content without that re-check stamp.
Sources
Cite the public record.
Factual claims about pricing, model capabilities, benchmarks, and legal constraints should cite primary sources: vendor docs, official blogs, and standards bodies. That matters most on research-based reviews, where the public record is the test. Opinions, workflow tips, and prompt examples are editorial and may not need an outside citation.
Corrections
Send the error.
Found a mistake? Email contact@aiunpacker.com. Material corrections update the page and its modified date. Scores are not rewritten in silence to make a product look better.