RadarModel.com

Database Schema Drift Starts With One Manual ALTER

Sat, 17 Oct 2026 00:00:00 +0000

It’s 2 a.m. and checkout is timing out. Someone finds the slow query, adds an index on production by hand, and the graphs go green. Nobody writes a migration for it. Three weeks later a deploy runs a migration that drops and rebuilds that table, the index is gone, and checkout times out again. Or the other way round: a hotfix makes a column NOT NULL on production only, and the next release, which was tested against staging, fails every insert that leaves it empty.

RadarModel Schema Launches to Catch Database Drift

Sat, 17 Oct 2026 00:00:00 +0000

RadarModel 0.2 adds a second command, radarmodel-schema. It reads the live schema of a Postgres, MySQL, MariaDB or SQLite database, keeps it, reads it again later and tells you what changed. A column dropped by hand, a type changed on production only, an index lost in a rebuild. It’s in the same download as RadarModel AI, open source under the Apache License 2.0, and the code is on GitHub.

Migration tools know what they applied. They don’t look at what’s actually in the database, and a change made around them stays invisible until something fails. RadarModel Schema looks. Why schema drift happens

How RadarModel Schema Was Tested Against Real Databases

Sat, 17 Oct 2026 00:00:00 +0000

A drift detector earns trust slowly and loses it in one night. Report a dropped table that’s still there and the alert channel gets muted. So RadarModel Schema’s tests spend as much effort on what it must not report as on what it must.

None of them use a fake database. SQLite runs on Linux, macOS and Windows. Postgres 12, 16 and 17, MySQL 8.0 and 8.4, and MariaDB 10.6 and 11.4 run in containers on every push. Each test creates its own database on the server, does real DDL to it, and drops it afterwards.

AI Models Drift Under Your App and Nobody Tells You

Sat, 17 Oct 2026 00:00:00 +0000

Your app calls an AI model by name. It’s a string in a config file, gpt-4o or claude-sonnet-4-5, and it was right the day someone typed it. The model behind that string lives on somebody else’s servers, on somebody else’s schedule.

Providers retire models. They rename them, or point an alias at a newer one. They cut a context window, add a retirement date, move a model from active to deprecated, raise the price per token. None of that is a secret. It goes into a changelog, a deprecations page, maybe an email to whoever signed up for the account three years ago. And the team that owns the app finds out from a stack trace.

RadarModel AI Launches as Open Source Under the Apache License

Sat, 17 Oct 2026 00:00:00 +0000

RadarModel AI 0.1 is out. It reads the model lists of OpenAI, Anthropic, Google and OpenRouter, compares each with the last one it saw, and tells you when a model your app calls is gone, retiring, or changed its limits or price. It’s open source under the Apache License 2.0, one binary per system, and the code is on GitHub.

It exists because providers change models on their own schedule, and the first sign is usually a failed request. The model lists are public through each provider’s API, so a small tool can read them every hour and say what moved. Why it matters

How RadarModel AI Was Tested Against Broken Provider Answers

Sat, 17 Oct 2026 00:00:00 +0000

A tool that watches for removed models has one way to be useless: telling you a model is gone when it isn’t. Do it twice and the alerts get muted, and then the real removal goes by unseen. So most of RadarModel AI’s tests aren’t about finding changes. They’re about not inventing them.

The fake provider

The tests run against a fake API that answers like all four providers at once: OpenAI’s list, Anthropic’s with its cursor paging, Google’s with page tokens, OpenRouter’s with prices and limits. Each test takes a baseline, then breaks the next answer from one provider in one specific way.

Why the Project Is Called RadarModel

Sat, 17 Oct 2026 00:00:00 +0000

Two words, both doing their plain jobs.

A radar doesn’t look once. It sweeps, round and round, and what it’s good at is noticing that something moved since the last pass. That’s the whole method here: read the list, keep it, read it again, compare.

About

Mon, 01 Jan 0001 00:00:00 +0000

RadarModel watches the models your app depends on and tells you when one of them changes underneath it. It’s two products on one small engine. RadarModel AI watches the model lists of AI providers. RadarModel Schema watches database schemas for drift: changes made outside your migrations.

Why the Project Exists

An app that calls an AI model calls it by name. gpt-4o, claude-sonnet-4-5, gemini-2.5-flash. Those names don’t stay put. Providers retire models on a schedule, rename them, shrink a context window, add a retirement date, or change the price per token. Each of them announces it somewhere: a changelog, a deprecations page, an email to whoever signed up. Most teams find out when a request fails in production.

Contact

Mon, 01 Jan 0001 00:00:00 +0000

The project would like to hear from:

Teams running AI in production who want to say what they’d need RadarModel AI to catch.
Teams whose databases drift who want to say what RadarModel Schema should catch, or which database to cover next.
Anyone who wants another provider covered, such as Azure OpenAI, AWS Bedrock or Mistral.
Anyone with a question about the tool, its tests or the figures on this site.

Write to info@radarmodel.com.

Download RadarModel

Mon, 01 Jan 0001 00:00:00 +0000

Each archive below holds both commands, radarmodel-ai and radarmodel-schema, with the license files and the README. The links always point to the latest release.

System	Download
Linux, x86-64	radarmodel_linux_amd64.tar.gz
Linux, ARM64	radarmodel_linux_arm64.tar.gz
macOS, Apple silicon	radarmodel_darwin_arm64.tar.gz
macOS, Intel	radarmodel_darwin_amd64.tar.gz
Windows, x86-64	radarmodel_windows_amd64.zip

Checksums are in SHA256SUMS. Every release is listed on GitHub.

Install

On Linux or macOS:

tar -xzf radarmodel_linux_amd64.tar.gz
sudo mv radarmodel-ai radarmodel-schema /usr/local/bin/
radarmodel-ai version
radarmodel-schema version

The binaries are pure Go and need nothing else installed. The macOS binaries aren’t signed by Apple, so macOS may block the first run. Allow it in System Settings under Privacy & Security, or run xattr -d com.apple.quarantine radarmodel-ai radarmodel-schema. On Windows, unzip the archive and run radarmodel-ai.exe or radarmodel-schema.exe from a terminal.

Quick Start

Mon, 01 Jan 0001 00:00:00 +0000

Five minutes, one config file, and you’ll know the next time a model your app calls changes. First download RadarModel and put radarmodel-ai and radarmodel-schema on your PATH. This page starts with RadarModel AI; RadarModel Schema follows.

1. Write a config

radarmodel-ai init

That writes radarmodel.json in the current folder. Open it and put the models your app actually calls under watch, as provider:model. Remove the providers you don’t use.

{
  "interval": "1h",
  "providers": [
    {"type": "openai"},
    {"type": "openrouter"}
  ],
  "watch": [
    "openai:gpt-4o",
    "openrouter:anthropic/*"
  ]
}

A * matches anything, slashes included, so openrouter:anthropic/* watches every Anthropic model on OpenRouter.

Reference

Mon, 01 Jan 0001 00:00:00 +0000

Everything RadarModel 0.2 does, in one page: radarmodel-ai first, then radarmodel-schema. The README on GitHub says the same in the repository.

Commands

radarmodel-ai init  [-config FILE]           write a starter config
radarmodel-ai check [-config FILE] [flags]   scan once, compare, report
radarmodel-ai watch [-config FILE] [flags]   scan every interval until stopped
radarmodel-ai show  [-config FILE] SOURCE    list the stored models of a source
radarmodel-ai version

The config is radarmodel.json in the current folder, or the file in $RADARMODEL_CONFIG, or -config FILE.