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

Quasar 438B Is API-Only, and That Is Not Sovereignty

Mikel AmigotSeptember 10, 2026
Premium

Multiverse Computing's Quasar 438B scored 43 on Intelligence Index v4.1.1 at launch on 2 September 2026, the top European result. It is also proprietary, API-only, and compressed from Z.ai's open-weights GLM-5.2.

The Short Answer

Multiverse Computing launched Quasar 438B on 2 September 2026, and at 43 on Artificial Analysis Intelligence Index v4.1.1 at launch it was the highest-scoring European model. It is also proprietary, API-only, and compressed from Z.ai's open-weights GLM-5.2 β€” so it is not sovereignty. Sovereignty is decided by where inference runs and who holds the weights. With ibl.ai you own all the code and the data.

A good European model and a sovereign European deployment are different purchases, and the launch coverage merged them.

What is Quasar 438B, and what did Multiverse Computing actually ship?

A 438-billion-parameter reasoning model from Multiverse Computing, headquartered in Donostia-San SebastiΓ‘n, Spain, announced on 2 September 2026.

The headline claim is the Artificial Analysis Intelligence Index, where Multiverse reports a score of 43 on v4.1.1 β€” ahead of NVIDIA Nemotron 3 Ultra at 38 and Mistral Medium 3.5 at 30, and the highest among the European models in that comparison.

The supporting numbers are specific enough to check. Terminal-Bench v2.1 of 69.3, an AA-LCR long-context reasoning score of 75.0, and a 500-token response including thinking time in 15.3 seconds.

Artificial Analysis independently lists the served model at roughly 180 output tokens per second, a 1M-token context window, and $0.60 per million input tokens against $1.80 per million output tokens.

Property Published value
Launch date2 September 2026
Parameters438B
AA Intelligence Index (v4.1.1)43
Terminal-Bench v2.169.3
Context window1M tokens
Output speed~180 tokens/sec
Price (in / out)$0.60 / $1.80 per 1M tokens
LanguagesEnglish, Spanish
Base modelGLM-5.2 (Z.ai, open weights)
WeightsProprietary, not published
AccessCompactifAI API only

Is Quasar 438B open-weights, and where do its weights come from?

No, and this is the part that most of the launch coverage left out.

Multiverse's own technical write-up states it plainly: Quasar 438B is a compressed model built from GLM-5.2, the open-weights model from Z.ai.

The compression is the company's actual product. A quantum-inspired pruning pass cuts the expert layers from 265 to 148 experts per layer, followed by a healing pass and quantization-aware compression in FP8 and NVFP4.

That is legitimate engineering, and the resulting model is genuinely faster and cheaper to serve than the base. It is also not a European base model. The trained weights Quasar derives from came from a Chinese lab, and the Quasar weights themselves are not published.

Quasar is announced only through the CompactifAI API and does not appear among the models Multiverse offers for private deployment.

In fairness to Multiverse, CompactifAI offers to create a custom "Slim" version of an open-source model a customer already uses. That is a different product from Quasar, and it is the one a sovereignty-minded buyer should be asking about.

Does running a European model make a European deployment sovereign?

No. A model's nationality is a property of the vendor, and sovereignty is a property of the deployment.

If your ministry sends prompts to dashboard.compactif.ai, then your inference runs on infrastructure you do not control, your data leaves your perimeter in transit, and your continued access depends on a commercial relationship with one supplier β€” the sole provider serving this model.

None of that changes because the supplier is in Spain rather than California. It is a shorter jurisdictional distance, which is worth something, and it is not the same thing as control.

The three questions that actually decide it are: where does inference execute, who holds the weights and the data at rest, and can you replace the model without rewriting the system around it.

This is the same test we applied to digital sovereignty in government AI, and Quasar passes none of the three today.

Regulatory pressure makes the distinction concrete rather than academic.

The EU AI Act entered into force on 1 August 2024, with obligations for general-purpose AI models applying from 2 August 2025 β€” obligations a public body has to evidence for the system it operates, not for the vendor's headquarters.

What should a European ministry or bank do about Quasar 438B today?

Use it, if it is the best model for the task, and stop treating that decision as a sovereignty decision.

Quasar is priced at a level where evaluating it costs almost nothing, and a 1M-token context with a 69.3 Terminal-Bench score is a serious agentic-coding proposition. Route the workloads that suit it there.

Then keep the sovereignty question where it belongs: in the platform layer that sits above the model. That layer is what holds your data, your permissions, your audit trail and your integrations, and it is the piece you cannot swap on a quarter's notice.

The practical shape is a platform you run yourself that can call Quasar over the API today, run Mistral's open-weight models or Gemma or Llama on your own hardware tomorrow, and move a workload between the two without a rewrite.

A model is a component with a shelf life of months. The platform around it is a decade-long commitment, which is why the ownership question belongs there.

How does ibl.ai make a European AI deployment sovereign?

By separating the two decisions the Quasar coverage conflated: which model you use, and who controls the system running it.

With ibl.ai you own all the code and the data.

The platform is delivered as full source code under a perpetual license and runs inside your own perimeter β€” your cloud, your VPC, on-premise, or a fully air-gapped network with no outbound connectivity.

It is model-agnostic across any LLM, so Quasar over the CompactifAI API and a self-hosted open-weight model can run side by side and swap without touching application code.

Billing is usage-based with no per-seat pricing, so cost tracks what your organization actually processes rather than how many civil servants have accounts.

For a European buyer, the practical consequence is that the residency question has a factual answer: the inference endpoint is one you chose, and the data at rest sits in storage you administer.

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.

Related reading: digital sovereignty: why agencies need model-agnostic AI β€” the same three-question test, applied to public-sector procurement.

Sources: launch date, Intelligence Index score of 43, Terminal-Bench 69.3 and the Mistral/Nemotron comparisons from Multiverse Computing's release and its launch page; the GLM-5.2 base model and the 265β†’148 expert pruning from Multiverse's technical write-up; output speed, context window and pricing from Artificial Analysis; AI Act dates from the European Commission.

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