Pricing and packaging

Pricing for AnswerLens is open-source, BYOK, and artifact-first.

AnswerLens is not a hosted dashboard with seat-based licensing. The code, Pages docs, example reports, and release assets are public. The only variable costs appear when you choose to run eval-mode benchmarking with your own provider account or consume your own GitHub runner minutes.

Open surfaces

What costs $0

The open-source repository, Pages site, and live demo report.
The CLI workflow for a basic `audit` run with no provider key.
The reusable GitHub Action contract and release asset downloads.
Local fixture demos, report bundles, and static review artifacts.

BYOK model

Where variable cost appears

Surface	Cost model	Notes
CLI audit	$0 provider cost	Basic `audit` runs do not require provider API keys.
Eval runs	Bring your own provider bill	OpenAI and Perplexity usage stays in your own account.
GitHub Action	Your repository runner minutes	The Action keeps the same artifact contract used by local runs.
Release assets and Pages	$0 to download	Demo bundles, the compiled site, and docs stay publicly accessible.

How teams adopt

Packaging choices

Teams usually start with the live demo report, move to one local real-site audit, and then wire the same output contract into the GitHub Action. The package and release surfaces are intentionally simple:

@answerlens/cli for CLI installs and dry-run packaging.
The root GitHub Action for pull-request and workflow-based adoption.
Release assets for tarballs, demo bundles, and the compiled site bundle.
Pages as the public proof surface for docs, examples, playbooks, pricing, and trust.

That model keeps pricing legible: open source for the product surface, BYOK for optional eval usage, and no hosted AnswerLens control plane fee today.

Built by YSCJRH from repo-native docs, releases, and artifacts. No consumer AI UI scraping. No ranking promises.