Jupiter Metis Binary: self-host the Solana liquidity router

Jupiter Metis Binary: self-host the Solana liquidity router. Source and releases: github.com/jup-ag/metis-binary; product/docs: metis.builders.

Click to zoom

What Metis is

Metis is Jupiter’s onchain multi-hop, multi-split routing engine — the pathfinder that walks Solana DEX liquidity (Raydium, Orca, Meteora, Pump, Phoenix, Sanctum, and dozens more). Marketing on metis.builders frames it as the Solana liquidity engine with 60+ venues; treat volume stats as product claims, not your SLA.

In the hosted Jupiter Swap API V2, Metis is one routing engine among several:

Use the meta-aggregator when you want best price and least ops. Use metis-binary when latency, data residency, custom fee accounts, instruction composability, or independence from Jupiter’s public API rate limits matter enough to run the router yourself.

Repository

jup-ag/metis-binary is intentionally thin: Dockerfile (debian trixie-slim, amd64), release zips of metis-binary-x86_64-unknown-linux-gnu, and a Fly.io example. The algorithm and API surface are documented on metis.builders — not reimplemented in the public tree. Latest tags at research time were in the v7.x line (e.g. v7.1.0). Always pin a release tag in production.

# From upstream Dockerfile — linux/amd64 binary zip
FROM --platform=linux/amd64 debian:trixie-slim
WORKDIR /app
# unzip metis-binary-x86_64-unknown-linux-gnu.zip → ./metis-binary
ENV RUST_LOG=info
CMD ["/app/metis-binary"]

Access: Binary Key

Self-host is not anonymous. Docs: Binary Key.

1. Request via portal.metis.builders.
2. Prove control of a wallet with at least 10,000 JUP staked at vote.jup.ag — one escrow, do not split stake across multiple escrows for the check.
3. Receive Binary Key by email; one key → one binary instance.

Never put the key in client code or git. Pass as BINARY_KEY / --binary-key. Docs state no Jupiter-side rate limit on the self-hosted surface (your RPC and hardware become the limit). Penalties and binary errors have dedicated pages if the key or process misbehaves — read those before paging on-call.

Run shape

Hard requirements: BINARY_KEY + RPC_URL. Recommended: Yellowstone gRPC so account state stays hot without thrashing HTTP RPC.

RUST_LOG=info ./metis-binary \
  --binary-key "$BINARY_KEY" \
  --rpc-url "$RPC_URL" \
  --yellowstone-grpc-endpoint "$YELLOWSTONE_GRPC_ENDPOINT" \
  --yellowstone-grpc-x-token "$YELLOWSTONE_GRPC_X_TOKEN"

# Defaults once healthy:
#   API      127.0.0.1:8080
#   metrics  127.0.0.1:9100  → /metrics /health /ready

Full tables (Yellowstone transport knobs, diagnostic toggles) live under Self host. Config via env, CLI flags (1:1 with env), or --env-file.

HTTP API (self-hosted)

Documented reference routes:

Quote guides cover platformFeeBps + feeAccount, onlyDirectRoutes (often worse price — use sparingly), and maxAccounts (recommend starting near 64; too low drops account-heavy AMMs like some DLMM paths). Simple vs shared-accounts routing instructions matter when markets lack ALTs — see the requote-with-lower-max-accounts guide before shipping a tight CU/account budget.

# Example shape — pin host/port to your API_ENDPOINT
curl -sG "http://127.0.0.1:8080/quote" \
  --data-urlencode "inputMint=So11111111111111111111111111111111111111112" \
  --data-urlencode "outputMint=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v" \
  --data-urlencode "amount=100000000"

Deploy notes

• Docker: upstream image path expects the linux gnu zip; platform linux/amd64.
• Fly.io: examples/fly.io — fly launch / fly deploy; README suggests performance-class sizing (e.g. performance-8x) for serious load — validate against your QPS and gRPC.
• Observability: scrape /metrics; gate traffic on /ready not just process up.
• Send path: binary builds quotes/txs; landing is still your RPC, bundle stack, or Jupiter submit infrastructure — self-host does not mean free inclusion.

Chooser

People and links

Resources

• metis-binary repository
• Metis builders
• Solana aggregators for developers
• Jupiter Exchange on Solana