# MEV Alpha Store > Low-latency MEV infrastructure for Solana: Private Orderflow, Private TPU Send, Shreds and leader-aware routing, built on a validator network. Data delivered via gRPC or WebSocket. Offers are personalized after contact on Telegram. This website is a catalog of our services. After you contact us on Telegram, each service is tailored to your needs and the price is agreed individually. Key facts: - Network: Solana mainnet - Main validators: Frankfurt - Regions: Frankfurt, Amsterdam, London, Dublin, New York, Tokyo, Singapore (all services) - Data delivery: gRPC or WebSocket - Pricing: personalized for each client; the price is agreed after contact on Telegram - Payments: SOL; fees are non-refundable - Transactions submitted through Private TPU Send are excluded from the Private Orderflow stream - Also known as: Solana mempool or pending-transaction stream (Private Orderflow), SWQoS or staked connections (Private TPU Send), shred stream similar to ShredStream (Shreds), backrun bundles - Private TPU Send accepts atomic bundles (for example a target transaction followed by a backrun), landing in the leader slots of validators in our network - Contact and orders: direct messages on Telegram, @MevAlphaStore (https://t.me/MevAlphaStore) - Announcements: Telegram channel (https://t.me/MevAlphaStore) - GitHub: https://github.com/MevAlphaPool/mevalpha-solana ## Services - [Private Orderflow](https://mevalpha.com/private-orderflow/): Transactions straight from validator TPUs, before they are executed and included in a block. Offer tailored to: the size of the stake pool you access. - [Private TPU Send](https://mevalpha.com/private-tpu-send/): Your transactions delivered straight to the slot leader, away from public channels. Offer tailored to: your required throughput (TPS). - [Shreds (Early Data)](https://mevalpha.com/shreds/): Block data while the block is still being produced, before replay. Offer tailored to: the number of regions you need. - [Orderflow + TPU Combo](https://mevalpha.com/orderflow-tpu-combo/): From spotting an opportunity to landing the transaction, in one package. Offer tailored to: stake pool size and throughput. - [Full Stack](https://mevalpha.com/full-stack/): Data, execution and routing in one package. Offer tailored to: stake pool size, throughput and regions. ## Who it is for - For bots, arbitrage & snipers: React to on-chain events first and land transactions in the slot that matters. Relevant: Shreds (Early Data), Private TPU Send. - For searchers & MEV teams: See pending transactions early and act on them within a single infrastructure. Relevant: Private Orderflow, Orderflow + TPU Combo, Full Stack. - For validators: Join our network as a validator or node operator. Terms are agreed individually. Relevant: Validator partnerships. ## Pricing and ordering - [Pricing](https://mevalpha.com/pricing/): how personalized pricing works - [Get started](https://mevalpha.com/get-started/): how to order, from first contact to live access - [FAQ](https://mevalpha.com/faq/): answers about location, latency, data formats, pricing, payments and refunds ## Documentation - [Documentation](https://mevalpha.com/docs/index.md): Technical documentation for MEV Alpha Store on Solana mainnet: Private Orderflow, Private TPU Send, Shreds (Early Data) and the Combo and Full Stack packages. - [How it works](https://mevalpha.com/docs/how-it-works.md): The life of a Solana transaction from submission to finality, and where MEV Alpha Store Private Orderflow, Private TPU Send, Shreds and leader-aware routing fit in. - [Glossary](https://mevalpha.com/docs/glossary.md): Definitions of Solana and MEV terms used in the MEV Alpha Store documentation, from TPU and SWQoS to shreds, entries, FEC sets and commitment levels. - [Your first connection](https://mevalpha.com/docs/getting-started.md): Step-by-step guide from requesting access to receiving the first Private Orderflow message and landing the first transaction through Private TPU Send. - [Authentication](https://mevalpha.com/docs/authentication.md): How MEV Alpha Store API keys work for gRPC and WebSocket streams and for Private TPU Send, how to pass them from code and how to keep them secure. - [Regions & endpoints](https://mevalpha.com/docs/regions.md): Regions where MEV Alpha Store infrastructure runs, how you receive your endpoints and how to choose a hosting location. - [Limits](https://mevalpha.com/docs/limits.md): Throughput and connection limits for MEV Alpha Store services, what happens when a limit is exceeded and how to design clients that handle bursts. - [Errors](https://mevalpha.com/docs/errors.md): HTTP, JSON-RPC, gRPC and WebSocket error codes returned by MEV Alpha Store services, what each one means and whether to retry. - [Troubleshooting](https://mevalpha.com/docs/troubleshooting.md): Common issues with MEV Alpha Store connections, latency, transaction landing and data streams, and how to resolve them. - [Private Orderflow](https://mevalpha.com/docs/private-orderflow.md): Receive pending Solana transactions from the TPU of MEV Alpha Store validators, pushed to your own Jito-compatible gRPC server or streamed over WebSocket. Integration, message format, coverage, backrun placement and processing guidelines. - [Private TPU Send](https://mevalpha.com/docs/private-tpu-send.md): Submit Solana transactions through MEV Alpha Store Private TPU Send, delivered to current and upcoming leaders over staked QUIC connections. Request format, code examples, priority fees and confirmation. - [Shreds (Early Data)](https://mevalpha.com/docs/shreds.md): Receive Solana block data from MEV Alpha Store before replay via gRPC or WebSocket. Message format, Rust and TypeScript consumers and how to reconstruct entries and transactions from shreds. - [Combo & Full Stack](https://mevalpha.com/docs/packages.md): How the MEV Alpha Store Orderflow + TPU Combo and Full Stack packages work, including credentials and leader-aware routing based on the Solana leader schedule. - [Latency & benchmarking](https://mevalpha.com/docs/latency.md): How to measure the latency advantage of MEV Alpha Store Shreds and Private Orderflow and the landing rate of Private TPU Send from your own server, with code examples and common measurement pitfalls. - [Production checklist](https://mevalpha.com/docs/production-checklist.md): Checklist for running MEV Alpha Store integrations in production, covering infrastructure, credentials, stream consumers, transaction sending, monitoring and operations. - [How to see pending transactions on Solana (mempool)](https://mevalpha.com/docs/solana-mempool.md): Solana has no public mempool. Where pending transactions actually are, which data sources show them before execution, and how to stream them with MEV Alpha Store Private Orderflow. - [How to backrun a transaction on Solana](https://mevalpha.com/docs/solana-backrun.md): Step by step, how to spot a price-moving Solana transaction before it executes, build a backrun with a profit check and land it right behind the target with an atomic bundle through MEV Alpha Store. - [What is SWQoS on Solana (stake-weighted QoS)](https://mevalpha.com/docs/solana-swqos.md): How stake-weighted QoS decides which Solana transactions reach the leader under congestion, and how to send over staked connections with Private TPU Send. - [What is a Solana shred stream (shreds vs RPC)](https://mevalpha.com/docs/solana-shred-stream.md): Shreds vs RPC on Solana: how a shred stream shows a block's transactions while it is still being produced, before replay, and when that matters. - [Atomic bundles on Solana, with and without Jito](https://mevalpha.com/docs/solana-bundles.md): What an atomic bundle is on Solana, how Jito bundles and tips work, and how to land bundles through Private TPU Send without a Jito tip. ## Optional - [Validator partnerships](https://mevalpha.com/validators/): cooperation with validator operators and node owners - [Terms](https://mevalpha.com/terms/): summary of the terms of service - [Acceptable use](https://mevalpha.com/acceptable-use/): no sandwich attacks or front-running, wallet verification - [Full text for LLMs](https://mevalpha.com/llms-full.txt): all website content in one Markdown file