Editorial policy

How Bitpute produces, checks, and corrects everything you read here — and where the numbers come from.

How the numbers themselves are produced: the calculation methodology documents every formula, and why Bitpute exists explains the problem it solves.

1What we publish

Two kinds of content. Computed figures — VRAM, fit, speed and cost — are derived from published formulas by a single calculation engine; the full derivation is on the methodology page. Explanatory writing — the concept guides and model notes — puts those numbers in context. We do not publish benchmark results we did not run, or numbers we cannot derive from first principles. Where a figure is an estimate rather than a measurement, we say so.

2Where the data comes from

Model specifications (parameter counts, layers, attention configuration, native context) are taken from each model's official card and config.json. GPU specifications (VRAM, memory bandwidth, TDP) come from manufacturer datasheets. Prices are indicative and move constantly — we show them to compare orders of magnitude, not to quote a checkout total. Full source list is in the references.

3How numbers are verified

Rather than a single named reviewer signing off on prose, every published figure is checked mechanically. An automated parity test asserts that the numbers on all 500+ pages match the reference calculation engine to within 0.01 GB, across models from 0.1B to 671B, and it runs on every change to a formula or constant. Every input constant is traceable to a primary source — manufacturer datasheets for GPU specifications and each model’s published card for model specifications — all cited on the methodology page. Where a figure cannot be verified from a primary source, the page says so rather than estimating.

4Use of AI

Some explanatory copy is drafted with AI assistance and reviewed by the maintainer before publishing. The numbers are never generated by a language model — they are computed by the deterministic engine described in the methodology. We mention this because it is the whole point: a calculator you can check beats a paragraph you have to trust.

5Corrections

Found an error, or have a better source for a constant? Tell us. We would rather fix a number than defend it. Material fixes are logged in the changelog so you can see what changed and when.

6Independence & funding

Bitpute is an independent project and carries no display advertising. Links to cloud GPU providers are provided for reference; if any becomes a paid or affiliate arrangement, it will be disclosed here and on the relevant page.

7Who makes this

See About Bitpute for who builds and maintains the site and why it exists.