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

Duolingo Cut Its AI Video Call Cost From $0.30 to Under a Cent. What the Earnings Calls Actually Say

ibl.aiNovember 9, 2026
Premium

Duolingo says the AI inference behind one Video Call fell from about $0.30 to well under $0.01, mainly by moving to open-weight models while keeping frontier models for the few cases that need them. What its two earnings calls support, what the short version leaves out, and why the right to switch models is the real asset.

The Short Answer

Duolingo says the AI inference behind one Video Call fell from about $0.30 to well under $0.01, mainly by moving to open-weight models. The saving came from choosing the model per task. On ibl.ai you own all the code and the data and run every agent model-agnostic, so that choice stays yours.

The figures come from Duolingo's own earnings calls: the Q2 2026 call on August 5, 2026, and the Q3 2026 call on November 3, 2026.

What did Duolingo say about its Video Call AI cost?

Duolingo's CEO, Luis von Ahn, said on the November 3 call that Video Call "was costing about $0.30 per call, just generally on AI inference." He added: "We've managed to reduce that cost to well under $0.01 per call."

He named the cause in the same answer: "that's mainly by moving to open-source models or open-weight models." That is a drop of more than 30 times, a cut of more than 96%.

The number is not new this week. Von Ahn first gave it on the August 5 call: "It is now under $0.01 per video call." The November call repeated it with more detail.

What does the short version of the Duolingo story leave out?

The short version leaves out two details, and neither changes the conclusion. First, "per call" here means one Video Call conversation with Duolingo's AI character, not a single request to a model.

Second, Duolingo did not switch off frontier models. On November 3 von Ahn said "There are some small cases where a frontier model's still needed."

In August he said the company wants "to use open-weight models as much as possible," because "sometimes the frontier models are more advanced."

So the accurate version is a mix: open-weight models for the bulk of the work, frontier models where they still earn their price.

Why did the cost of Duolingo's Video Call matter to its business?

The cost decided who could get the feature. At $0.30 a call, von Ahn said in August, Duolingo "decided to put it behind our most expensive plan, which is Max."

Once the cost fell, Video Call moved down a tier. On November 3 he said: "Video Call for the longest time was just available in Max. Now that it's in Super." The move also sits alongside Duolingo's plan, stated on the same call, to sunset Max.

The CFO, Gillian Munson, said "The AI costs have not been as high as we thought, which is great," and named "less AI costs than we expected" as a driver of gross margin. She also expects margin to dip slightly as Video Call rolls out to all paid subscribers.

Are open-weight models good enough for production AI features?

For most of Duolingo's users, the company says yes. Von Ahn's words on November 3: "for the majority of our users, open-weight models are about as good as frontier models."

Duolingo is not the only one reporting this. Revolut says self-hosting open GLM models cut its AI coding costs to roughly a tenth, about $0.30 per million tokens; we went through what Revolut's numbers actually say.

The pattern across both: most production work, conversation practice, completion, extraction, routine drafting, runs well on models that cost a fraction of the frontier. For how open weights now set the price of closed models, see the open-weight price floor.

How can an organization switch AI models without rebuilding its product?

An organization can switch only if the model is a setting, not a dependency. Duolingo could move because it was free to pick the model for each task.

On ibl.ai, each agent's LLM is chosen per agent. On the organization in our recording, the catalogue listed 45 model providers and 316 chat models on one grid; it syncs itself every six hours, and a switch keeps the agent's prompts, data and connectors.

Costs then shows what each agent spends, so the saving from a switch is measured rather than assumed.

Who should own the AI stack that makes a model switch possible?

The organization paying for the inference should own the AI stack. A product rented per seat from one model vendor cannot follow prices down; Duolingo's could.

On ibl.ai you own all the code and the data, the platform runs model-agnostic, there is no per-seat pricing, and you can deploy anywhere, from your own cloud to a fully air-gapped network.

That is the same freedom to choose that cut Duolingo's cost per call, without building the platform yourself.

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.

Sources: Duolingo's Q3 2026 earnings call (November 3, 2026) and Q2 2026 earnings call (August 5, 2026), transcripts published by The Motley Fool. The brief called it "30x cheaper per call" and a switch to open-weight models; the calls support more than 30 times cheaper per Video Call conversation, first disclosed in August, with frontier models kept for some cases.

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.

Related Articles

Revolut Cut AI Coding Costs About 90% by Self-Hosting Open Models. What the Numbers Actually Say

Revolut says self-hosting open GLM models on 56 Nvidia B200 GPUs cut its AI coding costs to roughly a tenth of what it paid frontier labs, about $0.30 per million tokens. What the talk supports, what the viral version got wrong, and what it means for organizations without a GPU cluster.

ibl.aiNovember 4, 2026

Fine-Tunes Beat Frontier Models. Not Junior Analysts.

The claim going around financial services is that open-weight fine-tunes now do the work banks pay junior analysts for. Half of that is measured and true: Bridgewater's Qwen3-235B fine-tune hit 84.7% accuracy at 13.8x lower inference cost than frontier models. The other half is also measured, and it is false β€” on GAUGE, the benchmark graded against 1,001 real professional valuations, the best agent scored 53.4 against a junior-analyst mean of 66.0.

Jaione AmigotOctober 16, 2026

Four Frontier Models in a Day: The Real Cost Is Migration

Four frontier models shipped on September 22, 2026, and seven Claude models were retired during 2026. AWS puts one production model migration at two days to two weeks β€” the recurring cost is migration, not licensing.

Mikel AmigotSeptember 24, 2026

Ripple-65B: A 65B Apache 2.0 Coding Model That Runs on One Box. What the Benchmarks Actually Say

Ricursive's Ripple-65B Preview is a dense 65B Apache 2.0 model that reports 80.5 on Terminal-Bench 2.1, a 0.4-point edge over a 501B model. What the self-reported numbers support, what the headline leaves out, and why the license matters more than the leaderboard.

ibl.aiNovember 7, 2026

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

Custom quote

perpetual license Β· you own the stack

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

Best for: Organizations and enterprises that benefit from 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