-
Notifications
You must be signed in to change notification settings - Fork 143
feat: ultra vs metis #804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: ultra vs metis #804
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| 1. [Routing Engines: Meta-aggregated vs. Single Routing Primitive](#routing-engines) | ||
| 2. [Execution Model: Integrated Engine vs. Routing Primitive](#execution-model) | ||
| 3. [Configuration Layer: Optimized & Opinionated vs. Flexible Control](#configuration-layer) | ||
| 4. [Operational Realities: Managed Service vs. Self-Service](#operational-realities) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's break down what this means across five critical dimensions.
we mention only 4
blog/ultra-vs-metis.mdx
Outdated
| There are also other latency involved such as transaction landing latency, which is sub-seconds (50-400ms) for Ultra since | ||
| it uses Jupiter's proprietary transaction landing engine, Jupiter Beam. | ||
|
|
||
| > **"Ultra takes a fee, Metis or API-reseller providers don't"** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, they pay for Metis API via monthly sub
there is payment in both the cases, one is a subscription, one is based on tx size/usage
No description provided.