Strategy Is Retiring MicroStrategy Developer by December 2026

Open your Strategy release notes. June twenty twenty-six. Scroll to End of Support. Developer. Command Manager. Object Manager. Available through the December twenty twenty-six release... and then not included in subsequent upgrades.

Developer? That's where half my modelers live all day.

Fourteen months. And here's the question I want you holding the whole time: the thing replacing it is called Mosaic, and it promises one model across every tool. I think it can do that. I also think most shops are about to end up with two models instead of one.

Okay. Back up. This is MicroStrategy, right?

Was. According to the analyst firm BARC, founded nineteen eighty-nine as MicroStrategy, rebranded to Strategy in February twenty twenty-five. And as part of the rebrand... they put the Bitcoin symbol in the logo.

In the logo. Of a BI vendor.

Their own LinkedIn description is that they're the first and largest Bitcoin treasury company AND a provider of universal semantic layer and AI plus BI software.

So when I sign a renewal, what am I actually buying?

Two flagship products. Mosaic, and Strategy One. And which one is the core and which one is the add-on... that's the whole episode. Mosaic went generally available June twenty-fourth, twenty twenty-five. They call it an AI-powered Universal Intelligence Layer. Sits on top of any database or warehouse. Define metrics, relationships, calculations, access policies once... apply them across BI tools, applications and AI agents.

Katy, every semantic layer vendor on earth says that exact sentence.

They do. So here's the part that's actually specific. BARC's assessment makes one architectural point in Strategy's favor: Strategy One was built from the ground up, without acquisitions.

Which... is not nothing. Half the competition is three products in a trench coat.

Right. If your platform was assembled by acquisition, you've got two or three definitions of revenue living in different engines and a reconciliation meeting every Thursday that nobody enjoys.

But hang on. Mosaic is NEW. So they've got the old project-based model, and now Mosaic. That's the exact problem you just described.

That's the honest tension, and you can watch them stitching it month by month in the notes. January twenty twenty-six: Mosaic model linking, out of the box. Create linked attributes across models. Establish relationships between, quote, disparate models.

Disparate models. That phrase is doing a LOT of work.

It's an admission. In a real deployment you will have more than one model. The fabric is the linking, not some mythical single cube. Then February twenty twenty-six, listed as preview: access Mosaic models in the M-C-P server.

Meaning an agent can hit your governed metrics directly instead of hallucinating at the raw tables.

That's the intent. Their marketing line is blunt... AI guesses, Mosaic gives the right answer. And the most recent note I can verify is September twenty twenty-six, Mosaic Studio, value parameters. Tiny feature. But the cadence tells you where every engineer in that building is pointed.

And not at Developer.

Not at Developer. If your promotion path from dev to test to production runs through Object Manager, December twenty twenty-six is your deadline to replace it.

So is Mosaic the replacement for all of that? Or is it a second thing they're selling me alongside the first thing?

Read the Microsoft marketplace listing. The wording is that for organizations needing a complete AI plus BI experience on top of this trusted semantic core, Strategy One can be ADDED alongside Mosaic... to deliver governed self-service and pixel-perfect reporting.

So Mosaic is the core now. And the reporting I already paid for is the add-on.

That's how it reads. And that's the payoff to the question I opened with. Mosaic CAN hold embedded, self-service and governed reporting together... but only if your embedded apps and your dashboards both consume Mosaic. Run half on the old project model and you've fragmented the exact thing you bought this to unify.

Nobody migrates everything at once, though. Nobody ever has.

So be deliberate. Take the metrics finance and operations actually argue about, move those to Mosaic first, link the rest, and treat December twenty twenty-six as a hard date for your deployment tooling. Not a suggestion.

Give me the line between confirmed and claimed.

Confirmed: the rebrand, the June twenty twenty-five general availability, the end-of-support dates, the features in the release notes. Claimed by the vendor: that the semantic graph delivers a single source of truth, and that AI answers get reliably better. I have not seen independent benchmarking of that.

Trust the dates, test the promises.

Always. Next week, two things. Whether M-C-P server access moves from preview to general availability in the quarterly release... and whether any customer publishes real numbers on a Developer-to-Mosaic migration.

One model, every tool. Easy to say in a keynote.

A semantic layer is only universal if everything points at it. Otherwise you don't have one source of truth... you have a second one, and somebody on your team quietly keeping it alive.