Jupiter Exchange announced that Metis Router v7 is now a standalone project, formally decoupled from the Jupiter brand. This separation comes amid Solana’s intensifying aggregator wars, with rivals using Metis outputs to compare themselves to Jupiter and, in many cases, mislabelling those quotes as “Jupiter.”
The split is designed to fix that confusion. Jupiter will double down on its Jupiter Ultra engine (the multi-router execution layer behind its flagship swaps) while Metis Router becomes an independent, open-source primitive under metis.builders. Developers get a lean routing tool; Jupiter gets brand clarity as a full DeFi super-app.
Why Jupiter Detached From Metis Router
Jupiter gave three core reasons:
1. The Ecosystem Mislabelling Problem
Competitors often benchmarked themselves against “Jupiter quotes” that were simply Metis Router outputs lacking Ultra’s extras (RFQ systems, error handling, sandwich protection). The split ends that ambiguity.
2. Multi-Router Strategy
Ultra already routes volume to competing engines such as DFlow, OKX and JupiterZ. Jupiter no longer relies on Metis as its main execution layer.
3. Brand Focus
Jupiter has grown far beyond routing, now offering perps, prediction markets, limit orders and more. Separating Metis allows Jupiter to message itself as a clean DeFi super app, not just “the aggregator.”
Jupiter will still provide best-effort improvements (e.g., liquidity additions), but Ultra is now the priority.
What’s New in Metis Router v7
Metis v7 positions itself as a pure, low-level swap primitive:
- Real-time routing intelligence
- Raw instruction payloads for dev-level control
- Full composability, including CPI swaps
- JIT Aggregation: on-chain comparison of Prop AMMs at execution
- 60+ liquidity venues, with more integrations queued
- BrentOp Splitting: 1bp-precision trade splitting for greater efficiency
Metis prioritises flexibility; Jupiter Ultra still wins on end-to-end metrics, offering 34× better sandwich protection and 8–10× lower fees, according to Jupiter.
Accessing Metis v7
Metis now uses authenticated access:
| Access Type | Requirements | Best For |
|---|---|---|
| Hosted API | API key + Terms | Quick integration |
| Self-Hosted Binary | 10,000 JUP staked + Binary Key | Full control, custom RPC |
All integrators must clearly label outputs as Metis, not Jupiter.
When to Use Metis Router vs. Jupiter Ultra
Use Metis Router v7 when:
- You need full instruction control
- You’re writing on-chain logic or CPI swaps
- You want to manage your own slippage, fees and RPC setup
Use Jupiter Ultra when:
- You want end-to-end automation
- You need best execution with no infrastructure overhead
- You prioritise protection, speed and smart routing
- You’re a retail user or app needing simplicity
Aggregator Wars: DFlow’s Flash Surge
The timing of the split overlaps with renewed competition. On 15 November 2025, DFlow briefly overtook Jupiter with $1.21B daily volume, the first displacement since 2022. Its share plunged to 6.6% the following day, suggesting a one-off arb surge.
Still, it underscores a new multipolar phase in Solana aggregation. Tools like Titan and DFlow were among those accused of comparing themselves to Jupiter using Metis Router data rather than Ultra.
Jupiter still holds strong across derivatives and swap executions, but the field is no longer uncontested.
The Bigger Picture
For developers, the split means more modular choice: Metis for raw routing, Ultra for polished aggregation.
For users, nothing changes, Jupiter swaps remain Ultra-powered.
For the ecosystem, the separation marks a maturation: a clearer distinction between public-good infrastructure and full-stack DeFi products.
Disclaimer
This article is for information purposes only and does not constitute financial, investment, or legal advice.
