Projecting signups or revenue forward from a spreadsheet average ignores the pattern the actual data already contains. TimesFM is a pretrained model that takes a numeric time series, feeds, sales, anything with a timestamp, and forecasts it forward without you training anything. TimesFM 3.0 ranks first on three major forecasting benchmarks. Its pretrained weights are restricted to non-commercial use, which the code license alone does not tell you.
By Raj Singh · September 2026 · 32k stars · Rank #1, three benchmarks · 5 min read
A week of signups fed in on the left, a projected week fed out on the right, no manual seasonality tuning required. The same call handles a single series or a multivariate batch with covariates.
3.0 weights are non-commercial only. The code is Apache-2.0, but TimesFM 3.0's pretrained weights carry a separate non-commercial license. Commercial or production use of the default 3.0 checkpoint is explicitly not permitted.
Weights up to 2.5 stay Apache-2.0. If you need this in a commercial product today, install the 2.5 weights, not 3.0. pip install timesfm==1.3.0 reaches the archived 1.0 and 2.0 code if you need those specifically.
No training required to start. It is a pretrained foundation model. Zero-shot forecasting on your own series works out of the box; fine-tuning with LoRA is an optional extra example, not a required step.
Apple Silicon skips PyTorch entirely. pip install timesfm[mlx] runs native MLX inference on a Mac with no PyTorch dependency at all, useful if you want this on a laptop rather than a GPU box.
Licence, in plain English: Apache-2.0 for the code always. For weights: 2.5 and earlier are Apache-2.0 too; 3.0 is non-commercial, non-production only, for now.
Drop your email and unlock the rest: what you need, the install for your platform, which model version to pick for commercial use, and the first real forecast.
One email. No follow-up unless I ship something that fits.
The PyPI install is the fast path. Pick the 2.5 weights explicitly if commercial use matters, since the library defaults to the newest checkpoint otherwise.
The install
The local install path (git clone plus uv pip install -e .[torch]) is worth it only if you plan to read or modify the model code, not for normal use.
Which checkpoint you load is not a performance tuning knob, it is the difference between a model you can ship and one you cannot.
| Setting | Default | Why I change it |
|---|---|---|
| checkpoint_path | TimesFM 3.0 | Non-commercial license. Pin to a 2.5 checkpoint for anything shipping in a paid product. |
| context length | up to 16k on 2.5 | Longer context costs more compute per forecast. Match it to how much real history you actually have, not the maximum. |
The workflow is the same whether you are forecasting signups, revenue, or support ticket volume. The only real variable is how far out you ask it to project.
Google's own use inside BigQuery ML and Connected Sheets is the same model, wrapped for people who would rather write SQL or use a spreadsheet than Python.
checkpoint_path at a 2.5 weight instead before it ships.Model weights download from Hugging Face on first use and cache locally. Nothing here needs a Google Cloud account unless you specifically want the BigQuery ML or Vertex integrations.
One pip install, one checkpoint choice that is really a licence choice, and a spreadsheet average stops being your forecasting method. Pick 2.5 the moment commercial use is on the table.
↑ Unlocks the moment you submit the form above.
I'm Raj Singh, founder of DebtOps.ai and a Claude certified partner. Over the last five years I've managed $25M in ads, built AI solutions for Fortune 100 companies, and installed AI operating systems and AI brains inside small businesses. Everything here is something I've shipped, debugged, or watched a client ship. My goal with AgileSingh is to make you irreplaceable in this AI age.
A forecast is only useful once something acts on it. The AI infrastructure guide covers where a model like this fits into a real product stack instead of a one-off notebook.