Devstral Medium vs Together AI Inference Flex

“The primitive here is clean: a 70B instruction-tuned model with tool-use and long-context chops, released as open weights under Apache 2.0. That's the DX bet — they're trusting developers to self-host and compose rather than forcing you through a managed platform. The moment of truth is spinning this up on a local inference stack or hitting La Plateforme; both paths are documented and neither requires you to invent new abstractions. The weekend-alternative comparison breaks down fast: you can't fine-tune GPT-4o on your own hardware, and the 70B weight class at Apache 2.0 is genuinely rare for agentic coding quality. The specific decision that earns the ship is the open-weights release — it means this is infrastructure you can actually own, not a dependency you rent.”

“The primitive here is clean: a per-token inference endpoint that absorbs burst traffic without requiring you to reserve capacity in advance. The DX bet is that eliminating the capacity-planning step is worth the per-token premium over reserved instances — and for teams getting hammered by unpredictable spikes, that's exactly the right bet. The moment of truth is whether cold-start latency under burst conditions is actually low enough to not matter; Together hasn't published concrete p99 numbers publicly, which is the one thing I'd want before committing. Still, this is a real infrastructure problem and the API surface is not just three wrapped calls — the elasticity contract is the product.”

“Category is open-weights coding models; direct competitors are Qwen2.5-Coder-72B and DeepSeek-Coder-V2, both credible. The scenario where this breaks: multi-agent loops with 50+ tool calls on real monorepos — every 70B model degrades there, and Mistral hasn't published failure-mode data at that scale. What kills this in 12 months isn't a competitor — it's Mistral themselves shipping a larger model that makes this one look like a stepping stone, or the API pricing getting underbid by inference commodity players. But the Apache 2.0 open-weights release is real defensibility against the 'API provider ships this natively' risk: you already have the weights. I'm shipping this because the benchmark position is credible, the license is genuinely open, and the SWE-bench numbers on agentic tasks put it above the 70B field in a way that's hard to dismiss as benchmark-gaming.”

“Direct competitors are Modal, Replicate, and any team that pre-bought a reserved instance block on AWS Inferentia — so the real question is whether Together's per-token burst pricing beats the blended cost of over-provisioning. This breaks down for teams with predictable traffic patterns who'd be subsidizing elasticity they never use, and for very high-volume shops where the per-token premium compounds painfully. The prediction: Together gets acqui-hired or this becomes a commodity feature within 18 months once the major cloud providers finish building model-serving managed services, but right now there's a real window where the operational simplicity justifies the price for mid-size AI teams. What would make me more confident is published SLA data on burst latency — without it, this is a promise, not a product.”

“The thesis: by 2027, the majority of production agentic coding pipelines will be built on open-weight models running on owned infrastructure, not closed API calls, because latency, cost, and IP risk make the closed-API dependency untenable at scale. Devstral Medium is a direct bet on that trajectory, and it's on-time — inference hardware costs dropped enough in 2025 to make 70B self-hosting viable for mid-sized teams. The second-order effect that matters: if this model quality holds at self-hosted inference, it shifts negotiating power from model providers back to platform operators and enterprises. The dependency this bet needs is continued commoditization of H100/H200 spot pricing; if inference costs plateau, the self-hosting advantage shrinks. The future state where this is infrastructure: every mid-market dev platform ships a code agent layer built on Devstral-class weights, tuned for their stack, with zero per-token API exposure.”

“The thesis here is falsifiable: inference workloads will continue to be spiky and unpredictable as AI gets embedded in consumer products, and teams will not want to solve GPU fleet management as a core competency. That's a plausible bet — not a guaranteed one, since it depends on the model-serving abstraction layer not getting commoditized by the hyperscalers faster than Together can build workflow lock-in. The second-order effect that's underappreciated: if burst capacity becomes as easy as an API call, the threshold for shipping AI features into consumer products drops significantly, which expands the total number of AI-in-production deployments — which is good for every inference provider including Together. They're on-time to this trend, not early, which means execution speed matters more than vision right now.”

“The buyer splits into two segments: enterprises with data sovereignty requirements who will pay for on-prem deployment (clear budget, clear value), and API consumers hitting La Plateforme who are price-sensitive and will churn the moment a cheaper inference provider hosts the same Apache 2.0 weights — which will happen within 90 days. Mistral's moat here isn't the model; it's the ongoing fine-tuning roadmap and the trust they've built with European enterprise buyers who need EU-hosted inference. The pricing architecture is sound for the API tier if they hold margins against commodity inference, but the open-weight release is structurally cannibalizing their own API revenue, which means this is a developer-acquisition play, not a monetization play. That's a legitimate strategy if the funnel from open-weights users to enterprise La Plateforme contracts converts — and Mistral has enough enterprise traction in Europe to make that bet credible.”

“The buyer is clear: the ML infra lead at a Series A or B company whose model is in production and who got paged at 2am because a traffic spike hit a rate limit. That person has budget and a real problem. The pricing architecture is smart — per-token with no minimum means Together takes on utilization risk, which is a real commitment that creates trust. The moat question is harder: Together's defensibility is model variety and the operational trust they've built, but when AWS and Google finish productizing managed inference burst, Together needs the switching cost to be workflow-deep, not just API-key-deep. The specific business decision that earns the ship is the no-minimum-commitment structure — it removes the procurement friction that kills developer-led adoption.”