Jamba's pivot comes with turmoil
AI21, the company behind Jamba, was mid-transition from selling standalone LLMs to its new agent platform, Maestro. At the same time, more than 60% of its staff have been cut and a co-founder has departed. Here's what that means for evaluating AI21 as a vendor.
The org shrank mid-transition
to a new platform
For the past few quarters, AI21 has been moving away from selling its standalone large language model, Jamba, and toward Maestro, its new platform for building agents. Rewriting a product's go-to-market motion while reshuffling engineering and sales priorities is a heavy lift for any organization, even in calm conditions.
Onto that, in May 2026 AI21 laid off 61% of its entire staff and also lost a co-founder, who departed the company. AI21's official site continues to post Maestro-related announcements, but a strategic product pivot happening almost simultaneously with a severe headcount and leadership contraction is exactly the kind of combination that raises outside questions about business continuity.
This shouldn't be read as an isolated news item. It's better understood as two changes landing at once: a bet on a new platform, and a sharp organizational contraction.
What happened in recent months
What to add to your
vendor evaluation
This affects business stakeholders and product managers who are evaluating, or already running on, AI21 / Jamba.
Business
When picking a new vendor, weigh not just performance and cost but whether the company will still be around, in similar form, a few years from now. A 61% reduction is a scale that can plausibly thin out support and onboarding resources. Before signing, get written confirmation of how the support desk will be staffed going forward.
Product Manager
If you've already built on Jamba, the impact is limited — there's no urgent need to switch. But if any of your roadmap depends on Maestro's migration timeline, factor in the risk that it slips. If you're still in the evaluation phase, it's prudent to evaluate a multi-vendor setup in parallel rather than committing to one path.
Choosing a vendor is a bet not just on performance, but on
whether the company will still be around years from now.
What to check before signing
The near-term question is whether AI21, now with a smaller team, can carry the Maestro migration through to completion. Confirming these three points up front avoids surprises later.
Get support continuity in writing
Confirm with your account contact, in writing, whether the existing Jamba support SLA will hold going forward.
Add a continuity clause
Spell out in the contract what happens if the SLA isn't met, including data-migration provisions.
Evaluate alternatives in parallel
Assess a multi-vendor setup alongside AI21 so you're not solely dependent on one company.
Reasons for caution — the continuity question
The biggest unknown is how the shrunken organization will affect the speed and quality of product development going forward — that isn't visible yet. The co-founder's departure suggests that the leadership driving the Maestro pivot is itself in flux. AI21's site doesn't disclose the background of the departure or the details of any succession plan, so meaningful uncertainty remains.
A 61% reduction likely goes well beyond routine cost optimization. Whether AI21 can run a new platform like Maestro reliably with a much thinner development and support staff is something that can only be judged by results going forward. It's possible to read this optimistically — a leaner org focused entirely on Maestro — but it's equally plausible that reduced engineering capacity directly delays the roadmap. At this point, neither outcome can be ruled out.
If you're already running on a different vendor, the practical impact is limited — this alone isn't a reason to rush off Jamba. But if you're now considering AI21 / Jamba as a new vendor, it's worth explicitly adding "continuity risk" as an evaluation axis alongside the usual criteria.
| Traditional evaluation criteria | What to add now |
|---|---|
| Model performance / benchmarks | Staff and leadership changes in the past 6 months |
| API pricing and terms | Whether support SLAs are guaranteed to continue |
| Depth of existing features | Progress on the in-flight Maestro migration |