ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

Per-Seat AI Is Priced Against a Falling Floor

Miguel AmigotSeptember 1, 2026
Premium

OpenAI published Jalapeño's benchmarks at Hot Chips 2026: 1.5–1.9x throughput per kilowatt and 1.7–3.6x lower latency than NVIDIA's GB200 and GB300, at 700W against 1,400W. Inference costs have fallen roughly 95% in two years, and every per-seat AI licence is priced against a floor that keeps dropping.

The Short Answer

OpenAI published Jalapeño's benchmarks at Hot Chips 2026: 1.5–1.9x more throughput per kilowatt and 1.7–3.6x lower latency than NVIDIA's GB200 and GB300, at 700W against up to 1,400W. Combined with inference costs falling roughly 95% in two years, every per-seat AI licence is priced against a collapsing floor. On ibl.ai you own all the code and the data, so each cost reduction reaches you instead of a vendor's margin.

The chip is interesting. The pricing consequence is the part that belongs in a budget conversation.

What did OpenAI actually publish about Jalapeño?

Jalapeño is an inference ASIC OpenAI co-developed with Broadcom, detailed at Hot Chips 2026 in late August. The published comparisons, against NVIDIA's GB200 and GB300 rack systems:

  • 1.5x to 1.9x more throughput per kilowatt
  • 1.7x to 3.6x lower end-to-end latency
  • 2.1x to 4.1x higher performance on highly interactive workloads

Note the ranges. Most coverage has quoted the top of each — "1.9x and 3.6x" — which is the best case, not the result.

The hardware: 216GB of HBM4, up to 13.4 MXFP4 PFLOPS, a NUMA-style architecture built around 64 memory/core slices, drawing 700W. NVIDIA's comparators draw roughly 1,200W (GB200) and 1,400W (GB300).

OpenAI reports moving from initial design to manufacturing tapeout in nine months, using AI in the design loop for implementation exploration, verification and arithmetic circuit optimisation.

Deployment into its own infrastructure is planned by the end of 2026 — alongside, not instead of, continued NVIDIA purchases.

That last detail is the honest one. This is not a company replacing its GPU fleet. It is a company adding a workload-specific accelerator for the workload it runs most.

Why does the power number matter more than the throughput number?

Because in a datacentre, power is the binding constraint before capital is.

A 700W part delivering more throughput than a 1,400W part is not a 2x improvement on a spreadsheet line — it changes how many accelerators fit in a rack, what cooling is required, and whether an existing facility can host the deployment at all.

For an enterprise evaluating on-premise inference, this is the difference between "we need a new facility" and "this fits in the rack we have." Efficiency gains at the silicon layer show up as deployability long before they show up as unit economics.

We flagged the fragmentation of the inference market when custom silicon started splitting from training hardware in June. What is new is not that OpenAI designed a chip — that was known. It is that there are now published numbers to compare against.

How far have inference costs actually fallen?

Far enough that pricing assumptions from 2024 no longer describe the market.

GPT-4 launched in 2023 at roughly $30 per million input tokens. By mid-2026, equal-or-better quality is available from open-weight models at under $0.50 per million tokens — a decline of roughly 95% in two years. Stanford's AI Index measured one version of this decline at 280x.

Three forces compound:

Model efficiency. Smaller models reaching last generation's quality.

Inference optimisation. vLLM with PagedAttention delivering multiples of throughput through continuous batching; quantisation (INT4/INT8, FP8) shrinking memory footprints.

Hardware competition. Jalapeño, Microsoft's Maia, Meta's MTIA, Amazon's Inferentia and Trainium, Google's TPUs. Every hyperscaler building inference silicon pushes the floor down for everyone, including for the open-weight models an enterprise runs itself.

Cost model 1,000 users 5,000 users Behaviour as usage grows
Per-seat licence @ $30/user/mo $360,000/yr $1,800,000/yr Scales with headcount, used or not
Per-seat licence @ $60/user/mo $720,000/yr $3,600,000/yr Scales with headcount, used or not
Self-hosted on owned hardware GPU + power GPU + power Scales with actual work; absorbs every cost decline

Headcount figures are illustrative at published list prices. The point is the shape, not the exact cell: one column grows with how many people you employ, the other with how much work you actually do.

What does this mean for a per-seat AI contract?

It means you are paying a fixed price against a falling cost base, and the difference accrues to the vendor.

A per-seat licence signed on 2024 cost assumptions is a bet that the underlying cost of inference stays roughly where it was. It has not.

When a model gets 40% cheaper to serve, an organisation running its own infrastructure sees that as a lower bill. An organisation on a per-seat contract sees the same invoice.

This is why per-seat is structurally the wrong shape at scale rather than merely a more expensive option. It prices the wrong thing — people, rather than work — and it insulates you from exactly the improvement you would most want to capture.

The hardware side is now within reach for real workloads. A single NVIDIA RTX PRO 6000 Blackwell with 96GB of ECC GDDR7 can self-host a 70-billion-parameter model at FP8.

For organisations at sustained volume, published analyses put break-even on hardware in the region of 9 to 18 months under continuous load, with self-hosting delivering multiples of cost saving over premium API pricing at high token throughput.

Those break-even figures deserve a caveat that vendor comparisons usually omit: they assume continuous load. Hardware sitting idle overnight has a much worse payback than a spreadsheet showing peak throughput suggests. Model your actual duty cycle, not your peak.

What should you actually do about it?

Price the work, not the seats. Estimate tokens per month for the workflows you are actually automating. If that number is small, a metered API is genuinely the right answer and you should not build a datacentre. If it is large and growing, per-seat pricing is working against you.

Keep the model swappable. The entire benefit of a falling floor depends on being able to move to whatever is cheapest and good enough next quarter. An architecture that is model-agnostic across any LLM converts every price drop into your saving. One wired to a single vendor's model converts it into theirs.

Re-examine contracts written before this year. A three-year per-seat agreement priced in 2024 is being served by inference that costs a fraction of what it did when the ink dried.

The floor is still falling. The question is only whether your architecture lets you follow it down.

Sources: OpenAI — OpenAI and Broadcom unveil LLM-optimized inference chip · Tom's Hardware — Hot Chips 2026: OpenAI's Jalapeño AI ASIC unpacked · Broadcom — OpenAI and Broadcom Unveil LLM-Optimized Intelligence Processor

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.

  • Model-agnostic

    Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work — so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope · fixed timeline

A time-boxed proof of value on your real data — not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time · not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data · run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Six figures

perpetual license · you own the stack

We transfer the full source code. You own and self-host the entire platform — outright.

Best for: Government, defense, and enterprises that require perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable · zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM — Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY