> For the complete documentation index, see [llms.txt](https://elite-node.gitbook.io/elite-node-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elite-node.gitbook.io/elite-node-docs/introduction/welcome-to-elite-node.md). # Welcome to Elite Node The new era of MEV on Solana. **The Product:** \ Elite Node builds and provides private, high-performance execution infrastructure for traders who demand near-zero latency. Our core offering is a fully-managed, co-located Firedancer stack with direct Jito Shredstream access, engineered for a single purpose: to dominate every slot. **The Technology:** \ Our core is built on Rust and deployed on co-located Firedancer nodes to achieve sub-millisecond latency. We utilize a custom, low-level data pipeline that interfaces directly with the Jito Shredstream, allowing us to decode and analyze transactions in real-time, pre-finalization. This provides our partners with a decisive advantage to instantly construct and submit response bundles for 0-block strategy execution. **Access:** \ Elite Node is a private, application-only platform. We partner with professional traders, market makers, and liquidity providers who understand that in the MEV race, infrastructure, not strategy, is the ultimate victor. We are not a mass-market product. We are a strategic advantage. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://elite-node.gitbook.io/elite-node-docs/introduction/welcome-to-elite-node.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.