OpenAI delivered excellent reliability in every test, while Anthropic’s models proved faster and more cost-efficient with some trade-offs.
The first time we ran this benchmark, nearly every score sat at or near 100% across three trials per model. It pointed to a tidy conclusion: the frontier is solved, the models are interchangeable, and the best vendor is a matter of preference. However, running it properly at ten trials per model per task—240 runs in all—produced a more accurate picture.
The test pitted Anthropic’s Opus 4.8, Sonnet 5, and Haiku 4.5 against OpenAI’s new GPT-5.6 family, Sol, Terra, and Luna, and tasked each model with realenterprise work: merging access-control rules, untangling a noisy incident feed, writing an authorization engine with a full audit trail, and planning a zero-downtime database migration. Our grading was simple. Either the code passed a test, or it didn’t—and if a model ran past its output budget (16K tokens) mid-answer, that also counted as a miss.
A quick refresher on the four tests
The suite consists of four tests. Each one is real enterprise work where a subtly wrong answer means an outage, a security hole, or downtime, and each carries a weight, so the hard tasks count for more.
OpenAI’s three models passed all their tests without a single miss. Anthropic’s models passed 82% of the tests, but where they succeeded, they did at a fraction of the cost and speed of the OpenAI counterparts. The results make it clear that not everything requires the top model.
Weighted pass score per model (harder tasks carry higher weight)
Weighted frontier score, six models. The three GPT-5.6 models sit at a flat 100%. Anthropic’s line steps down from Opus at 92.9% to Sonnet at 75% to Haiku at 57.9%.
Models only stumbled on the toughest (migration planner) task
Every model aced the calibration task and the authorization engine, and only Haiku stumbled on incident correlation.
Most of the ranking, then, comes down to a single task: the migration planner, which puts the “multi-agent intelligence” of these frontier models to the test. Haiku couldn’t complete it, and Sonnet ran into the token cap seven out of ten times. Even Opus, despite its capabilities, failed twice.
However, the most surprising result was that Luna, OpenAI’s cheapest model, aced even the hardest task as consistently as its more expensive sister models.
Migration planner, trials passed out of 10. OpenAI swept it. Opus dropped two. Sonnet passed three, and all seven of its misses were the same failure: running out of the output budget mid-plan, not getting the plan wrong. Haiku went zero for ten with code that mostly didn’t run.
The final results are nuanced, but make the trade‑offs for enterprise teams clear
If there’s one result in this study that warrants attention, it’s Luna—OpenAI’s lowest-tier model. Not only did it complete all 40 tasks, but it also did it at a lower overall cost. While there will undoubtedly be work beyond Luna’s capabilities—namely, tasks requiring deeper reasoning or longer context performance—it performed comparably to both its sister models and its Anthropic counterparts across the test suite.
It’s also important to note that our test is a single-shot benchmark. External evaluations focused on longer, multi-step agentic workflows typically place Sol and Terra ahead of Luna on extended, complex work, which is consistent with how OpenAI positions its tiers.
From a top-tier model perspective, Sol beat Opus by around 7%. However, on closer inspection, Sol bought those seven points of reliability at roughly three times the cost per result and about nine times the latency. Opus answered in 23 seconds on average; Sol took over three minutes. For many flagship workflows, a correct result in 23 seconds at one-third of the price—with a rare migration slip—is a better tradeoff than a perfect result in three minutes. Of course, this won’t work for certain workloads, with this distinction being the real decision facing enterprise buyers.
For teams optimizing for cost and reliability, there’s one clear winner in our test suite: Luna by OpenAI.
Cost per success against frontier score. Luna and Terra sit top-left—perfect and cost-effective. Sol is perfect but far to the right on price. Opus is nearly as reliable as Sol at a fraction of the cost. Sonnet and Haiku fall down the left side.
Averaged across each vendor’s three models, the two companies divide the results across two different measures:
OpenAI’s lineup is more uniformly reliable across the suite. Anthropic’s is cheaper and faster where its models succeed. Ultimately, which of these matters more depends on the workload and the cost of a failed run.
Head to head, tier by tier:
FullStack’s honest recommendations
No vendor sweeps our evaluation on every axis. Our practical answer is to treat model selection as a routing decision.
For the lowest miss rate, reach for GPT-5.6—but pick Terra or Luna, not Sol. While all three OpenAI models hit 100%, Sol charges two to four times as much and runs far more slowly for the same result. Paying flagship rates for the kinds of tasks behind this report buys you latency, not additional reliability.
For the best overall value, opt for Luna. At four cents per success,OpenAI’s fastest model flawlessly completed hard frontier tasks. If your workload consists of a high volume of repeatable calls, it’s the most efficient option available as of this post.
For the lowest cost per result where occasional failures are acceptable, Opus 4.8 is worth serious consideration. It was the fastest model tested—at one-third Sol's cost—and finished at 93% with occasional migration misses. For interactive, human-in-the-loop workflows where speed is a priority and a retry is cheap, that trade-off is likely worth it.
For migration-style planning work, handle Sonnet 5 and Haiku with care. Sonnet’s problem is specific and addressable: it consistently runs out of output budget on long plans rather than producing incorrect ones. A higher output ceiling will likely improve its score, though teams should account for its higher token cost.
Haiku’s failures run deeper. It generated code that didn’t execute, and a larger budget won’t resolve a syntax error. A compile-and-retry gate should be in place before you use it in any high-stakes pipeline.
Should you trust a result where no Anthropic model hit 100%?
That’s a fair question, and one we asked ourselves before publishing. Ultimately, there are several factors about the test that gave us confidence.
The gaps are large rather than marginal: a model going three of ten, or zero of ten, on a task isn’t noise. The failures also carry consistent, identifiable signatures—truncation for Sonnet and non-running code for Haiku—which is characteristic of structural weaknesses rather than random instability.
OpenAI’s strength in agentic coding is also reflected in independent public benchmarks, so a clean sweep here isn’t an artifact of our test harness.
WHAT THESE QUICK BENCHMARKS ARE, AND WHAT THEY AREN’T
Ten trials across four tasks give us enough data to see consistent patterns on this suite, but four tasks is still a narrow, deliberately edge-heavy set—not a general capability ranking. Reliability is measured under a fixed 16,000-token output budget, which is the single variable most likely to improve Sonnet’s mid-tier result if raised. Haiku ran under a slightly different reasoning configuration than the other models, with a fixed thinking budget rather than high effort, though that gap doesn’t explain its non-running code failures. This evaluation measures single-shot code generation, not full agentic sessions, which cost more and exercise different skills. Sonnet 5 is on introductory pricing through August 31, 2026. Model prices were confirmed against Anthropic’s and OpenAI’s live pricing pages on July 15, 2026.
FullStack runs these evaluations independently—across vendors rather than relying on any lab’s published launch benchmarks—because our team ships real software for real customers and integrates these models directly into our development process. Our takeaway isn’t that OpenAI wins or that Anthropic wins. Rather, on this suite, we found that OpenAI is the more reliable default and that Anthropic is the faster and more cost-efficient option.
The best approach is to route each job to whichever of those qualities matters most for that workload. Done well, your team will capture most of OpenAI’s reliability at most of Anthropic’s price, giving you the best of both worlds.
Learn more
Frequently Asked Questions
How did OpenAI’s Sol, Terra, and Luna perform in this coding benchmark?
OpenAI’s GPT‑5.6 models—Sol, Terra, and Luna—each achieved 100% reliability across all four software engineering tasks and all 40 trials per model under a 16K token output budget. This means every generated solution either passed the tests or, in the case of long outputs, stayed within the token limit without truncation. Terra and Luna delivered this perfect record at lower cost and latency than Sol, making them stronger defaults for most enterprise coding workloads.
How did Anthropic’s Opus 4.8, Sonnet 5, and Haiku 4.5 compare to OpenAI’s models?
Anthropic’s models passed 82% of tests overall, with Opus 4.8 reaching 92.9%, Sonnet 5 hitting 75%, and Haiku 4.5 landing at 57.9%. While they lagged OpenAI on reliability, Anthropic’s models were, on average, roughly 2.3× cheaper per successful result and about three times faster in latency. The main weaknesses were structural: Sonnet repeatedly ran out of output budget on long migration plans, and Haiku often produced code that failed to run.
Which AI coding model offers the best value for enterprise workloads?
For cost‑optimized reliability, the benchmark points to Luna—OpenAI’s lowest‑tier GPT‑5.6 model—as the best overall value. Luna completed all 40 tasks flawlessly, including the hardest migration planner test, at around four cents per successful result and with competitive latency. For teams running high‑volume, repeatable coding workflows, Luna captures the reliability benefits of frontier models at a near‑small‑model price.
When does it make sense to choose Anthropic’s Opus, Sonnet, or Haiku instead of OpenAI’s models?
Opus 4.8 is compelling when speed and cost matter more than absolute reliability, especially in human‑in‑the‑loop workflows where a quick retry is acceptable. It comes within roughly seven points of Sol’s reliability while being about three times cheaper and nine times faster per answer. Sonnet 5 can be attractive at its introductory pricing if teams can tolerate occasional truncation and tune output budgets accordingly, while Haiku 4.5 should be routed through compile‑and‑retry safeguards before use in high‑stakes pipelines due to non‑running code failures.
What do these results mean for enterprise AI routing and model selection?
The benchmark suggests that no single vendor or model tier is universally “best”; instead, teams should treat model choice as a routing decision. OpenAI’s GPT‑5.6 lineup is the more reliable default for agentic coding, whereas Anthropic’s models offer faster, cheaper results where they succeed. By routing tasks according to workload requirements—reliability for critical automation, cost and latency for interactive or retry‑friendly flows—enterprises can blend OpenAI’s reliability with Anthropic’s economy to get most of the benefits of both.
AI is changing software development.
The Engineer's AI-Enabled Development Handbook is your guide to incorporating AI into development processes for smoother, faster, and smarter development.
Enjoyed the article? Get new content delivered to your inbox.
Subscribe below and stay updated with the latest developer guides and industry insights.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
We use cookies to provide our services, to allow us to better understand our audience, and to provide and serve personalized ads or content. By using our website, you consent to the terms of our Privacy Policy and our Cookie Policy, and the use of cookies, pixels, and other technology as described more fully therein
The GPC signal has been honored.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.