Every vendor sells an “AI Platform.” None of them sells a complete one.

Walk any conference floor in 2026 and every booth has the same sign: AI Platform. The hyperscalers say it. The on-prem hardware vendors say it. The data companies say it. Each one means something different by it, and each one delivers a different slice of the actual stack.

I run a lab. I’m a practitioner analyst, I put this stuff on real hardware and watch where it breaks. The pattern is consistent: no single vendor delivers a complete enterprise AI stack. You compose one. Completeness is built, not bought.

So I did two things about it.

First, I graded the vendors. Layer by layer.

A real AI stack isn’t one product. It’s a set of layers, and most buyers can’t see the seams. So I made the seams explicit. I call it the 4+1 model:

• Compute and networking at the bottom.
• The data plane above it: storage, retrieval, pipelines.
• Orchestration and runtime in the middle.
• The reasoning plane near the top. This is the layer that decides what runs where based on business context, not just cluster metrics.
• It’s the real differentiator, and it’s the layer most enterprise stacks are quietly missing.
• The application layer on top, where the business value shows up. That’s the “+1.”

Then I graded the major vendors at every layer. Each grade carries two reads, not one. Can the vendor actually do the job at that layer? And who keeps the decision authority: you, or the vendor? Capability tells you the layer works. Authority tells you what judgment you’re borrowing from your platform vendor without noticing. Both live at layer2c.com, and every grade is something I tested, not a feature checklist.

Then I built Stack Builder, so you can compose with those grades.

Stack Builder is live at stackbuilder.layer2c.com. It’s free. No login, no limit.

You tell it what you’re trying to do, or you start from an easy-button: public, private, or hybrid. It composes a complete 4+1 architecture across vendors, layer by layer, from the graded assessments. Not from a model guessing what vendors do. From grades I stand behind. When it places a vendor at a layer, you can click straight through to the assessment that backs it.

Then it does the part the booth never does. It shows you the trade.

Every composed stack comes with two signals. The first is integration effort: where stitching best-of-breed across vendors breaks the native integration a single platform builds for itself. The second is reasoning dependency: how much autonomous judgment the stack is built to run, and therefore how much it matters who owns that reasoning plane. A single public cloud scores low on integration effort and high on reasoning dependency. Easy to assemble, and you’ve handed the hardest decisions to one vendor. That’s the trade most buyers back into.

You can edit the whole thing. Drag a vendor onto a layer and the stack recomposes. Don’t like the reasoning plane the easy-button picked? Swap it and watch the signals move.

What it is, and what it isn’t.

Stack Builder is an educational instrument, not a turnkey generator. It won’t hand you a finished design to go build unadvised. There is no turnkey AI stack, and the tool says so out loud. The easy-buttons are illustrative patterns. They teach the shapes and what each shape costs you.

What it’s good at is making the invisible choice visible. The most expensive mistake I see isn’t picking the wrong vendor. It’s ceding your reasoning plane by default, then discovering the placement in a post-incident review instead of choosing it before you deploy. Neither placement is wrong. Unplaced authority is wrong.

So here’s who should open it. If you’re about to standardize on one platform because the demo was clean, spend ten minutes composing the alternative and read the two signals. If you’re building on-prem and think a strong storage layer means you’re covered, look at where your reasoning plane actually sits. Then make the call on purpose.

Create an account and it saves your roadmaps. That’s the only thing login gets you. Everything else is open.

Go try it: stackbuilder.layer2c.com. Tell me where it’s wrong. The grades are tested. The way it stitches them together earns its authority in the field, by people using it, and that starts now.