The deploy took four minutes. The evening is yours.

Spend it on the recital.

The game you said you'd be at.
The long way home.
Dinner, while it's still hot.
02:14 · 0 incidents

One script. Every database. On purpose.

Nobody saw the outage that didn't happen.

SQL MultiCast runs your .sql scripts across a named list of databases — fifty dev instances, every tenant shard, or the three servers you actually meant. With the guardrails to make sure it was the three you meant.

Free for individuals and small teams. Verify an email address once — no card. Every feature is unlocked for 30 days, and the free tier keeps working after that.

Lane 07 · Prod

Prod is
game day.

You've already practiced this. Built for the part of the job that goes wrong quietly.

01

Call the play once.

Distribution lists, not a checkbox hunt

Name a set of databases once and reuse it. All Prod means the same thing today as it did last quarter, and the list is a file you can review in a pull request.

02

Name the stakes out loud.

A production target says so

Connections marked production require an explicit, itemised confirmation before anything connects — naming the servers, not a generic "are you sure". The same consent is a --yes flag in the CLI, so automation cannot skip what the UI insists on.

03

See the miss. Fix it.

Errors that take you to the line

A failure reports the batch, the line and the database, and the editor jumps there with a marker. Four on-error policies, chosen per script: stop the batch, stop the target, skip the target, or carry on.

04

Every value in position.

Variables that know what they are

Declare a variable once for the workspace and give it a value per environment. Each one declares how it renders — text, identifier, number or raw — so substitution quotes correctly instead of hoping.

05

Scout before kickoff.

Read the estate before you change it

list coverage reads every database in a group and reports what differs between them, so a migration that assumes uniformity finds out first.

06

Same moves on every field.

Same tool, three faces

The desktop app, the sqlmc command line, and an MCP server for your coding agent all run the same code. A guardrail present in one and missing in another would be worse than none, so there aren't any.

Be the reason it's quiet.

Free to use, properly

Individuals and small organizations get every feature, through all three faces, free — no nag screens and nothing held back to sell you later. What the free tier limits is how much you can point at once: three connections and five databases per run, after a 30-day trial with no ceilings at all. Pro removes the ceilings; larger organizations need an Enterprise licence. See where the lines are.

Register and download