Short answer: Both platforms offer a free tier, but the limits are shaped differently. A registry's free tier is metered per call and limited in namespaces; a generated server runs locally for free and hosts on the Hub within plan limits. Estimate your call volume and the number of services before relying on either free tier for production.
What the free tiers are designed for
A free gateway tier is a way to start and evaluate, with a per-call allowance and a small number of namespaces. A local-first studio is free on the desktop and hosts docs and MCP together on the Hub within plan limits.
Where the limits bite
| Limit | Free gateway | Local / Hub |
|---|---|---|
| Call volume | Metered, free allowance | Local unlimited; Hub within plan |
| Services / namespaces | Few | One contract per project |
| Collaboration | Paid | Hub hosting |
| Custom domain | Often paid | Hub within plan |
How to estimate
Count the calls an agent makes per session, not just the number of users. Agent traffic is bursty and repeated, and a metered free tier runs out faster than a per-user intuition suggests.
The safe path
Develop locally for free, then compare the current hosted limits against your expected traffic before going to production. Do not assume a free tier covers a busy agent.
This is part of the Powerduck vs Smithery comparison. Next, read publishing without a registry.
Top comments (0)