TimesFM or Chronos: which forecasting model to pick

Both models forecast a time series without training on your data and run on a CPU. Google's TimesFM is newer: version 3.0 shipped in 2026-08, but that is the one under a non-commercial license, while versions 1.0 to 2.5 stay open for business under Apache 2.0. Amazon's Chronos is Apache 2.0 across the whole line, and the latest Chronos-2 from 2025-10 accounts for external factors: prices, promotions, weather. Chronos sizes start at 8M, so it fits a modest server, while TimesFM starts at 200M. The catalog lists both for retail, manufacturing and finance; the choice depends on whether you need external factors and how much the newest version matters.

Comparison based on catalog data

ParameterTimesFMChronos
CategoryForecastingForecasting
DeveloperGoogle, USAAmazon, USA
ReleasesMay 2024 – Aug 2026Mar 2024 – Oct 2025
Sizes200M – 500M8M – 710M
HardwareLaptop, 1 GPULaptop
Commercial useCommercial use with conditionsCommercial use allowed
LicenseVersions 1.0 to 2.5: Apache 2.0; TimesFM 3.0: non-commercial licenseApache 2.0
RussianNot applicableNot applicable
OllamaNoNo
Without GPUYesYes
Tasks
  • Sales and demand forecasting
  • Purchase and inventory planning
  • Load and traffic forecasting
  • Demand forecasting with promotions and prices
  • Inventory planning
  • Forecasting revenue and customer flow

Choose TimesFM if

  • You want the newest line: TimesFM 3.0 is dated 2026-08
  • The work is research, where the non-commercial 3.0 license is fine
  • Commercial use of versions 1.0 to 2.5 under Apache 2.0 is enough for you
TimesFM

Choose Chronos if

  • Forecasts must account for promotions, prices and weather: Chronos-2 does
  • You want the whole line under Apache 2.0 with no per-version caveats
  • Resources are tight: Chronos has models from 8M
Chronos

Other comparisons

Need a model for your task?

An open model can run on your own server: data stays in-house, there is no per-request fee, and the model can be fine-tuned on your documents.

  1. SelectThe model and size for your task and hardware budget
  2. DeployOn your server or in a closed network, with an API
  3. Fine-tuneOn your data, or connect a knowledge base
  4. IntegrateInto your CRM, ERP, bot, website or team chat
Discuss deployment