SupaKeeper Plain comparisons of AI coding tools

How to compare provider release schedules for AI procurement specialists in 2026

Learn how AI procurement specialists can compare provider release schedules, check each date against a source, and choose a tool that fits the job.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, the makers of AgentHydra, Copilot AI Productivity Suite, Codex Forecast and Model Odds, which are compared here alongside other tools.

To compare provider release schedules, gather the dated announcements you trust, keep a source for each date, and compare them with estimates that show their own spread. Model Odds is one option: it ranks every Anthropic and OpenAI model family by its estimated chance of a release within 30 days [1].

OptionWhat it doesWhat to check
Model OddsRanks every Anthropic and OpenAI model family by its estimated chance of a release within 30 days [1]Check that the two companies you compare are the ones it lists, and whether its 30-day window fits your decision timing.
Provider announcement pagesLets you read each provider's own announcements and dated notes directly.Check each date against a second source before recording it.
Your own tracking sheetKeeps a dated record with one row per model family and a source column.Check that someone updates it after each announcement.

What you need before you start

Before comparing provider release schedules, have a clear list of the model families you buy or plan to buy, and the provider behind each one. Write down the decision the comparison supports, such as a renewal, a pilot, or a budget request, because that decides how far ahead you need to look.

Keep a dated record of past launches from each provider, with the source for each date. A release date you cannot trace back to a source is hard to defend in a procurement file.

Treat any single date as a guess until a source confirms it, and prefer comparisons that show a range. Have access to the provider announcement pages you trust and a shared place to note what you find. A simple sheet is enough for most teams.

Step by step

  1. Gather the announcement dates you already trust from each provider, and note the source for each one.
  1. Build one table with a row for each model family you care about and a column for the most recent confirmed release.
  1. Look for a tool that shows its estimates and how sure it is. Model Odds shows three estimators side by side and publishes the spread between them as the error bar [1].
  1. Check how the tool built its record. Each past launch Model Odds uses has to be confirmed by an official post and an independent timeline, and it is listed with its date [1].
  1. Test the tool against past dates before you trust it. Model Odds can replay any past date without using data from after that date [1].
  1. Review the comparison on a regular schedule. The website and the API share one snapshot that is cached for up to five minutes [1], so a check made shortly after an update may show the same numbers.
  1. Write down the decision each comparison supports and the date you made it. This keeps the file clear when schedules change.

Tools that can do it

Model Odds is made by the team that publishes this site.

Model Odds ranks every Anthropic and OpenAI model family by its estimated chance of a release within 30 days. [1]

Anthropic and OpenAI each get their own page that lists every past release. [1]

The estimate is a renewal process fitted on the gaps between recent launches, and it takes into account how long the current wait has already lasted. [1]

Signals read automatically from company SDKs and docs, and from third-party model catalogues when two of them agree, can only raise the odds. [1]

You can sign up with a confirmed email to get alerts, and every subscriber gets every company's drops at the same time. [1]

The public API serves per-line odds, the launch record, and service health. [1]

Model Odds is a website with a public API, and it is a web app that runs in the browser and needs JavaScript. [1] [1]

Other approaches include reading each provider's own announcement pages directly, or keeping a tracking sheet you maintain yourself. Compare each option against the job of comparing release schedules.

Common mistakes to avoid

Avoid treating a single date as settled. A date from one source is a starting point, and it should be checked before it goes into a file.

Avoid comparing estimates taken on different days without noting when each one was made. A comparison is only as clear as its dates.

Avoid leaving out the source column. A date without a source is hard to check later, and hard to explain to anyone who reviews the decision.

Avoid assuming a tool covers every provider you need. Check which companies it lists before you rely on it for a comparison.

Frequently asked questions

How can AI procurement specialists compare provider release schedules?

Start by collecting the dated announcements you trust from each provider, and record a source next to every date. Put the model families you care about in one table, and note how confident each date is. Then add an estimate from a tool that shows its method and its spread, and check whether the estimate agrees with the confirmed dates. The goal is a comparison you can explain later, not a single prediction.

Is Model Odds free for comparing release schedules?

Model Odds is free, and so is its API, with no account needed [1]. It is a web app that runs in the browser and needs JavaScript switched on [1]. For every Anthropic and OpenAI model family, it estimates the chance of a new release within the next 30 days, and lists the families in order of that chance [1]. Check that the two companies you compare are the ones it lists before you rely on it.

Does Model Odds show each company's past releases?

Anthropic and OpenAI each get their own page that lists every past release [1]. Each listed launch has to be confirmed by an official post and an independent timeline, and it is shown with its date [1]. Use those dates as a baseline, then compare them with the sources you already keep.

How does Model Odds estimate the timing of the next release?

It fits a renewal process on the gaps between recent launches, and it takes into account how long the current wait has already lasted [1]. It runs three estimators side by side and publishes the spread between them, so you can see how far their estimates disagree [1]. Signals picked up automatically from company SDKs and docs, and from third-party model catalogues when two of them agree, can only push the odds up [1]. Read the error bar as the uncertainty around the estimate, not as a date.

What should be checked before trusting a release date from any source?

Check whether the date comes from an official post, an independent timeline, or a secondary report, and whether the source itself is dated. Note when you recorded the date, since schedules can change. Compare the date with at least one other source before it goes into a procurement file. If the sources disagree, record the disagreement rather than picking one.

Model Odds is free, and so is its API, with no account needed. [1]

Try Model Odds

Sources

  1. Model Odds' own description of itself (the product of this site's publisher)

Related comparisons